[Bug 109526] [CARRIZO] amdgpu fails to resume from S3, atombios stuck executing C554 (len 629, WS 0, PS 0)
https://bugs.freedesktop.org/show_bug.cgi?id=109526
Bug ID: 109526 Summary: [CARRIZO] amdgpu fails to resume from S3, atombios stuck executing C554 (len 629, WS 0, PS 0) Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: johannes.hirte@datenkhaos.de
there is already a similar report at kernel bugzilla, but nobody took notice: https://bugzilla.kernel.org/show_bug.cgi?id=190971
It's a kernel bug, first seen with linux-4.20 on my Carrizo. I don't have a testcase for reproducing, so it's hard to bisect. Sometimes it happens multiple times a day, with every suspend-resume cycle. Sometimes the machine works for several days with at least two suspend-resume-cycles per day.
https://bugs.freedesktop.org/show_bug.cgi?id=109526
--- Comment #1 from Johannes Hirte johannes.hirte@datenkhaos.de --- Still an issue with linux-5.0.0-rc6
https://bugs.freedesktop.org/show_bug.cgi?id=109526
--- Comment #2 from Nicholas Kazlauskas nicholas.kazlauskas@amd.com --- Please post your full dmesg log and an Xorg log if applicable.
I see you have a partial log for the problem on the kernel bugzilla but it'd help to have a full one.
https://bugs.freedesktop.org/show_bug.cgi?id=109526
--- Comment #3 from Johannes Hirte johannes.hirte@datenkhaos.de --- Created attachment 143380 --> https://bugs.freedesktop.org/attachment.cgi?id=143380&action=edit dmesg log
full dmesg log from boot until a hang attached
https://bugs.freedesktop.org/show_bug.cgi?id=109526
--- Comment #4 from Johannes Hirte johannes.hirte@datenkhaos.de --- Anything I can do help debugging this? It's still an issue with 5.1-rc1 and really annoying.
https://bugs.freedesktop.org/show_bug.cgi?id=109526
--- Comment #5 from Johannes Hirte johannes.hirte@datenkhaos.de --- Created attachment 144083 --> https://bugs.freedesktop.org/attachment.cgi?id=144083&action=edit dmesg log from suspend->resume->suspend->resume
When this bug occurs, from sddm it is possible to put the system into suspend again via hotkey. In most cases the second resume works. Attaching a dmesg output from such a suspend->resume->suspend->resume cycle. Maybe this helps debugging this.
https://bugs.freedesktop.org/show_bug.cgi?id=109526
--- Comment #6 from Johannes Hirte johannes.hirte@datenkhaos.de --- ping? still an issue with kernel 5.1
https://bugs.freedesktop.org/show_bug.cgi?id=109526
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #7 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/688.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org