Bug 82100 - [snb] GPU HANG: ecode -1:0x00000000 when using Chromium web browser with Xmonad
Summary: [snb] GPU HANG: ecode -1:0x00000000 when using Chromium web browser with Xmonad
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-03 21:51 UTC by Christian Roeder
Modified: 2017-07-03 10:36 UTC (History)
1 user (show)

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


Attachments
Content of /sys/class/drm/card0/error (2.01 MB, text/plain)
2014-08-03 21:51 UTC, Christian Roeder
no flags Details
Xorg.log (59.02 KB, text/plain)
2014-08-03 21:52 UTC, Christian Roeder
no flags Details

Description Christian Roeder 2014-08-03 21:51:54 UTC
Created attachment 103944 [details]
Content of /sys/class/drm/card0/error

The GPU hangs when I use Chromium web browser with the Xmonad window manager. I did not experience that bug with another application so far, nor with GNOME window manager. It also only happens when the external monitor is connected.

The kernel ringbuffer has the following messages:

[152527.227869] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[152527.227871] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[152527.227872] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[152527.227873] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[152527.227873] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[152527.227874] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[152547.208299] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[152551.196393] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[152556.176512] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
[152565.178068] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck wait on render ring, action: continue

Attached please find the file from the sysfs as mentioned in the kernel output.

The version of Xorg as reported in Xorg.log is 1.15.2 and uname -a says:
Linux hostname 3.15.5-2-ARCH #1 SMP PREEMPT Fri Jul 11 07:56:02 CEST 2014 x86_64 GNU/Linux

More information can be found in the attached Xorg.log.
Comment 1 Christian Roeder 2014-08-03 21:52:36 UTC
Created attachment 103945 [details]
Xorg.log
Comment 2 Chris Wilson 2014-12-21 20:09:04 UTC
Maybe this will help

commit d247cb7d0cdb73736f31612157e47f166af68ba0
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Dec 8 10:07:25 2014 +0000

    sna/gen6: Poke PSMI control around WAIT_FOR_EVENT to prevent idling
    
    The bspec recommends preventing the hardware from going to sleep around
    a WAIT_FOR_EVENT, and tells us to use disable sleep bit in PSMI control
    to accomplish this.
    
    References: https://bugs.freedesktop.org/show_bug.cgi?id=62373
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Comment 3 Christian Roeder 2015-07-13 17:38:29 UTC
With current Xorg version 1.15.2 and intel module

[    14.538] (II) Module intel: vendor="X.Org Foundation"
[    14.538]    compiled for 1.15.2, module version = 2.99.912
[    14.538]    Module class: X.Org Video Driver
[    14.538]    ABI class: X.Org Video Driver, version 15.0

I do not see the error anymore. It has been stable for a few months now, so I'd say this bug can be closed. Should you need further information, don't hesitate.
Comment 4 Chris Wilson 2015-07-14 09:14:17 UTC
I hope the PSMI trick has helped. Closing for now, but please reopen if we have further fail. Thanks for the report and update.
Comment 5 Jari Tahvanainen 2017-07-03 10:36:19 UTC
Closing >1 year old resolved+worksforme.


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.