https://bugs.freedesktop.org/show_bug.cgi?id=104345 --- Comment #13 from bernhardu --- Happened again. A way to avoid that crash may be to not stay int first cold boot. I am not sure but I think I never saw this when system was running from a rebooted state (warm boot). [ 0.000000] Linux version 4.19.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.12-1 (2018-12-22) ... [32345.334084] amdgpu 0000:08:00.0: GPU fault detected: 146 0x06407704 for process plasmashell pid 1422 thread plasmashel:cs0 pid 1720 [32345.334092] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001002C8 [32345.334096] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02077004 [32345.334101] amdgpu 0000:08:00.0: VM fault (0x04, vmid 1, pasid 32775) at page 1049288, read from 'SDM0' (0x53444d30) (119) [32345.334114] amdgpu 0000:08:00.0: GPU fault detected: 146 0x06407704 for process plasmashell pid 1422 thread plasmashel:cs0 pid 1720 [32345.334118] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001002C8 [32345.334121] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02077004 [32345.334125] amdgpu 0000:08:00.0: VM fault (0x04, vmid 1, pasid 32775) at page 1049288, read from 'SDM0' (0x53444d30) (119) [32345.334523] amdgpu 0000:08:00.0: GPU fault detected: 146 0x06d8770c for process plasmashell pid 1422 thread plasmashel:cs0 pid 1720 [32345.334528] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001002DB [32345.334532] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0207700C [32345.334538] amdgpu 0000:08:00.0: VM fault (0x0c, vmid 1, pasid 32775) at page 1049307, read from 'SDM0' (0x53444d30) (119) [32355.357958] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=947938, emitted seq=947940 [32355.357965] [drm] GPU recovery disabled. [32505.119425] INFO: task kworker/u32:2:12454 blocked for more than 120 seconds. [32505.119433] Tainted: G OE 4.19.0-1-amd64 #1 Debian 4.19.12-1 [32505.119435] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [32505.119438] kworker/u32:2 D 0 12454 2 0x80000000 [32505.119460] Workqueue: events_unbound commit_work [drm_kms_helper] [32505.119464] Call Trace: [32505.119474] ? __schedule+0x2a2/0x870 [32505.119480] ? __switch_to_asm+0x40/0x70 [32505.119484] schedule+0x28/0x80 [32505.119488] schedule_timeout+0x26d/0x390 [32505.119586] ? dce110_timing_generator_get_position+0x5b/0x70 [amdgpu] [32505.119682] ? dce110_timing_generator_get_crtc_scanoutpos+0x70/0xb0 [amdgpu] [32505.119687] dma_fence_default_wait+0x238/0x2a0 [32505.119691] ? dma_fence_release+0x90/0x90 [32505.119695] dma_fence_wait_timeout+0xdd/0x100 [32505.119699] reservation_object_wait_timeout_rcu+0x173/0x280 [32505.119800] amdgpu_dm_do_flip+0x112/0x340 [amdgpu] [32505.119903] amdgpu_dm_atomic_commit_tail+0x750/0xdb0 [amdgpu] [32505.119909] ? wait_for_completion_timeout+0x3b/0x1a0 [32505.119913] ? __switch_to_asm+0x34/0x70 [32505.119917] ? __switch_to_asm+0x40/0x70 [32505.119921] ? __switch_to_asm+0x34/0x70 [32505.119924] ? __switch_to_asm+0x40/0x70 [32505.119938] commit_tail+0x3d/0x70 [drm_kms_helper] [32505.119946] process_one_work+0x1a7/0x3a0 [32505.119951] worker_thread+0x30/0x390 [32505.119955] ? pwq_unbound_release_workfn+0xd0/0xd0 [32505.119959] kthread+0x112/0x130 [32505.119963] ? kthread_bind+0x30/0x30 [32505.119967] ret_from_fork+0x22/0x40 [32528.537326] sysrq: SysRq : Keyboard mode set to system default -- You are receiving this mail because: You are the assignee for the bug.