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: Thu, 09 Aug 2018 17:35:20 +0000 [thread overview]
Message-ID: <bug-87278-502-Ypsy9iE7BN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-87278-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1312 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=87278
Julien Isorce <julien.isorce@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #31 from Julien Isorce <julien.isorce@gmail.com> ---
I (In reply to Marek Olšák from comment #17)
> This seems to be fixed with current Mesa git. Can you confirm?
It looks like it is not fixed in mesa git as I can reproduce it with the
apitrace in comment #c29 with Cap Verde, radeon driver, mesa 18+, kernel
4.15.0-15-generic, LLVM 7.0.0, xorg 1.20.99.1, xf86-video-ati 18.0.1.
(same result with kernel 4.4, mesa 12.0.6, llvm 3)
radeon 0000:08:00.0: GPU fault detected: 146 0x0d64520c
radeon 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001196EB
radeon 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0405200C
VM fault (0x0c, vmid 2) at page 1152747, read from CB_CMASK (82)
I always get the errors above and sometimes I get the gpu lockup and also
sometimes the Packet0 not allowed!.
The possible fix in #c10 does not help.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2927 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-08-09 17:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 10:38 [Bug 87278] Packet0 not allowed and GPU fault detected errors with Serious Engine games bugzilla-daemon
2014-12-13 10:39 ` 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 [this message]
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-Ypsy9iE7BN@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