<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 - Hard lockup (Freeze)/GPU HANG: ecode 9:1:0xfffffffe with Skylake"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109949">109949</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Hard lockup (Freeze)/GPU HANG: ecode 9:1:0xfffffffe with Skylake
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI git
</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>normal
</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>borrowck@protonmail.com
</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=143604" name="attach_143604" title="kernel dmesg before freeze">attachment 143604</a> <a href="attachment.cgi?id=143604&action=edit" title="kernel dmesg before freeze">[details]</a></span>
kernel dmesg before freeze
I am not sure how to 100% reproduce this, but in my case, by opening ~30
chromium tabs with youtube videos running should cause a hard lockup, aka
system/xorg freezes, music hangs too with repeating audio chunks,
sysrq/ping/network/netconsole/ssh doesn't work.
The only dmesg I could recover contained something like this:
[ 174.026397] i915 0000:00:02.0: GPU HANG: ecode 9:1:0xfffffffe, in [0], hang
on rcs0
[ 174.026403] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 174.026406] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 174.026407] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 174.026409] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 174.026411] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 174.027425] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 174.028043] i915 0000:00:02.0: Resetting chip for hang on rcs0
Well, I am not exactly sure how I should continue debugging this because it's
basically a hard-lockup.
Note: I am not sure when it started but I've been having this issue for quite
some time (This also occurred with 4.18.x, and perhaps even before that,
although I can't quite remember when it started).
System info:
CPU: Intel i7-6700K (Not overclocked)
Kernel: Linux - 5.0.0-arch1-2-ARCH-02093-g2988dab1bd13 #1 SMP PREEMPT Sat Mar 9
22:56:40 CET 2019 x86_64 GNU/Linux (drm-tip/
24962f1aef49db97e09c7942157a2dbc973b546b)
Distro: Arch Linux
Display Connector: eDP
chromium: 72.0.3626.121 (with hw accel enabled + intel-hybrid-driver)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>