Created attachment 190561 [details] 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
Please attach the full dmesg output.
Created attachment 190631 [details] output of dmesg here is the full dmesg log
Does this still happen with a 4.3(-rc) kernel?
Created attachment 191041 [details] dmesg from failed 4.3rc6 resume
Created attachment 191051 [details] dmesg from successful 4.2.3 resume
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.
The log from 4.3-rc6 doesn't show any trace of the amdgpu driver. Did you accidentally disable it when compiling that kernel?
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.
Created attachment 192801 [details] 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.
Running 4.5.1 stable, no trace of the former problem. I guess it was resolved at some point.