From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 94900] Regression: HD6950 GPU lockup with octodad: dadliest catch Date: Mon, 11 Apr 2016 21:41:59 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1394595368==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 51E316E282 for ; Mon, 11 Apr 2016 21:41:59 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1394595368== Content-Type: multipart/alternative; boundary="14604109190.bb5c3a0D2.25601"; charset="UTF-8" --14604109190.bb5c3a0D2.25601 Date: Mon, 11 Apr 2016 21:41:59 +0000 MIME-Version: 1.0 Content-Type: text/plain 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. --14604109190.bb5c3a0D2.25601 Date: Mon, 11 Apr 2016 21:41:59 +0000 MIME-Version: 1.0 Content-Type: text/html
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 [details]
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.
--14604109190.bb5c3a0D2.25601-- --===============1394595368== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1394595368==--