For a long time now, I don't recall which 3.x broke this but there's been many changes since and now, when the GPU does randomly reset, the display goes blank, X display is restored, but I can only move mouse, cannot interact with X. Can someone point me to some debugging approaches to see if there's some lock being held somewhere thats causing this? I am able to ssh into the laptop so, this seems to point to some sort of lock thats not released. Bisecting radeon drm will be difficult if I have to start from near the beginning of r600g drm support.
This looks like a deadlock in the kernel. I guess some fence is not signalled during the reset, so GEM_WAIT_IDLE never returns.
How to debug? Do we have a flag to show lock/unlock states so i can try to pair who forgot to release lock? is it X? is it drm driver?
Even as of 3.14 final, this happens, 3.15-rc2 right now is too unstable for me to boot into.
I don't use that dGPU much anymore, closing, and probably a lot of fixes have occurred which may have solved this also. I haven't tried a recent 4.8 kernel to confirm, but I still could for fun. closing.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.