From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 87278] Packet0 not allowed and GPU fault detected errors with Serious Engine games
Date: Sat, 13 Dec 2014 10:38:05 +0000 [thread overview]
Message-ID: <bug-87278-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2070 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=87278
Bug ID: 87278
Summary: Packet0 not allowed and GPU fault detected errors with
Serious Engine games
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: daniel@constexpr.org
Created attachment 110808
--> https://bugs.freedesktop.org/attachment.cgi?id=110808&action=edit
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3722 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-12-13 10:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 10:38 bugzilla-daemon [this message]
2014-12-13 10:39 ` [Bug 87278] Packet0 not allowed and GPU fault detected errors with Serious Engine games bugzilla-daemon
2014-12-13 18:45 ` bugzilla-daemon
2014-12-16 8:48 ` bugzilla-daemon
2014-12-16 8:56 ` bugzilla-daemon
2014-12-17 5:52 ` bugzilla-daemon
2014-12-17 9:39 ` bugzilla-daemon
2014-12-17 10:34 ` bugzilla-daemon
2014-12-19 3:36 ` bugzilla-daemon
2014-12-19 3:39 ` bugzilla-daemon
2014-12-19 11:13 ` bugzilla-daemon
2014-12-19 13:32 ` bugzilla-daemon
2014-12-28 16:29 ` bugzilla-daemon
2014-12-28 16:30 ` bugzilla-daemon
2014-12-30 5:15 ` bugzilla-daemon
2015-01-05 7:14 ` bugzilla-daemon
2015-01-05 8:16 ` bugzilla-daemon
2015-02-07 13:36 ` bugzilla-daemon
2015-02-07 14:56 ` bugzilla-daemon
2015-02-07 15:57 ` bugzilla-daemon
2015-02-07 19:48 ` bugzilla-daemon
2015-02-07 23:08 ` bugzilla-daemon
2015-02-08 10:18 ` bugzilla-daemon
2015-02-18 18:26 ` bugzilla-daemon
2015-02-19 15:44 ` bugzilla-daemon
2015-03-10 18:59 ` bugzilla-daemon
2015-03-31 22:33 ` bugzilla-daemon
2015-04-01 2:08 ` bugzilla-daemon
2015-04-01 11:54 ` bugzilla-daemon
2015-04-01 11:55 ` bugzilla-daemon
2015-05-08 23:09 ` bugzilla-daemon
2015-08-01 18:38 ` bugzilla-daemon
2018-08-09 17:35 ` bugzilla-daemon
2019-09-25 17:51 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-87278-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox