https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #34 from Michel Dänzer michel@daenzer.net --- (In reply to comment #33)
This is the Xorg.0.log file from an instance where I didn't get keyboard/mouse control back at all, and Xorg just chewed up 100% of one CPU instead.
DRICloseScreen is a DRI1 function; I suspect the backtraces in the Xorg log file aren't reliable. It would be interesting to see where the Xorg process is spinning, e.g. by attaching gdb to it and getting a couple of backtraces from it.
(In reply to comment #32)
Perhaps not, but possibly worth asking Mr Greg KH if he'd be prepared to consider it anyway?
Sure, feel free to ask him. :)
Anyway, any GPU resource leaks should be accompanied by 'normal' memory leaks, so valgrind should be the proper tool for the job.