Created attachment 82479 [details] dmesg output I've noticed a kernel BUG/Oops during a GPU stall when playing Legend of Grimrock (closed source). The oops causes X to become a defunct process with no entires in the Xorg.log file. The screen goes into standby mode and the only way to solve this is to reboot the computer. The machine is responsive via ssh and I've attached my dmesg output after the oops. I have not played this game with another kernel, so I don't know if it's new or not. I have a Radeon HD 4850, on an Intel Core2Duo with 8GB of ram. Running 'latest' git (gb616d01).
What version of mesa are you using? Does disabling hyperz help? Set env var R600_DEBUG=nohyperz (git) or R600_HYPERZ=0 (older mesa releases).
Also, if this is a 32-bit game running on a 64-bit distro, make sure you have a recent version of the 32-bit 3D driver.
Yes it is, both the 32 bit and the 64 bit are compiled from the same commit.
This might be due to a overheat issue. I just got another GPU lockup while playing the game (after a few hours) and it did not cause the kernel OOPS/Bug in question, so everything went on as normal after the GPU recovered. However, after a few minutes I lost the display (it went black). Logging in over SSH and checking the temperature sensor revealed that the radeon GPU reported 127.5C. So unless someone else has seen this issue, I think it can be discarded.
-- 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/mesa/mesa/issues/452.
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.