[Bug 91278] Tonga GPU lock/reset fail with Unigine Valley
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Jul 17 02:30:42 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=91278
--- Comment #3 from Andy Furniss <adf.lists at gmail.com> ---
I've of course tried various things sine reporting - Valley doesn't always
instantly lock. Unreal 4.5 Elemental got half way before locking.
Perhaps more interesting I managed to reset/fail resume just browsing - of
course I've done a lot of browsing without issue so far. The difference this
time was I had a huge ffmpeg/x265 encode going - it was using all my memory (8
Gig and swap had been used a bit), so it's possible memory pressure plays a
role - or maybe just a red herring :-)
I haven't managed to get a reset running timedemos on openarena or xonotic so
far - will try with memory pressure as time allows.
The reset when browsing -
-rw-rw-r-- 1 andy andy 153K Jun 13 00:04 hacky-fix.jpeg
[ 8052.101670] amdgpu 0000:01:00.0: GPU lockup (waiting for 0x000000000000f019
last fence id 0x000000000000f018 on ring 9)
[ 8052.101672] amdgpu 0000:01:00.0: failed to sync rings (-35)
[ 8052.108912] amdgpu 0000:01:00.0: Saved 9216 dwords of commands on ring 9.
[ 8052.108929] amdgpu 0000:01:00.0: GPU softreset: 0x00000100
[ 8052.108930] amdgpu 0000:01:00.0: GRBM_STATUS=0x00003028
[ 8052.108932] amdgpu 0000:01:00.0: GRBM_STATUS2=0x00000008
[ 8052.108934] amdgpu 0000:01:00.0: GRBM_STATUS_SE0=0x00000006
[ 8052.108935] amdgpu 0000:01:00.0: GRBM_STATUS_SE1=0x00000006
[ 8052.108937] amdgpu 0000:01:00.0: GRBM_STATUS_SE2=0x00000006
[ 8052.108938] amdgpu 0000:01:00.0: GRBM_STATUS_SE3=0x00000006
[ 8052.108940] amdgpu 0000:01:00.0: SRBM_STATUS=0x20020240
[ 8052.108941] amdgpu 0000:01:00.0: SRBM_STATUS2=0x00000080
[ 8052.108943] amdgpu 0000:01:00.0: SDMA0_STATUS_REG = 0x76DEED57
[ 8052.108945] amdgpu 0000:01:00.0: SDMA1_STATUS_REG = 0x46DEED57
[ 8052.108946] amdgpu 0000:01:00.0: CP_STAT = 0x00000000
[ 8052.108948] amdgpu 0000:01:00.0: CP_STALLED_STAT1 = 0x00000c00
[ 8052.108949] amdgpu 0000:01:00.0: CP_STALLED_STAT2 = 0x00000000
[ 8052.108951] amdgpu 0000:01:00.0: CP_STALLED_STAT3 = 0x00000000
[ 8052.108953] amdgpu 0000:01:00.0: CP_CPF_BUSY_STAT = 0x00000000
[ 8052.108954] amdgpu 0000:01:00.0: CP_CPF_STALLED_STAT1 = 0x00000000
[ 8052.108956] amdgpu 0000:01:00.0: CP_CPF_STATUS = 0x00000000
[ 8052.108957] amdgpu 0000:01:00.0: CP_CPC_BUSY_STAT = 0x00000000
[ 8052.108959] amdgpu 0000:01:00.0: CP_CPC_STALLED_STAT1 = 0x00000000
[ 8052.108961] amdgpu 0000:01:00.0: CP_CPC_STATUS = 0x00000000
[ 8052.108962] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 8052.108964] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 8052.109078] amdgpu 0000:01:00.0: SRBM_SOFT_RESET=0x00000400
[ 8052.110233] amdgpu 0000:01:00.0: GRBM_STATUS=0x00003028
[ 8052.110235] amdgpu 0000:01:00.0: GRBM_STATUS2=0x00000008
[ 8052.110236] amdgpu 0000:01:00.0: GRBM_STATUS_SE0=0x00000006
[ 8052.110238] amdgpu 0000:01:00.0: GRBM_STATUS_SE1=0x00000006
[ 8052.110239] amdgpu 0000:01:00.0: GRBM_STATUS_SE2=0x00000006
[ 8052.110241] amdgpu 0000:01:00.0: GRBM_STATUS_SE3=0x00000006
[ 8052.110242] amdgpu 0000:01:00.0: SRBM_STATUS=0x20020040
[ 8052.110244] amdgpu 0000:01:00.0: SRBM_STATUS2=0x00000080
[ 8052.110245] amdgpu 0000:01:00.0: SDMA0_STATUS_REG = 0x76DEED57
[ 8052.110247] amdgpu 0000:01:00.0: SDMA1_STATUS_REG = 0x46DEED57
[ 8052.110248] amdgpu 0000:01:00.0: CP_STAT = 0x00000000
[ 8052.110250] amdgpu 0000:01:00.0: CP_STALLED_STAT1 = 0x00000c00
[ 8052.110252] amdgpu 0000:01:00.0: CP_STALLED_STAT2 = 0x00000000
[ 8052.110253] amdgpu 0000:01:00.0: CP_STALLED_STAT3 = 0x00000000
[ 8052.110255] amdgpu 0000:01:00.0: CP_CPF_BUSY_STAT = 0x00000000
[ 8052.110256] amdgpu 0000:01:00.0: CP_CPF_STALLED_STAT1 = 0x00000000
[ 8052.110258] amdgpu 0000:01:00.0: CP_CPF_STATUS = 0x00000000
[ 8052.110259] amdgpu 0000:01:00.0: CP_CPC_BUSY_STAT = 0x00000000
[ 8052.110261] amdgpu 0000:01:00.0: CP_CPC_STALLED_STAT1 = 0x00000000
[ 8052.110262] amdgpu 0000:01:00.0: CP_CPC_STATUS = 0x00000000
[ 8052.110282] amdgpu 0000:01:00.0: GPU reset succeeded, trying to resume
[ 8052.110289] [drm] probing gen 2 caps for device 1002:5a16 = 31cd02/0
[ 8052.111446] [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000).
[ 8052.113940] [drm] ring test on 0 succeeded in 10 usecs
[ 8053.856277] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 1
test failed (scratch(0xC040)=0xCAFEDEAD)
[ 8054.049187] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 2
test failed (scratch(0xC040)=0xCAFEDEAD)
[ 8054.242101] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 3
test failed (scratch(0xC040)=0xCAFEDEAD)
[ 8054.435020] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 4
test failed (scratch(0xC040)=0xCAFEDEAD)
[ 8054.627925] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 5
test failed (scratch(0xC040)=0xCAFEDEAD)
[ 8054.820839] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 6
test failed (scratch(0xC040)=0xCAFEDEAD)
[ 8055.013737] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 7
test failed (scratch(0xC040)=0xCAFEDEAD)
[ 8055.206669] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 8
test failed (scratch(0xC040)=0xCAFEDEAD)
[ 8055.313826] [drm:sdma_v3_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 9
test failed (0xCAFEDEAD)
[ 8055.319862] amdgpu 0000:01:00.0: GPU reset failed
[ 8055.320787] amdgpu 0000:01:00.0: couldn't schedule ib
[ 8055.320806] [drm:amdgpu_gem_va_ioctl [amdgpu]] *ERROR* Couldn't update BO_VA
(-22)
[ 8055.320831] amdgpu 0000:01:00.0: couldn't schedule ib
[ 8055.320841] [drm:amdgpu_gem_va_ioctl [amdgpu]] *ERROR* Couldn't update BO_VA
(-22)
[ 8055.320854] amdgpu 0000:01:00.0: couldn't schedule ib
[ 8055.320863] [drm:amdgpu_gem_va_ioctl [amdgpu]] *ERROR* Couldn't update BO_VA
(-22)
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150717/bd8ae2d5/attachment.html>
More information about the dri-devel
mailing list