<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 - [SKL]GPU HANG: ecode 9:1:0xb0bd8fb5, in systemd-logind [412], reason: Hang on blitter ring, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101289">101289</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[SKL]GPU HANG: ecode 9:1:0xb0bd8fb5, in systemd-logind [412], reason: Hang on blitter ring, action: reset
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg 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>slacker702@gmail.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=131697" name="attach_131697" title="i915 crash dump">attachment 131697</a> <a href="attachment.cgi?id=131697&action=edit" title="i915 crash dump">[details]</a></span>
i915 crash dump
Upon resume from hibernate.
dmesg:
PM: restore of devices complete after 1173.471 msecs
PM: Image restored successfully.
PM: Basic memory bitmaps freed
Restarting tasks ... done.
[drm] RC6 on
e1000e: enp0s31f6 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[drm] GPU HANG: ecode 9:1:0xb0bd8fb5, in systemd-logind [412], reason: Hang on
blitter ring, action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including
userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI ->
DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not
a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always
attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
drm/i915: Resetting chip after gpu hang
[drm] RC6 on
[drm] GuC firmware load skipped
X.Org X Server version: 1.19.3.
OS: Archlinux x86_64
Kernel: Linux 4.9.30-1-lts.
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts
root=UUID=4e2f3394-d315-4384-b975-05e33af1ab06 rw acpi_backlight=none quiet
loglevel=3 rd.systemd.show_status=false rd.udev.log-priority=3
systemd.log_level=err resume=UUID=25e25554-34e4-4d4a-a7f5-81ef2415db94
printk.time=0 splash
Motherboard:
ASRock Z170M Extreme4, BIOS/UEFI AMI P7.20
CPU: Intel Core i3-6100
Display connector: HDMI
lspci:
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev
07)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI
Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal
subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI
#1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller
[AHCI mode] (rev 31)
00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev
f1)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1
(rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9
(rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
(rev 31)
02:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller</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>