<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Tonga startx fails since mesa/drm 56d8dd6 amdgpu: make vamgr per device v2"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91704#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Tonga startx fails since mesa/drm 56d8dd6 amdgpu: make vamgr per device v2"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91704">bug 91704</a>
from <span class="vcard"><a class="email" href="mailto:master.homer@gmail.com" title="Mathias Tillman <master.homer@gmail.com>"> <span class="fn">Mathias Tillman</span></a>
</span></b>
<pre>I can confirm that reverting to ffa305d0fc926418e4dff432381ead8907dc18d9 makes
it work, before it would fail before reaching the dm login page (I'm using
sddm), and now it reaches the login page. I also did a manual unpatching of
56d8dd6a9c03680700e0b0043cb56e0af7e3e3de when on the latest commit, which gave
me the same result.
The conflict looks to me like it's trying to initialize the device multiple
times - I did some debugging, and it reaches the amdgpu_device_initialize
function several times with the same virtual address. I'm not sure if this is
intentional or not, but it does seem a bit odd to me. Maybe there should be a
saved global state of vamgr's that corresponds to the virtual address? Or is it
just not supposed to initialize the same device multiple times?</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>