https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #5 from Alexandre Demers alexandre.f.demers@gmail.com --- (In reply to Daniel Scharrer from comment #0)
Created attachment 110808 [details] dmesg output with the GPU fault errors filtered out
Running Serious Sam 3 or The Talos Principle spams dmesg with thousands of these errors:
[ 6001.212237] radeon 0000:01:00.0: GPU fault detected: 147 0x02528801 [ 6001.212243] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0FF02192 [ 6001.212246] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x12088001 [ 6001.212249] VM fault (0x01, vmid 9) at page 267395474, read from TC (136)
There are also a few "Packet0 not allowed" errors (followed by a hex dump):
[15446.473341] radeon 0000:01:00.0: Packet0 not allowed!
So far it's only these errors in dmesg - I haven't observed any actual rendering issues, crashes, GPU lockups because of this.
I have only attached a filtered kernel log with the GPU fault errors removed
- the full log is available at http://constexpr.org/tmp/serious-dmesg.log
(140 MiB).
Both of these games use the Serious Engine 3.5 (Serious Sam 3) or 4 (The Talos Principle). This is also reproducible with The Talos Principle Public Test which as of now is still available as a free download on Steam.
Kernel: 3.18.0-gentoo GPU: Radeon HD 7950 Driver: radeonsi, Mesa 10.5.0-devel (git-ff96537)
This might be related to bug 84500 - however those spurious Packet0 have been gone for a while now with updated Mesa - now I got them again but only while running Serious Engine games.
I haven't had a look at the log when launching SS3, but for sure it crashes in no time. It crashes in no time once in a game. It could be related to your bug. However, I think the VM and the Packet 0 are different bugs. I'll have a look in the logs if I get something similar.