Description of problem: Random lock ups of the computer, it becomes unresponsive and a hard reboot is needed. Version-Release number of selected component (if applicable): 4.15.13-300.fc27.x86_64 How reproducible: Very random, it seems independent of the program being used. Steps to Reproduce: 1. Wait for it. 2. 3. Actual results: -- Reboot -- Apr 02 18:40:08 wpa_supplicant[1046]: wlp8s0: WPA: Group rekeying completed with e2:55:7d:77:2d:51 [GTK=CCMP] Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: at page 0x0000000103202000 from 27 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:56 vm_id:4 pas_id:0) Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: at page 0x0000000103202000 from 27 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:56 vm_id:4 pas_id:0) Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: at page 0x0000000103205000 from 27 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:56 vm_id:4 pas_id:0) Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: at page 0x0000000103205000 from 27 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:56 vm_id:4 pas_id:0) Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: at page 0x0000000103204000 from 27 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:56 vm_id:4 pas_id:0) Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: at page 0x0000000103204000 from 27 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:56 vm_id:4 pas_id:0) Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: at page 0x0000000103201000 from 27 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:56 vm_id:4 pas_id:0) Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: at page 0x0000000103201000 from 27 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:56 vm_id:4 pas_id:0) Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: at page 0x0000000103200000 from 27 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:56 vm_id:4 pas_id:0) Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x004C0071 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: at page 0x0000000103200000 from 27 Apr 02 18:40:05 kernel: amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:56 vm_id:4 pas_id:0) Apr 02 18:40:05 kernel: gmc_v9_0_process_interrupt: 7 callbacks suppressed Apr 02 18:39:40 sssd[secrets][8739]: Starting up Expected results: No crashes, Additional info: model name : AMD Ryzen 5 2400G with Radeon Vega Graphics stepping : 0 microcode : 0x8101007
It might be unrelated but running the darktable flatpak seems a reliable way to trigger this, although I also had a crash with Chromium. Magic Sysrq keys work.
This comment was flagged a spam, view the edit history to see the original text if required.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.