Bug 94408 - [HSW] GPU HANG, on Team Fortress, reason: Engine(s) hung
Summary: [HSW] GPU HANG, on Team Fortress, reason: Engine(s) hung
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Ian Romanick
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-05 23:09 UTC by Olivier Sessink
Modified: 2017-02-10 22:39 UTC (History)
1 user (show)

See Also:
i915 platform: HSW
i915 features: GPU hang


Attachments
GPU crash dump saved to /sys/class/drm/card0/error (2.85 MB, text/plain)
2016-03-05 23:09 UTC, Olivier Sessink
Details

Description Olivier Sessink 2016-03-05 23:09:08 UTC
Created attachment 122121 [details]
GPU crash dump saved to /sys/class/drm/card0/error

while playing Team Fortress:

[1386590.432674] [drm] stuck on render ring
[1386590.432692] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[1386590.432695] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[1386590.432706] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[1386590.432713] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[1386590.432715] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[1386590.438564] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0xfb94000 ctx 1) at 0xfb95320
[1386596.430946] [drm] stuck on render ring
[1386602.405246] [drm] stuck on render ring

This is the first time this happened. And I have played this game many times. Could be a cosmic ray hitting the GPU ;-)
Comment 1 Olivier Sessink 2016-03-05 23:12:48 UTC
b.t.w. this is on Ubuntu Trusty

Linux marshall 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

some bits from /var/log/Xorg.log.0

X.Org X Server 1.15.1
Release Date: 2014-04-13
[    10.518] X Protocol Version 11, Revision 0
[    10.518] Build Operating System: Linux 3.2.0-76-generic x86_64 Ubuntu
[    10.518] Current Operating System: Linux marshall 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 2016 x86_64
[    10.518] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic root=UUID=b7a0fa1a-cc54-4226-a4b2-dba2793d81fc ro quiet splash intel_pstate=enable libata.force=noncq vt.handoff=7
[    10.518] Build Date: 12 February 2015  02:49:29PM
[    10.518] xorg-server 2:1.15.1-0ubuntu2.7 (For technical support please see http://www.ubuntu.com/support) 


[    10.583] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
        i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
        915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
        Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
        GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[    10.584] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[    10.584] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[    10.584] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[    10.584] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    10.584] (II) FBDEV: driver for framebuffer: fbdev
[    10.584] (II) VESA: driver for VESA chipsets: vesa
[    10.584] (++) using VT number 7

[    10.585] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 (Timo Aaltonen <tjaalton@debian.org>)

[    10.589] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4600
[    10.589] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2
[    10.589] (II) intel(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[    10.589] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[    10.589] (==) intel(0): RGB weight 888
[    10.589] (==) intel(0): Default visual is TrueColor
[    10.589] (**) intel(0): Framebuffer tiled
[    10.589] (**) intel(0): Pixmaps tiled
[    10.589] (**) intel(0): "Tear free" disabled
[    10.589] (**) intel(0): Forcing per-crtc-pixmaps? no
[    10.589] (II) intel(0): Output VGA1 has no monitor section
[    10.589] (II) intel(0): Output HDMI1 has no monitor section
[    10.589] (II) intel(0): Output HDMI2 has no monitor section
[    10.589] (II) intel(0): Output VIRTUAL1 has no monitor section
[    10.589] (--) intel(0): Output HDMI1 using initial mode 1920x1200 on pipe 0

[    10.595] (II) intel(0): SNA initialized with Haswell (gen7.5, gt2) backend
[    10.595] (==) intel(0): Backing store enabled
[    10.595] (==) intel(0): Silken mouse enabled
[    10.596] (II) intel(0): HW Cursor enabled
[    10.596] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    10.597] (==) intel(0): DPMS enabled
[    10.597] (II) intel(0): [DRI2] Setup complete
[    10.597] (II) intel(0): [DRI2]   DRI driver: i965
[    10.597] (II) intel(0): [DRI2]   VDPAU driver: i965
[    10.597] (II) intel(0): direct rendering: DRI2 Enabled
[    10.597] (==) intel(0): hotplug detection: "enabled"
[    10.597] (--) RandR disabled
[    10.601] (II) SELinux: Disabled on system
[    10.624] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[    10.624] (II) AIGLX: enabled GLX_ARB_create_context
[    10.624] (II) AIGLX: enabled GLX_ARB_create_context_profile
[    10.624] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[    10.624] (II) AIGLX: enabled GLX_INTEL_swap_event
[    10.624] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[    10.624] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[    10.625] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[    10.625] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[    10.625] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[    10.625] (II) AIGLX: Loaded and initialized i965
[    10.625] (II) GLX: Initialized DRI2 GL provider for screen 0
[    10.627] (II) intel(0): switch to mode 1920x1200@60.0 on HDMI1 using pipe 0, position (0, 0), rotation normal, reflection none
[    10.640] (II) intel(0): Setting screen physical size to 508 x 317
Comment 2 yann 2016-09-05 11:08:47 UTC
Not sure about cosmic ray ;) 
Assigning to Mesa product (please let me know if I am mistaken with this GPU Hang).

From this error dump, hung is happening in render ring batch with active head at 0x0fb95320, with 0x7a000003 (PIPE_CONTROL) as IPEHR.

Batch extract (around 0x0fb95320):

0x0fb952fc:      0x780e0000: 3DSTATE_CC_STATE_POINTERS
0x0fb95300:      0x00006381:    pointer to COLOR_CALC_STATE at 0x00006380 (changed)
0x0fb95304:      0x78250000: 3DSTATE_DEPTH_STENCIL_STATE_POINTERS
0x0fb95308:      0x00006341:    pointer to DEPTH_STENCIL_STATE at 0x00006340 (changed)
0x0fb9530c:      0x7a000003: PIPE_CONTROL
0x0fb95310:      0x00100002:    no write, cs stall, stall at scoreboard,
0x0fb95314:      0x00000000:    destination address
0x0fb95318:      0x00000000:    immediate dword low
0x0fb9531c:      0x00000000:    immediate dword high
0x0fb95320:      0x7a000003: PIPE_CONTROL
0x0fb95324:      0x00004000:    qword write,
0x0fb95328:      0x0784f000:    destination address
0x0fb9532c:      0x00000000:    immediate dword low
0x0fb95330:      0x00000000:    immediate dword high
0x0fb95334:      0x790d0002: 3DSTATE_MULTISAMPLE
0x0fb95338:      0x00000000:    dword 1
0x0fb9533c:      0x00000000:    dword 2
0x0fb95340:      0x00000000:    dword 3
Comment 3 yann 2016-11-04 15:22:59 UTC
Please test a new version of Mesa (12 or 13) and mark as REOPENED
if you can reproduce and RESOLVED/* if you cannot reproduce.

If you can reproduce, please capture and upload an apitrace (https://github.com/apitrace/apitrace) so that we can easily 
reproduce as well.
Comment 4 Annie 2017-02-10 22:39:14 UTC
Dear Reporter,

This Mesa bug has been in the "NEEDINFO" status for over 60 days. I am closing this bug based on lack of response but feel free to reopen if resolution is still needed. Please ensure you're supplying the correct information as requested.

Thank you.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.