<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - radeonsi: R9 280X hangs with SuperTuxKart"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88183#c25">Comment # 25</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - radeonsi: R9 280X hangs with SuperTuxKart"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88183">bug 88183</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to Alexandre Demers from <a href="show_bug.cgi?id=88183#c24">comment #24</a>)
<span class="quote">> To my knowledge, since I've had this video card (a few months), I've been
> dealing with VM faults.</span >
Note that I'm referring specifically to the VM faults triggered by your
apitrace from <a href="show_bug.cgi?id=88183#c5">comment 5</a>. A VM fault by itself is a generic symptom which can be
caused by many different things, it's more or less the equivalent of a CPU
segmentation fault.
<span class="quote">> However, are VM faults only related to mesa or can they come from somewhere
> else (drm)?</span >
The Mesa driver is most likely in general, though in this particular case it
could also be e.g. libdrm_radeon calculating the surface parameters
incorrectly.</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>