<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - GPU Hangs Abruptly"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107866#c25">Comment # 25</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - GPU Hangs Abruptly"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107866">bug 107866</a>
from <span class="vcard"><a class="email" href="mailto:denys.kostin@globallogic.com" title="Denis <denys.kostin@globallogic.com>"> <span class="fn">Denis</span></a>
</span></b>
<pre>ok... looks like I reproduced the issue with provided apitrace. But I haven't
ideas - how... I mean, that issue is not straight and stable. I launched
browser with an openGL rendering on it (on of the available demo's) - and then
provided trace - maybe for 3 or 5 times.
And, according to the dmesg, I got 1 hang:
[ 7991.390603] powercap intel-rapl:0: package locked by BIOS, monitoring only
[ 8214.539084] perf: interrupt took too long (3142 > 3137), lowering
kernel.perf_event_max_sample_rate to 63500
[ 8360.400165] [drm] GPU HANG: ecode 6:0:0x85fffffc, in glretrace [20413],
reason: hang on rcs0, action: reset
[ 8360.400167] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 8360.400168] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 8360.400168] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 8360.400169] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 8360.400170] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 8360.400214] i915 0000:00:02.0: Resetting chip for hang on rcs0
[ 8456.495729] intel_powerclamp: Start idle injection to reduce power
Investigating</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>