https://bugzilla.kernel.org/show_bug.cgi?id=106291
Bug ID: 106291 Summary: amdgpu fails GPU reset when resuming from suspend Product: Drivers Version: 2.5 Kernel Version: 4.2.3 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri@kernel-bugs.osdl.org Reporter: universaledge97@gmail.com Regression: No
Created attachment 190561 --> https://bugzilla.kernel.org/attachment.cgi?id=190561&action=edit output of "dmesg | grep amdgpu"
Rarely, when resuming from suspend, amdgpu will fail to reset the GPU, causing X.org to crash. This does have any particular cause I can identify. Any variety of programs could be open when this error occurs. Attached is a log of the output of "dmesg | grep amdgpu", although I have the full ouput from dmesg if needed.
Running XFX R9 285 Tonga
https://bugzilla.kernel.org/show_bug.cgi?id=106291
--- Comment #1 from Michel Dänzer michel@daenzer.net --- Please attach the full dmesg output.
https://bugzilla.kernel.org/show_bug.cgi?id=106291
universaledge97@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #190561|0 |1 is obsolete| |
--- Comment #2 from universaledge97@gmail.com --- Created attachment 190631 --> https://bugzilla.kernel.org/attachment.cgi?id=190631&action=edit output of dmesg
here is the full dmesg log
https://bugzilla.kernel.org/show_bug.cgi?id=106291
--- Comment #3 from Michel Dänzer michel@daenzer.net --- Does this still happen with a 4.3(-rc) kernel?
https://bugzilla.kernel.org/show_bug.cgi?id=106291
--- Comment #4 from universaledge97@gmail.com --- Created attachment 191041 --> https://bugzilla.kernel.org/attachment.cgi?id=191041&action=edit dmesg from failed 4.3rc6 resume
https://bugzilla.kernel.org/show_bug.cgi?id=106291
--- Comment #5 from universaledge97@gmail.com --- Created attachment 191051 --> https://bugzilla.kernel.org/attachment.cgi?id=191051&action=edit dmesg from successful 4.2.3 resume
https://bugzilla.kernel.org/show_bug.cgi?id=106291
--- Comment #6 from universaledge97@gmail.com --- Sorry for the delay; not much time to debug when in college.
I am having an issue with suspend on 4.3rc6, but instead of amdgpu failing to reset, I simply experience an uninteractive black screen on resume everytime. Not sure if the two issues are in any way related. Accessing the machine through SSH, I was able to grab dmesg output when it happened.
For comparison, I also grabbed dmesg from a successful 4.2.3 suspend-resume.
https://bugzilla.kernel.org/show_bug.cgi?id=106291
--- Comment #7 from Michel Dänzer michel@daenzer.net --- The log from 4.3-rc6 doesn't show any trace of the amdgpu driver. Did you accidentally disable it when compiling that kernel?
https://bugzilla.kernel.org/show_bug.cgi?id=106291
--- Comment #8 from universaledge97@gmail.com --- It turned out that the amdgpu kernel module was not included in compilation. I normally use the linux-mainline package from the AUR (I run Arch Linux) to install rc kernels, where, for some reason, the amdgpu module was not enabled to compile by default. I now have amdgpu built into 4.3rc7, and will report back if the issue is still present.
https://bugzilla.kernel.org/show_bug.cgi?id=106291
--- Comment #9 from universaledge97@gmail.com --- Created attachment 192801 --> https://bugzilla.kernel.org/attachment.cgi?id=192801&action=edit dmesg 4.3.0 - Xorg hang
I ended up having to reinstall Arch Linux after my gpg directory was corrupted when the system auto-suspended in the middle of a package upgrade.
Running Linux 4.3.0 from Arch Linux testing repo: I'm not getting the GPU reset bug anymore; rather Xorg just randomly hangs indefinitely after waking from suspend, resulting in an uninteractive black screen. Curiously, there's no Xorg crash log. The dmesg log provides a call trace from before the hang.
https://bugzilla.kernel.org/show_bug.cgi?id=106291
universaledge97@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |OBSOLETE
--- Comment #10 from universaledge97@gmail.com --- Running 4.5.1 stable, no trace of the former problem. I guess it was resolved at some point.
dri-devel@lists.freedesktop.org