From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93436] [radeonsi][regression] GPUVM faults playing ARK: Survival Evolved, started 4.4-rc3, -rc5 is worse
Date: Fri, 18 Dec 2015 07:58:05 +0000 [thread overview]
Message-ID: <bug-93436-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2532 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93436
Bug ID: 93436
Summary: [radeonsi][regression] GPUVM faults playing ARK:
Survival Evolved, started 4.4-rc3, -rc5 is worse
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: shawn.starr@rogers.com
Kernel is spamming non-fatal GPU VM faults:
[ 8792.444427] VM fault (0x02, vmid 5) at page 600320, read from 'TC2'
(0x54433200) (72)
[ 8792.475656] radeon 0000:01:00.0: GPU fault detected: 147 0x000a4802
[ 8792.475976] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00092900
[ 8792.476343] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A048002
[ 8792.476718] VM fault (0x02, vmid 5) at page 600320, read from 'TC2'
(0x54433200) (72)
[ 8792.505901] radeon 0000:01:00.0: GPU fault detected: 147 0x000a4802
[ 8792.506232] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00092900
[ 8792.506596] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A048002
[ 8792.506970] VM fault (0x02, vmid 5) at page 600320, read from 'TC2'
(0x54433200) (72)
[ 8792.537730] radeon 0000:01:00.0: GPU fault detected: 147 0x000a4802
[ 8792.538049] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00092900
[ 8792.538416] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A048002
[ 8792.538783] VM fault (0x02, vmid 5) at page 600320, read from 'TC2'
(0x54433200) (72)
[ 8792.567524] radeon 0000:01:00.0: GPU fault detected: 147 0x000a4802
[ 8792.567849] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00092900
[ 8792.568216] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A048002
[ 8792.568586] VM fault (0x02, vmid 5) at page 600320, read from 'TC2'
(0x54433200) (72)
[ 8795.015367] radeon 0000:01:00.0: GPU fault detected: 147 0x0c0a4802
[ 8795.015698] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x000928E0
[ 8795.016065] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A048002
[ 8795.016438] VM fault (0x02, vmid 5) at page 600288, read from 'TC2'
(0x54433200) (72)
...
Mesa from git master: 2015-12-11
kernel: 4.4.0-0.rc5.git1.2.fc24.x86_64
Can I use the new debugging in mesa to capture what is causing fault?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3789 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:[~2015-12-18 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 7:58 bugzilla-daemon [this message]
2015-12-18 15:09 ` [Bug 93436] [radeonsi][regression] GPUVM faults playing ARK: Survival Evolved, started 4.4-rc3, -rc5 is worse bugzilla-daemon
2015-12-18 23:58 ` bugzilla-daemon
2015-12-19 1:50 ` bugzilla-daemon
2015-12-19 7:22 ` bugzilla-daemon
2015-12-19 10:38 ` 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-93436-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.