Comment # 10
on bug 105819
from Antonio Chirizzi
Just to say that the bug is still present with latest ubuntu kernel 4.20.0-042000-generic. Graphical system hung/frozen, but able to connect through ssh to shutdown the system (which went through but was never completely achieved by the way): Jan 12 10:54:37 antonioRyzen kernel: [79117.092896] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Jan 12 10:55:46 antonioRyzen kernel: [79186.259081] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=2040014, emi tted seq=2040017 Jan 12 10:55:46 antonioRyzen kernel: [79186.259091] [drm] GPU recovery disabled. Jan 12 10:58:06 antonioRyzen kernel: [79325.706182] INFO: task kworker/u32:53:5973 blocked for more than 120 seconds. Jan 12 10:58:06 antonioRyzen kernel: [79325.706189] Not tainted 4.20.0-042000-generic #201812232030 Jan 12 10:58:06 antonioRyzen kernel: [79325.706191] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 12 10:58:06 antonioRyzen kernel: [79325.706194] kworker/u32:53 D 0 5973 2 0x80000000 Jan 12 10:58:06 antonioRyzen kernel: [79325.706217] Workqueue: events_unbound commit_work [drm_kms_helper] Jan 12 10:58:06 antonioRyzen kernel: [79325.706219] Call Trace: Jan 12 10:58:06 antonioRyzen kernel: [79325.706230] __schedule+0x29e/0x840 Jan 12 10:58:06 antonioRyzen kernel: [79325.706234] schedule+0x2c/0x80 Jan 12 10:58:06 antonioRyzen kernel: [79325.706236] schedule_timeout+0x258/0x360 Jan 12 10:58:06 antonioRyzen kernel: [79325.706333] ? optc1_get_crtc_scanoutpos+0x69/0xa0 [amdgpu] Jan 12 10:58:06 antonioRyzen kernel: [79325.706338] dma_fence_default_wait+0x20a/0x280 Jan 12 10:58:06 antonioRyzen kernel: [79325.706340] ? dma_fence_release+0xa0/0xa0 Jan 12 10:58:06 antonioRyzen kernel: [79325.706343] dma_fence_wait_timeout+0xe7/0x110 Jan 12 10:58:06 antonioRyzen kernel: [79325.706346] reservation_object_wait_timeout_rcu+0x201/0x340 Jan 12 10:58:06 antonioRyzen kernel: [79325.706411] ? amdgpu_get_vblank_counter_kms+0x111/0x160 [amdgpu] Jan 12 10:58:06 antonioRyzen kernel: [79325.706505] amdgpu_dm_do_flip+0x12c/0x3a0 [amdgpu] Jan 12 10:58:06 antonioRyzen kernel: [79325.706598] amdgpu_dm_atomic_commit_tail+0x738/0xe20 [amdgpu] Jan 12 10:58:06 antonioRyzen kernel: [79325.706601] ? __switch_to_asm+0x40/0x70 Jan 12 10:58:06 antonioRyzen kernel: [79325.706603] ? __switch_to_asm+0x34/0x70 Jan 12 10:58:06 antonioRyzen kernel: [79325.706606] ? wait_for_completion_timeout+0x38/0x140 Jan 12 10:58:06 antonioRyzen kernel: [79325.706608] ? __switch_to_asm+0x40/0x70 Jan 12 10:58:06 antonioRyzen kernel: [79325.706610] ? __switch_to_asm+0x34/0x70 Jan 12 10:58:06 antonioRyzen kernel: [79325.706611] ? __switch_to_asm+0x40/0x70 Jan 12 10:58:06 antonioRyzen kernel: [79325.706623] commit_tail+0x42/0x70 [drm_kms_helper] Jan 12 10:58:06 antonioRyzen kernel: [79325.706633] commit_work+0x12/0x20 [drm_kms_helper] Jan 12 10:58:06 antonioRyzen kernel: [79325.706637] process_one_work+0x20f/0x410 Jan 12 10:58:06 antonioRyzen kernel: [79325.706640] worker_thread+0x34/0x400 Jan 12 10:58:06 antonioRyzen kernel: [79325.706643] kthread+0x120/0x140 Jan 12 10:58:06 antonioRyzen kernel: [79325.706645] ? pwq_unbound_release_workfn+0xd0/0xd0 Jan 12 10:58:06 antonioRyzen kernel: [79325.706648] ? __kthread_parkme+0x70/0x70 Jan 12 10:58:06 antonioRyzen kernel: [79325.706650] ret_from_fork+0x22/0x40 Here comes the reboot: Jan 12 11:00:30 antonioRyzen kernel: [ 0.000000] Linux version 4.20.0-042000-generic (kernel@tangerine) (gcc version 8.2.0 (Ubuntu 8.2.0-12ubuntu1)) #201812232030 SMP Mon Dec 24 01:32:58 UTC 2018 Jan 12 11:00:30 antonioRyzen kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000-generic root=UUID=38be40bd-cd34-4ab8-93d3-ff3a317f25eb ro quiet splash processor.max_cstate=1 vt.handoff=1
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
