<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 - [BDW] drm crashes on newer kernels"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101694">101694</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[BDW] drm crashes on newer kernels
</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>critical
</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>bugger@grr.la
</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=132426" name="attach_132426" title="/sys/class/drm/card0/error">attachment 132426</a> <a href="attachment.cgi?id=132426&action=edit" title="/sys/class/drm/card0/error">[details]</a></span>
/sys/class/drm/card0/error
On newer kernels, Xorg sometimes freezes temporarily. The bug occured on at
least kernels 4.11.8 and 4.12.0, while 4.9.33 did not, after a long while of
intense usage. This indicates that this is a kernel issue, but not necessarily.
chipset: Intel i5-5257U
system architecture: 64-bit
xf86-video-intel: not installed
xserver: 1.19.3
mesa: 17.1.14
libdrm: 2.4.81
kernel: 4.12.0
Linux distribution: Void (with musl libc)
Machine or mobo model: Apple MacBookPro12,1 (2015)
Display connector: internal monitor
Reproduction:
Open chromium and load some intensive web pages. After a while it should freeze
for a few seconds, and later return to normal after some minor graphic
artifacts. This will occur repeatedly indefinitely.
dmesg excerpt:
[ 202.561869] DMAR: DRHD: handling fault status reg 3
[ 202.561874] DMAR: [DMA Write] Request device [00:02.0] fault addr fd285000
[fault reason 23] Unknown
[ 209.700964] [drm] GPU HANG: ecode 8:0:0x85dffffb, in chromium [1064],
reason: Hang on rcs, action: reset
[ 209.700965] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 209.700966] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 209.700966] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 209.700966] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 209.700967] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 209.701011] drm/i915: Resetting chip after gpu hang
[ 219.743979] drm/i915: Resetting chip after gpu hang
[ 229.727960] drm/i915: Resetting chip after gpu hang
[ 229.728133] DMAR: DRHD: handling fault status reg 2
[ 229.728138] DMAR: [DMA Write] Request device [00:02.0] fault addr ffff9000
[fault reason 23] Unknown
[ 241.759968] drm/i915: Resetting chip after gpu hang
[ 249.760012] drm/i915: Resetting chip after gpu hang
[ 249.866657] DMAR: DRHD: handling fault status reg 3
[ 249.866664] DMAR: [DMA Write] Request device [00:02.0] fault addr fbb00000
[fault reason 23] Unknown
[ 259.744063] drm/i915: Resetting chip after gpu hang
[ 269.728105] drm/i915: Resetting chip after gpu hang
[ 448.369227] DMAR: DRHD: handling fault status reg 3
...etc...</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>