[Bug 89936] New: [BSW Regression]Run Cairo Performance case will result GPU HANG: ecode 8:0:0x85dffffb, in X [4370], reason: Ring hung
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Apr 7 04:31:34 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=89936
Bug ID: 89936
Summary: [BSW Regression]Run Cairo Performance case will result
GPU HANG: ecode 8:0:0x85dffffb, in X [4370], reason:
Ring hung
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: wendy.wang at intel.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 114914
--> https://bugs.freedesktop.org/attachment.cgi?id=114914&action=edit
GPU_HANG_dmesg_cairo_case
System Environment:
--------------------
Failed Platform: Braswell
Kernel Regression: Yes,
but cannot bisect because of the bug between the good and bad commit.
89350 [BSW bisected] kernel fails to start up
Kernel:
Good commit: drm-intel-nightly branch 2015-02-10 kernel
Bad commit: drm-intel-nightly branch from 2015-03-10 to the latest kernel
commit
Description:
Run cairo performance, check dmesg will see GPU HANG error message:
GPU HANG: ecode 8:0:0x85dffffb, in X [4370], reason: Ring hung, action: reset
[ 119.815835] [drm:i915_reset_and_wakeup] resetting chip
[ 119.815956] [drm:i915_context_is_banned [i915]] *ERROR* gpu hanging too
fast, banning!
[ 119.817187] drm/i915: Resetting chip after gpu hang
Dmesg file has been attached.
Reproduce Steps:
1. cd /home/cairo/perf
2. vblank_mode=0 CAIRO_TEST_TARGET=xlib ./cairo-perf-trace
/home/cairo-traces/benchmark/firefox-chalkboard.trace
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150407/40ed095f/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list