<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - X server crashes in i965 on desktop startup when DRI3 v1.2 / modifier support is enabled"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106642#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - X server crashes in i965 on desktop startup when DRI3 v1.2 / modifier support is enabled"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106642">bug 106642</a>
from <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>(In reply to Sergii Romantsov from <a href="show_bug.cgi?id=106642#c4">comment #4</a>)
<span class="quote">> As alternative temporal solution (without patching) can be tried to set
> 'INTEL_DEBUG=norbc' (but can't check if it helps).</span >
If one wants to do manual testing, best is just to patch Mesa, or instead of
disabling all RBC (texture uploads, offscreen render targets...), one should
just disable it for onscreen render targets from X server config
("dmabuf_capable" option).
For automated testing these aren't options though. Hacking around upstream
bugs in testing automation is just plain wrong. More visible the issues are in
automation, the quicker they should be fixed / worked around *in upstream*.
And if automation doesn't catch desktop killer bugs, automation should be
fixed.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>