Created attachment 1915900 [details] kernel log 1. Please describe the problem: My machine randomly locks up after an upgrade from Fedora 34 to Fedora 35. The only running applications are Thunderbird and Firefox. 2. What is the Version-Release number of the kernel: kernel-5.19.8-100.fc35.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Yes. kernel-5.17.12-100.fc34.x86_64 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Afraid not. I do not know the trigger yet. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: I have not tested that yet. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Attached kernel log from the hang, plus the latest fresh boot.
To make this easier to find, these are the first lines of the hang: > Oct 04 07:35:49 kernel: radeon 0000:00:01.0: ring 5 stalled for more than 10080msec > Oct 04 07:35:49 kernel: radeon 0000:00:01.0: GPU lockup (current fence id 0x0000000000002ab9 last fence id 0x0000000000002abb on ring 5) > Oct 04 07:35:49 kernel: radeon 0000:00:01.0: Saved 345 dwords of commands on ring 0. > Oct 04 07:35:49 kernel: radeon 0000:00:01.0: GPU softreset: 0x0000038C Followed by: > Oct 04 07:35:50 kernel: radeon 0000:00:01.0: GPU reset succeeded, trying to resume > Oct 04 07:35:50 kernel: radeon 0000:00:01.0: Wait for MC idle timedout ! > Oct 04 07:35:50 kernel: radeon 0000:00:01.0: Wait for MC idle timedout ! > Oct 04 07:35:50 kernel: [drm] ring test on 0 succeeded in 3 usecs And eventually: > Oct 04 07:35:51 kernel: [drm:cik_ring_test [radeon]] *ERROR* radeon: ring 1 test failed (scratch(0x3010C)=0xCAFEDEAD) > Oct 04 07:35:51 kernel: [drm:cik_ring_test [radeon]] *ERROR* radeon: ring 2 test failed (scratch(0x3010C)=0xCAFEDEAD) > Oct 04 07:35:51 kernel: [drm:cik_sdma_ring_test [radeon]] *ERROR* radeon: ring 3 test failed (0xCAFEDEAD) > Oct 04 07:35:51 kernel: [drm:cik_resume [radeon]] *ERROR* cik startup failed on resume > Oct 04 07:35:52 kernel: [drm:cik_ib_test [radeon]] *ERROR* radeon: fence wait timed out. > Oct 04 07:35:52 kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-110). After which the system was too wedged to respond, or log anything else.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
Unfortunately the bug remains in Fedora 36.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.