<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Cannot unbind GPU from AMDGPU"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97500#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Cannot unbind GPU from AMDGPU"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97500">bug 97500</a>
from <span class="vcard"><a class="email" href="mailto:notasas@gmail.com" title="Grazvydas Ignotas <notasas@gmail.com>"> <span class="fn">Grazvydas Ignotas</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=126768" name="attach_126768" title="modprobe then rmmod">attachment 126768</a> <a href="attachment.cgi?id=126768&action=edit" title="modprobe then rmmod">[details]</a></span>
modprobe then rmmod
I've been trying today's drm-next-4.9-wip (merged with 4.8.0-rc7) and the
situation has improved somewhat, doing rmmod just after modprobe succeeds with
a WARN from TTM, but attempts to modprobe it again are failing. If X session is
started/stopped before rmmod, the consequences are more severe, looks like some
sort of corruption.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>