[Bug 96175] [SKL GT4e] 3D game nexuiz 1.6.1 causes GPU HANG
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Jul 18 05:43:50 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=96175
--- Comment #17 from Terrence Xu <terrence.xu at intel.com> ---
Hello mwa,
The bad news is I also reproduced this issue after I downloaded the guc
firmware and enabled it in i915.
The error log as below:
[ 252.697245] [drm] GPU HANG: ecode 9:0:0xfffffffe, in nexuiz-linux-x8 [2970],
reason: Hang on render ring, action: reset
[ 252.697247] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 252.697248] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 252.697249] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 252.697250] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 252.697251] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 252.697272] [drm:i915_reset_and_wakeup] resetting chip
[ 252.697282] drm/i915: Resetting chip after gpu hang
[ 252.697316] [drm:gen8_init_common_ring] Execlists enabled for render ring
[ 252.697334] [drm:gen8_init_common_ring] Execlists enabled for blitter ring
[ 252.697349] [drm:gen8_init_common_ring] Execlists enabled for bsd ring
[ 252.697363] [drm:gen8_init_common_ring] Execlists enabled for bsd2 ring
[ 252.697378] [drm:gen8_init_common_ring] Execlists enabled for video
enhancement ring
[ 252.697408] [drm:intel_guc_setup] GuC fw status: path
i915/skl_guc_ver6_1.bin, fetch SUCCESS, load SUCCESS
[ 252.697411] [drm:intel_guc_setup] GuC fw status: fetch SUCCESS, load PENDING
[ 252.698532] [drm:guc_ucode_xfer_dma] DMA status 0x10, GuC status 0x8002f0ec
[ 252.698534] [drm:guc_ucode_xfer_dma] returning 0
[ 252.698536] [drm:intel_guc_setup] GuC fw status: fetch SUCCESS, load SUCCESS
[ 252.698550] [drm:select_doorbell_register] assigned normal priority doorbell
id 0x0
[ 252.698551] [drm:select_doorbell_cacheline] selected doorbell cacheline
0x40, next 0x80, linesize 64
[ 252.698559] [drm:guc_client_alloc] new priority 2 client ffff8804898d9280:
ctx_index 0
[ 252.698560] [drm:guc_client_alloc] doorbell id 0, cacheline offset 0x40
[ 254.696694] [drm] RC6 on
[ 262.695933] [drm:i915_reset_and_wakeup] resetting chip
[ 262.695944] drm/i915: Resetting chip after gpu hang
[ 262.697760] [drm:gen8_init_common_ring] Execlists enabled for render ring
[ 262.697787] [drm:gen8_init_common_ring] Execlists enabled for blitter ring
[ 262.697808] [drm:gen8_init_common_ring] Execlists enabled for bsd ring
[ 262.697828] [drm:gen8_init_common_ring] Execlists enabled for bsd2 ring
[ 262.697847] [drm:gen8_init_common_ring] Execlists enabled for video
enhancement ring
[ 262.697882] [drm:intel_guc_setup] GuC fw status: path
i915/skl_guc_ver6_1.bin, fetch SUCCESS, load SUCCESS
[ 262.697886] [drm:intel_guc_setup] GuC fw status: fetch SUCCESS, load PENDING
[ 262.701710] [drm:guc_ucode_xfer_dma] DMA status 0x10, GuC status 0x8002f0ec
[ 262.701713] [drm:guc_ucode_xfer_dma] returning 0
[ 262.701715] [drm:intel_guc_setup] GuC fw status: fetch SUCCESS, load SUCCESS
[ 262.701729] [drm:select_doorbell_register] assigned normal priority doorbell
id 0x0
[ 262.701730] [drm:select_doorbell_cacheline] selected doorbell cacheline
0x80, next 0xc0, linesize 64
[ 262.703708] [drm:guc_client_alloc] new priority 2 client ffff8804898d9280:
ctx_index 0
[ 262.703710] [drm:guc_client_alloc] doorbell id 0, cacheline offset 0x80
The guc status as below:
root at igvt-1604:/sys/kernel/debug/dri/0# cat i915_guc_load_status
GuC firmware status:
path: i915/skl_guc_ver6_1.bin
fetch: SUCCESS
load: SUCCESS
version wanted: 6.1
version found: 6.1
header: offset is 0; size = 128
uCode: offset is 128; size = 128640
RSA: offset is 128768; size = 256
GuC status 0x800300ec:
Bootrom status = 0x76
uKernel status = 0x0
MIA Core status = 0x3
Scratch registers:
0: 0xf0000000
1: 0x0
2: 0x0
3: 0x5f5e100
4: 0x600
5: 0x0
6: 0x0
7: 0x8
8: 0x3
9: 0xd4a00
10: 0x0
11: 0x0
12: 0x0
13: 0x0
14: 0x0
15: 0x0
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160718/557802ad/attachment.html>
More information about the intel-gfx-bugs
mailing list