<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 - GGPU HANG: ecode 9:0:0x00000000, reason: No progress on rcs0, bcs0, vcs0, vecs0, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104446">104446</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GGPU HANG: ecode 9:0:0x00000000, reason: No progress on rcs0, bcs0, vcs0, vecs0, 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>blocker
</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>rvprasad@ksu.edu
</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>I have PopOS (Ubuntu artful) installed with kernel 4.14.0-041400-generic
#201711122031 on a System76 laptop with Intel i915 integrated GPU (519b) and
NVidia 1070 (driver v387.26). When I enable "MSHYBRID" option in BIOS, the
screen goes blank upon booting and stays so as the system completes booting to
become operational without the display (I can ssh into the system). When I
enable "DISCRETE" option in BIOS, system boots up with display using the NVIDIA
card but Intel GPU is not visible in tools such as lspci.
Observable behavior is the same
- with stock 4.13.0 kernel in PopOS
- upon installing intel-microcode_3.20171117.1_amd64.deb
dmesg snippet:
[drm] GPU HANG: ecode 9:0:0x00000000, reason: No progress on rcs0, bcs0, vcs0,
vecs0, 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.
Since the display was off, I had to reboot the laptop and I could not find
/sys/class/drm/card0/error file.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>