<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Kernel hang, TearFree On, Mate desktop environment"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90873#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Kernel hang, TearFree On, Mate desktop environment"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90873">bug 90873</a>
from <span class="vcard"><a class="email" href="mailto:neatnoise@gmail.com" title="Tom <neatnoise@gmail.com>"> <span class="fn">Tom</span></a>
</span></b>
<pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=90873#c5">comment #5</a>)
<span class="quote">> <a href="http://lists.freedesktop.org/archives/dri-devel/2015-June/084514.html">http://lists.freedesktop.org/archives/dri-devel/2015-June/084514.html</a> fixes
> the hang for me (not a GPU hang but a kernel hang, because it tries to lock
> a mutex that's already locked).
>
>
> > [ 141.232226] radeon 0000:01:00.0: bo ffff8804236d3400 va 0x0000001000
> > conflict with (bo ffff88042a018800 0x0000001000 0x0000001563)
>
> These still happen, but at least with GNOME it continues working for me
> somehow. I tried various workarounds for this in the Xorg driver, but I
> haven't found anything that avoids these. I think the proper solution for
> these would be for the kernel driver to track GPU VA ranges per GEM handle
> instead of per BO.</span >
The latest patch applied to linux kernel rc8 fixed this issue, thanks.</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>