Bug 91403 - Crash dump of Celeron G1610
Summary: Crash dump of Celeron G1610
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-20 14:32 UTC by muumatch
Modified: 2017-07-24 22:46 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error file (2.11 MB, text/plain)
2015-07-20 14:32 UTC, muumatch
no flags Details
/sys/class/drm/card0/error file on kernel 4.0.9 (2.11 MB, text/plain)
2015-07-30 18:28 UTC, muumatch
no flags Details

Description muumatch 2015-07-20 14:32:34 UTC
Created attachment 117256 [details]
/sys/class/drm/card0/error file

Hi.
Sorry,my poor english. I'm not native speaker.

I use Celeron G1610, No graphic board. BIOS display error message.
OS is Debian 8.1

$ dmesg | grep drm

[    0.544867] [drm] Initialized drm 1.1.0 20060810
[    0.598453] [drm] Memory usable by graphics device = 2048M
[    0.598456] [drm] Replacing VGA console driver
[    0.620124] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    0.620126] [drm] Driver supports precise vblank timestamp query.
[    0.772048] [drm] GMBUS [i915 gmbus dpc] timed out, falling back to bit banging on pin 4
[    0.789054] fbcon: inteldrmfb (fb0) is primary device
[    0.817867] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder B
[    0.817868] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder B FIFO underrun
[    0.820201] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    0.850973] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[    1.816415] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[   14.152511] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A
[   23.804031] [drm] stuck on render ring
[   23.804555] [drm] GPU HANG: ecode 0:0x85fffffd, in Xorg [936], reason: Ring hung, action: reset
[   23.804558] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[   23.804560] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[   23.804561] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[   23.804563] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[   23.804564] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[   25.804064] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[   29.804031] [drm] stuck on render ring
[   29.804540] [drm] GPU HANG: ecode 0:0x85fffffd, in Xorg [936], reason: Ring hung, action: reset
[   29.804585] [drm:i915_context_is_banned] *ERROR* gpu hanging too fast, banning!
[   31.804444] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off

glxgears crashed.

$ glxgears 
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
Segmentation fault

mplayer's xv,opengl driver didn't work.
x11 driver is working.

I send these message and /sys/class/drm/card0/error file.
Comment 1 Chris Wilson 2015-07-30 06:49:44 UTC
A very early TLB failure, like

commit 5e4f518959bdf8a4f9c8f80879e4a0f7a95d2cb3
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Feb 13 14:35:59 2015 +0000

    drm/i915: Prevent TLB error on first execution on SNB

Please update your kernel to 4.0 or later.
Comment 2 muumatch 2015-07-30 18:27:31 UTC
Thanks replay.
I updated kernel 4.0.9. But same error occured.
I send /sys/class/drm/card0/error file again.

# dmesg | grep drm
[    0.515061] [drm] Initialized drm 1.1.0 20060810
[    0.570401] [drm] Memory usable by graphics device = 2048M
[    0.570405] [drm] Replacing VGA console driver
[    0.592128] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    0.592130] [drm] Driver supports precise vblank timestamp query.
[    0.605331] [drm] Initialized i915 1.6.0 20150130 for 0000:00:02.0 on minor 0
[    0.728047] [drm] GMBUS [i915 gmbus dpc] timed out, falling back to bit banging on pin 4
[    0.745134] fbcon: inteldrmfb (fb0) is primary device
[    0.774028] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder B
[    0.774052] [drm:cpt_irq_handler [i915]] *ERROR* PCH transcoder B FIFO underrun
[    0.846392] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[   13.796497] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
[   22.816030] [drm] stuck on render ring
[   22.816443] [drm] GPU HANG: ecode 7:0:0x85fffffd, in Xorg [958], reason: Ring hung, action: reset
[   22.816444] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[   22.816445] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[   22.816446] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[   22.816446] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[   22.816447] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[   22.824025] drm/i915: Resetting chip after gpu hang
[   28.804027] [drm] stuck on render ring
[   28.804435] [drm] GPU HANG: ecode 7:0:0x85fffffd, in Xorg [958], reason: Ring hung, action: reset
[   28.804721] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning!
[   28.812035] drm/i915: Resetting chip after gpu hang
Comment 3 muumatch 2015-07-30 18:28:58 UTC
Created attachment 117468 [details]
/sys/class/drm/card0/error file on kernel 4.0.9


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.