Bug 82095 - [845G] GPU HANG: ecode -1:0x00000000, reason: Command parser error, iir 0x0 0008040, action: continue
Summary: [845G] GPU HANG: ecode -1:0x00000000, reason: Command parser error, iir 0x0 0...
Status: CLOSED WONTFIX
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Daniel Vetter
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-03 14:31 UTC by Dmitry Gorbachev
Modified: 2017-07-24 22:52 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error (675.24 KB, text/plain)
2014-08-03 14:31 UTC, Dmitry Gorbachev
no flags Details
Xorg log (12.87 KB, text/plain)
2014-08-03 14:32 UTC, Dmitry Gorbachev
no flags Details
error #2 (674.62 KB, text/plain)
2014-08-22 08:09 UTC, Dmitry Gorbachev
no flags Details
error #3 (185.15 KB, application/x-gzip)
2014-08-28 06:55 UTC, Dmitry Gorbachev
no flags Details

Description Dmitry Gorbachev 2014-08-03 14:31:15 UTC
Created attachment 103910 [details]
/sys/class/drm/card0/error

Kernel Linux 3.15.7-gnu; distribution Parabola GNU/Linux (xf86-video-intel 2.99.914-1, xorg-server-libre 1.16.0-5, mesa 10.2.4-1, libdrm 2.4.56-1).

From the log:

kernel: Linux agpgart interface v0.103
kernel: agpgart-intel 0000:00:00.0: Intel 845G Chipset
kernel: agpgart-intel 0000:00:00.0: detected gtt size: 131072K total, 131072K mappable
kernel: agpgart-intel 0000:00:00.0: detected 512K stolen memory
kernel: agpgart-intel 0000:00:00.0: AGP aperture is 128M @ 0xe0000000
kernel: [drm] Initialized drm 1.1.0 20060810
kernel: [drm] Memory usable by graphics device = 128M
kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
kernel: [drm] Driver supports precise vblank timestamp query.
kernel: i915 0000:00:02.0: BAR 6: can't assign [??? 0x00000000 flags 0x20000000] (bogus alignment)
kernel: [drm] failed to find VBIOS tables
kernel: vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
kernel: [drm] initialized overlay support
kernel: [drm] Got external EDID base block and 0 extensions from "edid/edid.bin" for connector "VGA-1"
kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
kernel: i915 0000:00:02.0: registered panic notifier
kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

and:

kernel: [drm] GPU HANG: ecode -1:0x00000000, reason: Command parser error, iir 0x00008040, action: continue
kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
kernel: i915: render error detected, EIR: 0x00000010
kernel: [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
kernel: [drm] GPU HANG: ecode -1:0x00000000, reason: Command parser error, iir 0x00008000, action: continue
kernel: i915: render error detected, EIR: 0x00000010

It happens at random.
Comment 1 Dmitry Gorbachev 2014-08-03 14:32:00 UTC
Created attachment 103911 [details]
Xorg log
Comment 2 Dmitry Gorbachev 2014-08-22 08:09:38 UTC
Created attachment 105086 [details]
error #2
Comment 3 Dmitry Gorbachev 2014-08-28 06:55:28 UTC
Created attachment 105372 [details]
error #3
Comment 4 Daniel Vetter 2014-11-04 14:53:59 UTC
So discussed this a bit on irc with Chris and I think we can just ignore these. I've submitted a patch to stop capturing error states for CS error interrupts. There's really not a lot we can do for such old hardware, and we've seen these kinds of issues all over for years, without making any progress.

Presuming the error state is all that's amiss I'll close this as wontfix. Thanks anyway for reporting it, and if you have a functional bug correlated with this then pleasee reopen.


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.