Bug 96499 - GPU Hang
Summary: GPU Hang
Status: CLOSED DUPLICATE of bug 95311
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-12 20:07 UTC by Günther Noack
Modified: 2017-07-24 22:41 UTC (History)
2 users (show)

See Also:
i915 platform: BSW/CHT
i915 features: GPU hang


Attachments
/sys/class/drm/card0/error (376.42 KB, text/plain)
2016-06-12 20:07 UTC, Günther Noack
no flags Details
Dmesg (corresponding to the GPU hang memory dump) (79.27 KB, text/plain)
2016-06-12 20:09 UTC, Günther Noack
no flags Details

Description Günther Noack 2016-06-12 20:07:13 UTC
Created attachment 124487 [details]
/sys/class/drm/card0/error

Hardware:
Zotac ZBOX CI323 Nano

User visible symptoms:
After boot up and graphical log in, I can work for about half a minute, and then the screen freezes.

Switching to text mode with Ctrl+Alt+F2 is possible, but it takes a very long time until the screen actually shows the text mode.  (Maybe one or two minutes.)  In text mode things are fluent again.  Switching back to the logged in session, it's still hanging.

This bug is reproducable on this machine and makes graphical log in infeasible.

Software:
Antergos Linux (Arch-based, rolling release).  Ran into the bug for the first time on 2016-06-10, so the corresponding software update probably came in roughly in that week.  (Not using the machine every day.)

Kernel: Linux limbo 4.6.2-1-ARCH #1 SMP PREEMPT Wed Jun 8 08:40:59 CEST 2016 x86_64 GNU/Linux

from dmesg:

[  195.338739] [drm] stuck on render ring
[  195.344643] [drm] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [710], reason: Ring hung, action: reset
[  195.344648] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  195.344650] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  195.344652] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  195.344654] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[  195.344656] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  195.348200] drm/i915: Resetting chip after gpu hang
[  201.338938] [drm] stuck on blitter ring
[  201.345565] [drm] GPU HANG: ecode 8:1:0xfffffffe, in Xorg [710], reason: Ring hung, action: reset
[  201.346064] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning!
[  201.348448] drm/i915: Resetting chip after gpu hang

/sys/class/drm/card0/error is attached to the bug.

*After* the actual screen freeze, there is a longer list of stack traces in dmesg.
(vblank wait timeout, WARN_ON(!lret), ...)
Comment 1 Günther Noack 2016-06-12 20:09:43 UTC
Created attachment 124488 [details]
Dmesg (corresponding to the GPU hang memory dump)

(Here's the dmesg corresponding to the memory dump above)
Comment 2 yann 2016-06-13 07:38:07 UTC
For both bugs:
- Hung happening on "render" ring, 
- Application is "Xorg",
- HW/PCI_ID is "0x22b1", 
- Instruction/IPETH is "0x00000000"
- ACTHD = HEAD (in render ring => not batch)

*** This bug has been marked as a duplicate of bug 95311 ***


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.