<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [gen3] [drm] GPU HANG: ecode 3:0:7ee06741 in Chrome_InProcGp, hang on rcs0, reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109047">109047</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[gen3] [drm] GPU HANG: ecode 3:0:7ee06741 in Chrome_InProcGp, hang on rcs0, reset
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>minor
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>galkin-vv@ya.ru
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=142794" name="attach_142794" title="/sys/class/drm/card0/error">attachment 142794</a> <a href="attachment.cgi?id=142794&action=edit" title="/sys/class/drm/card0/error">[details]</a></span>
/sys/class/drm/card0/error
After using a chrome-based browser with gles2-based acceleration running for
several weeks with lot of tabs on a machine with small amount of memory the
screen flickers and the gpu hang appeared in dmesg.
>From the user point of view the problem is minor since the gpu recovered
finely, even browser is still working. This is mostly for sharing error state
text for a case that similar problem affects other users with a non-recoverable
hangs.
GPU HANG: ecode 3:0:0x7ee06741, in Chrome_InProcGp [7079], reason: hang on
rcs0, action: reset
System environment:
-- chipset: i945g (82945G/GZ Integrated Graphics Controller 8086:2772)
-- system architecture: 64-bit
-- xf86-video-intel: 2:2.99.917+git20180925-2
-- xserver:2:1.20.3-1
-- mesa:18.2.5-3
-- libdrm:2.4.95-1
-- kernel:4.19.0-rc7-amd64
-- Linux distribution:debian testing
-- Mobo model:DMI: Gigabyte Technology Co., Ltd. GC330UD, BIOS F2 03/17/2009
-- Display connector:d-sub
Browser opera 59.0.3154.0 was started with lots of non-default arguments
including --use-gl=egl that enables glesv2 backend (well, to make it usably
fast on i945)
opera-developer --no-zygote --use-gl=egl --enable-zero-copy
--enable-native-gpu-memory-buffers --disable-gpu-sandbox --in-process-gpu
--ui-disable-partial-swap --ui-enable-zero-copy
--disable-gpu-driver-bug-workarounds
--enable-features=CheckerImaging,UseSkiaRenderer,SkiaDeferredDisplayList
--enable-media-suspend --enable-background-timer-throttling
--enable-prefer-compositing-to-lcd-text --no-sandbox --no-pings
--use-skia-deferred-display-list --use-skia-renderer --renderer-process-limit=1
--limit-fps=15
Actually this bug is on the same physical machine that was
<a class="bz_bug_link
bz_status_CLOSED bz_closed"
title="CLOSED DUPLICATE - i945g gpu hang randomly (at night) after upgrading xserver-xorg-video-intel:i386 2:2.99.917+git20151019-1~exp1 (debian)"
href="show_bug.cgi?id=92732">https://bugs.freedesktop.org/show_bug.cgi?id=92732</a>
The linked bug was 3 years ago with odd mix of 32-bit userspace on 64bit
kernel.
Such mix was crashing every 2-3 weeks.
Now all is 64 bit and MUCH more stable - first hang in 3 months.
So, despite of this bug, generally i945g with gles2 is still in a good shape
with current kernel and mesa from the user point of view.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>