<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - Intel driver 2.21.13 hangs on shutdown process"
href="https://bugs.freedesktop.org/show_bug.cgi?id=67490#c23">Comment # 23</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - Intel driver 2.21.13 hangs on shutdown process"
href="https://bugs.freedesktop.org/show_bug.cgi?id=67490">bug 67490</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>As a userspace process, X is killable just like any other. The only times it
cannot are if the kernel is broken - that is the i915.ko oops whilst holding
its mutex is often enough to wedge the system. Until you can pinpoint where it
actually dies, probably requiring remote logging, you're not going to be able
to solve this other than using a bisect.
Note in the original bug report, the issue occurred with UXA. And a broken
package is a far more likely explanation.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>