Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#64866 - [linux] GPU resets since linux 5.4 on Ryzen 5 2500U
Attached to Project:
Arch Linux
Opened by rainer (raneon) - Monday, 16 December 2019, 21:47 GMT
Last edited by freswa (frederik) - Friday, 21 February 2020, 14:49 GMT
Opened by rainer (raneon) - Monday, 16 December 2019, 21:47 GMT
Last edited by freswa (frederik) - Friday, 21 February 2020, 14:49 GMT
|
DetailsSince the upgrade to linux 5.4 I get a lot of graphic resets/crashes with a Ryzen 5 2500U notebook (Vega 8 GPU, HP Envy x360). Basically I only have to open on Plasma the system settings or Firefox with Webrender enabled. Then the GPU will crash and try to reset, which partially works but takes 20 seconds. The system will not crash completely, only the GPU will do a reset.
Testing on Plasma Wayland was easier, as the system was able to recover better from the GPU reset, X11 must be killed before doing another test. Linux 5.3 worked fine. Downgrading to linux-lts solves the GPU reset issue, but then standby is broken, so I cannot use this as a stable workaround. Additional info: * Linux 5.4 Steps to reproduce: - Open Plasma (Wayland) - Open system settings and scroll down in the menu entry list or open Firefox with Webrender enabled => GPU crashes journalctl -f (Plasma Wayland) Dez 16 22:25:11 pc kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! Dez 16 22:25:11 pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered Dez 16 22:25:33 pc kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! Dez 16 22:25:33 pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered Dez 16 22:25:55 pc kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! Dez 16 22:25:55 pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered Dez 16 22:26:15 pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered Dez 16 22:26:38 pc kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! Dez 16 22:26:38 pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered journalctl -f (Plasma) Dez 16 22:32:23 pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered Dez 16 22:36:42 pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered Dez 16 22:37:28 pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered |
This task depends upon
Closed by freswa (frederik)
Friday, 21 February 2020, 14:49 GMT
Reason for closing: No response
Additional comments about closing: This seems pretty stalled to me. If it's still an issue. Please fill a re-open request. Thank you :)
Friday, 21 February 2020, 14:49 GMT
Reason for closing: No response
Additional comments about closing: This seems pretty stalled to me. If it's still an issue. Please fill a re-open request. Thank you :)
There is some similarity to https://gitlab.freedesktop.org/drm/amd/issues/934
Or you could open a new bug on https://gitlab.freedesktop.org/drm/amd/issues