https://bugzilla.kernel.org/show_bug.cgi?id=198883 --- Comment #60 from Andrey Grodzovsky (andrey.grodzovsky@xxxxxxx) --- (In reply to Ricardo Ribalda from comment #59) > Hi Andrey > > Testing with llvm7 setup: > > > R600_DEBUG=notiling,norbplus xinit > > does not avoid the hang :( > > [ 31.200134] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, > last signaled seq=7, last emitted seq=8 > [ 31.200147] [drm] IP block:gfx_v8_0 is hung! > [ 31.200152] [drm] GPU recovery disabled. > > > > GALLIUM_DDEBUG=flush xinit > > Seems to have a (good) impact. Hang happened after around 20 boots. > > [ 13.389894] NET: Registered protocol family 39 > [ 28.640142] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, > last signaled seq=652, last emitted seq=654 > [ 28.640154] [drm] IP block:gfx_v8_0 is hung! > [ 28.640160] [drm] GPU recovery disabled. > [ 246.752083] INFO: task amdgpu_cs:0:636 blocked for more than 120 seconds. > [ 246.752092] Not tainted 4.16.0-rc4-qtec-standard #1 > [ 246.752095] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables > this message. > [ 246.752099] amdgpu_cs:0 D 0 636 543 0x00080000 > [ 246.752099] amdgpu_cs:0 D 0 636 543 0x00080000 > [ 246.752103] Call Trace: > [ 246.752115] ? __schedule+0x25c/0x860 > [ 246.752122] ? dma_fence_default_wait+0x10c/0x280 > [ 246.752124] ? dma_fence_default_wait+0x1c8/0x280 > [ 246.752127] schedule+0x2f/0x90 > [ 246.752130] schedule_timeout+0x1f1/0x440 > [ 246.752220] ? amdgpu_cs_bo_validate+0x7f/0x120 [amdgpu] > [ 246.752276] ? amdgpu_ttm_alloc_gart+0x5d/0x270 [amdgpu] > [ 246.752284] ? dma_fence_default_wait+0x10c/0x280 > [ 246.752287] ? dma_fence_default_wait+0x1c8/0x280 > [ 246.752290] dma_fence_default_wait+0x1f4/0x280 > [ 246.752294] ? dma_fence_default_wait+0x280/0x280 > [ 246.752297] dma_fence_wait_timeout+0x2e/0x100 > [ 246.752359] amdgpu_ctx_wait_prev_fence+0x46/0x80 [amdgpu] > [ 246.752418] amdgpu_cs_ioctl+0x1f2/0x1af0 [amdgpu] > [ 246.752478] ? amdgpu_cs_find_mapping+0xe0/0xe0 [amdgpu] > [ 246.752504] drm_ioctl_kernel+0x59/0xb0 [drm] > [ 246.752524] drm_ioctl+0x29f/0x340 [drm] > [ 246.752581] ? amdgpu_cs_find_mapping+0xe0/0xe0 [amdgpu] > [ 246.752630] amdgpu_drm_ioctl+0x49/0x80 [amdgpu] > [ 246.752635] do_vfs_ioctl+0x8e/0x680 > [ 246.752641] ? SyS_futex+0x11d/0x150 > [ 246.752644] SyS_ioctl+0x74/0x80 > [ 246.752647] ? get_vtime_delta+0xe/0x40 > [ 246.752650] do_syscall_64+0x7b/0x1d0 > [ 246.752654] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 > [ 246.752658] RIP: 0033:0x3e292e57e7 > [ 246.752660] RSP: 002b:00007f17a2924b88 EFLAGS: 00000246 ORIG_RAX: > 0000000000000010 > [ 246.752663] RAX: ffffffffffffffda RBX: 00007f17a2924c78 RCX: > 0000003e292e57e7 > [ 246.752664] RDX: 00007f17a2924bf0 RSI: 00000000c0186444 RDI: > 000000000000000d > [ 246.752666] RBP: 00007f17a2924bf0 R08: 00007f17a2924ca0 R09: > 00007f17a2924c78 > [ 246.752667] R10: 00007f17a2924ca0 R11: 0000000000000246 R12: > 00000000c0186444 > [ 246.752668] R13: 000000000000000d R14: 0000000000d2c588 R15: > 0000000000000002 > > > kmscube git HEAD have not stalled after 50 attempts without any flag in > GALLIUM_DDEBUG or R600_DEBUG. > > It might not be relevant, but my platform can only boot with BIOS (it is > based on coreboot). When you tried this bug did you tried with UEFI or BIOS? > > Thanks I think my BIOS is set to UEFI but it can't have any relation to this issue. Andrey -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
