https://bugs.freedesktop.org/show_bug.cgi?id=91526
--- Comment #8 from Ilia Mirkin <[email protected]> ---
(In reply to Gediminas Jakutis from comment #7)
> This is still an issue[1], so I suppose it should be re-opened.
> I assume commit d68226087cf5f2f686d6c8f3377c5a1dec3d8bc4 might be at fault,
> but I haven't tested the game around that time, so I can't tell. I can
> bisect, if needed.
>
> [1] I just re-tested with the current mesa git head on a fully patched WoW
> client and the problem is there.
Argh! You're right :( Just retested with latest mesa and the trace you
originally supplied didn't work. But I *swear* it worked for me at commit
d68226087c. Maybe it was through luck? Or perhaps something in st/mesa changed
and it's taking a different path now...
--- Comment #9 from Gediminas Jakutis <[email protected]> ---
Diablo 3 seems to be hitting the exact same issue, BTW.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
Nouveau mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/nouveau
