From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 84147] New: (piglit) gl-3.0-multidrawarrays-vertexid produce GPU fault
Date: Sun, 21 Sep 2014 21:39:11 +0000 [thread overview]
Message-ID: <bug-84147-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1186 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=84147
Priority: medium
Bug ID: 84147
Assignee: dri-devel@lists.freedesktop.org
Summary: (piglit) gl-3.0-multidrawarrays-vertexid produce GPU
fault
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: smoki00790@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
Running piglit test on Kabini:
./bin/gl-3.0-multidrawarrays-vertexid -auto
test fail and produce:
[ 9372.705357] radeon 0000:00:01.0: GPU fault detected: 147 0x07c52002
[ 9372.705366] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x0000103E
[ 9372.705370] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x05020002
[ 9372.705374] VM fault (0x02, vmid 2) at page 4158, write from 'TC0'
(0x54433000) (32)
Guess but maybe something like intel do recently in
927f5db46135b3eb63f401833b1e40a3be9ca4e0 and before that is needed for
radeonsi.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2480 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-09-21 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 21:39 bugzilla-daemon [this message]
2014-09-22 6:59 ` [Bug 84147] (piglit) gl-3.0-multidrawarrays-vertexid produce GPU fault bugzilla-daemon
2015-01-31 15:38 ` bugzilla-daemon
2015-01-31 15:39 ` 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-84147-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;
as well as URLs for NNTP newsgroup(s).