<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c39">Comment # 39</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 <a class="email" href="mailto:jackdachef@gmail.com" title="jackdachef@gmail.com">jackdachef@gmail.com</a> <pre>(In reply to <a href="show_bug.cgi?id=81644#c38">comment #38</a>) > (In reply to <a href="show_bug.cgi?id=81644#c32">comment #32</a>) > > R600_DEBUG=sb,sbsafemath,nollvm chromium-browser > > Those debugging options only have an effect with the r600g driver, not with > radeonsi. > are the other ways to temporarily disable LLVM for debugging in radeonsi ? gentoo ebuilds force users to compile mesa & radeonsi with llvm - so that seemingly is the only way of operation with these kind of chipsets/cards ? > > > 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 > > r600g issues might be related, but most definitely not Intel GPU ones. so things are implemented *that* differently between intel & radeon drivers ?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>