[Bug 83341] [HSW]igt/gem_reset_stats sporadically causes poweroff
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Nov 7 00:07:14 PST 2014
https://bugs.freedesktop.org/show_bug.cgi?id=83341
--- Comment #3 from lu hua <huax.lu at intel.com> ---
Created attachment 109077
--> https://bugs.freedesktop.org/attachment.cgi?id=109077&action=edit
dmesg2
this cycle doesn't keep "Stopping rings 0xc0000004"
[ 58.788774] gem_reset_stats: starting subtest ban-ctx-render
[ 58.789340] [drm:i915_gem_open]
[ 58.789919] [drm:i915_gem_open]
[ 58.790456] [drm:i915_gem_context_create_ioctl] HW context 1 created
[ 58.791006] [drm:i915_gem_context_create_ioctl] HW context 2 created
[ 58.791660] [drm:i915_ring_stop_set] Stopping rings 0x80000001
[ 60.781089] [drm:intel_print_rc6_info] Enabling RC6 states: RC6 on
[ 60.785104] [drm:gen6_enable_rps] Overclocking supported. Max: 1250MHz,
Overclock max: 1250MHz
[ 64.776617] [drm] stuck on render ring
[ 64.777852] [drm] GPU HANG: ecode 0:0xe757ffff, in gem_reset_stats [4130],
reason: Ring hung, action: reset
[ 64.778547] [drm:i915_error_work_func] resetting chip
[ 64.780645] [drm] Simulated gpu hang, resetting stop_rings
[ 64.781337] drm/i915: Resetting chip after gpu hang
[ 64.782045] [drm:init_status_page] render ring hws offset: 0x001a1000
[ 64.784654] [drm:init_status_page] bsd ring hws offset: 0x001c3000
[ 64.785417] [drm:init_status_page] blitter ring hws offset: 0x001e4000
[ 64.786194] [drm:init_status_page] video enhancement ring hws offset:
0x00205000
[ 64.787052] [drm:i915_ring_stop_set] Stopping rings 0x80000001
[ 66.778421] [drm:intel_print_rc6_info] Enabling RC6 states: RC6 on
[ 66.781311] [drm:gen6_enable_rps] Overclocking supported. Max: 1250MHz,
Overclock max: 1250MHz
--
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/20141107/18c6e7cc/attachment.html>
More information about the intel-gfx-bugs
mailing list