From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94900] Regression: HD6950 GPU lockup with octodad: dadliest catch
Date: Mon, 11 Apr 2016 21:41:59 +0000 [thread overview]
Message-ID: <bug-94900-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3550 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94900
Bug ID: 94900
Summary: Regression: HD6950 GPU lockup with octodad: dadliest
catch
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: dan.g.tob@gmail.com
Created attachment 122873
--> https://bugs.freedesktop.org/attachment.cgi?id=122873&action=edit
dmesg
I Am seeing gpu lockups trying to launch octodad: dadliest catch with a radeon
HD6950 on steam. It was working before but its been a few months since I've
last tried to launch it. Both mesa and kernel have been updated since it was
last working.
kernel 4.4->4.5 mesa 11.1->11.2. Possibly libdrm updates too.
[ 267.335354] radeon 0000:02:00.0: ring 0 stalled for more than 10416msec
[ 267.335364] radeon 0000:02:00.0: GPU lockup (current fence id
0x000000000000821e last fence id 0x0000000000008229 on ring 0)
[ 267.444949] radeon 0000:02:00.0: Saved 335 dwords of commands on ring 0.
[ 267.445029] radeon 0000:02:00.0: GPU softreset: 0x00000009
[ 267.445031] radeon 0000:02:00.0: GRBM_STATUS = 0xE77E4828
[ 267.445032] radeon 0000:02:00.0: GRBM_STATUS_SE0 = 0xFF800001
[ 267.445033] radeon 0000:02:00.0: GRBM_STATUS_SE1 = 0xFF800001
[ 267.445034] radeon 0000:02:00.0: SRBM_STATUS = 0x200000C0
[ 267.445101] radeon 0000:02:00.0: SRBM_STATUS2 = 0x00000000
[ 267.445102] radeon 0000:02:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[ 267.445103] radeon 0000:02:00.0: R_008678_CP_STALLED_STAT2 = 0x00018000
[ 267.445104] radeon 0000:02:00.0: R_00867C_CP_BUSY_STAT = 0x00008006
[ 267.445106] radeon 0000:02:00.0: R_008680_CP_STAT = 0x80038647
[ 267.445107] radeon 0000:02:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 267.445108] radeon 0000:02:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
[ 267.445109] radeon 0000:02:00.0: VM_CONTEXT0_PROTECTION_FAULT_ADDR
0x00000000
[ 267.445111] radeon 0000:02:00.0: VM_CONTEXT0_PROTECTION_FAULT_STATUS
0x00000000
[ 267.445112] radeon 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 267.445113] radeon 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 267.461656] radeon 0000:02:00.0: GRBM_SOFT_RESET=0x0000DF7B
[ 267.461709] radeon 0000:02:00.0: SRBM_SOFT_RESET=0x00000100
[ 267.462863] radeon 0000:02:00.0: GRBM_STATUS = 0x00003828
[ 267.462864] radeon 0000:02:00.0: GRBM_STATUS_SE0 = 0x00000007
[ 267.462866] radeon 0000:02:00.0: GRBM_STATUS_SE1 = 0x00000007
[ 267.462867] radeon 0000:02:00.0: SRBM_STATUS = 0x200000C0
[ 267.462933] radeon 0000:02:00.0: SRBM_STATUS2 = 0x00000000
[ 267.462934] radeon 0000:02:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
[ 267.462935] radeon 0000:02:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
[ 267.462937] radeon 0000:02:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
[ 267.462938] radeon 0000:02:00.0: R_008680_CP_STAT = 0x00000000
[ 267.462939] radeon 0000:02:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
[ 267.462940] radeon 0000:02:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
[ 267.463016] radeon 0000:02:00.0: GPU reset succeeded, trying to resume
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4877 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 reply other threads:[~2016-04-11 21:41 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 21:41 bugzilla-daemon [this message]
2016-04-11 22:52 ` [Bug 94900] HD6950 GPU lockup with octodad: dadliest catch bugzilla-daemon
2016-04-11 22:53 ` bugzilla-daemon
2016-04-15 3:49 ` bugzilla-daemon
2016-05-03 11:05 ` [Bug 94900] HD6950 GPU lockup with various steam games (octodad, saints row 4) bugzilla-daemon
2016-05-03 11:06 ` bugzilla-daemon
2016-05-04 21:23 ` bugzilla-daemon
2016-05-06 11:37 ` bugzilla-daemon
2016-05-06 11:38 ` bugzilla-daemon
2016-05-06 19:30 ` bugzilla-daemon
2016-05-06 20:32 ` bugzilla-daemon
2016-05-16 9:05 ` bugzilla-daemon
2016-05-16 9:05 ` [Bug 94900] HD6950 GPU lockup loop with various steam games (octodad, saints row 4, grid autosport) bugzilla-daemon
2016-05-16 10:00 ` bugzilla-daemon
2016-06-06 11:57 ` bugzilla-daemon
2016-06-06 11:58 ` bugzilla-daemon
2016-07-12 22:21 ` bugzilla-daemon
2016-07-13 12:06 ` bugzilla-daemon
2016-07-16 1:50 ` bugzilla-daemon
2016-07-16 10:51 ` bugzilla-daemon
2016-07-16 13:53 ` bugzilla-daemon
2016-07-16 14:18 ` [Bug 94900] HD6950 GPU lockup loop with various steam games (octodad, saints row 4, dead island, " bugzilla-daemon
2016-07-16 16:20 ` bugzilla-daemon
2016-07-16 16:20 ` bugzilla-daemon
2016-07-16 16:26 ` [Bug 94900] HD6950 GPU lockup loop with various steam games (octodad[always], saints row 4[always], dead island[always], grid autosport[sometimes]) bugzilla-daemon
2016-07-17 21:36 ` bugzilla-daemon
2016-07-18 9:04 ` bugzilla-daemon
2016-07-18 10:26 ` bugzilla-daemon
2016-07-23 8:43 ` bugzilla-daemon
2016-09-02 8:11 ` bugzilla-daemon
2016-09-09 4:52 ` bugzilla-daemon
2016-09-17 20:23 ` bugzilla-daemon
2016-09-18 15:37 ` bugzilla-daemon
2016-09-22 14:59 ` bugzilla-daemon
2016-09-23 7:35 ` bugzilla-daemon
2016-09-28 17:26 ` bugzilla-daemon
2016-09-28 17:40 ` bugzilla-daemon
2016-10-02 10:07 ` bugzilla-daemon
2016-10-02 10:13 ` bugzilla-daemon
2016-10-02 10:29 ` bugzilla-daemon
2016-10-04 15:47 ` bugzilla-daemon
2016-10-30 9:11 ` bugzilla-daemon
2016-12-16 13:32 ` bugzilla-daemon
2016-12-22 8:37 ` bugzilla-daemon
2017-01-12 10:53 ` 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-94900-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