<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Random crashes on RadeonSI with Chromium."
href="https://bugs.freedesktop.org/show_bug.cgi?id=81644#c38">Comment # 38</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Random crashes on RadeonSI with Chromium."
href="https://bugs.freedesktop.org/show_bug.cgi?id=81644">bug 81644</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 <a href="show_bug.cgi?id=81644#c32">comment #32</a>)
<span class="quote">> R600_DEBUG=sb,sbsafemath,nollvm chromium-browser</span >
Those debugging options only have an effect with the r600g driver, not with
radeonsi.
<span class="quote">> radeonsi isn't the only chipset family affected: intel cards hd2000, hd3000,
> hd4000; gm45, gm965, i915 (sandybridge, ivybridge, haswell, etc.), or other
> radeons are also affected in different ways</span >
r600g issues might be related, but most definitely not Intel GPU ones.</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>