<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#c129">Comment # 129</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:aaronbottegal@gmail.com" title="Aaron B <aaronbottegal@gmail.com>"> Aaron B</a> <pre>Didn't mention it last night, but in my logs were this in my system log were messages about msc number being wrong, which we've seen before. But I also saw a "Chromium segfault" error which I haven't seen before, but would explain why it crashes. It's probably it's fault for not bailing from a bad return gracefully, but maybe the return isn't NULL when it should be, anything is possible. Also interesting in DMesg: [ 8531.831921] radeon 0000:01:00.0: Packet0 not allowed! Is it broken in all of radeonsi, and not only hawaii? I haven't seen this before. This was 500 seconds before my screen died. Still, anything else I should log from DPM and such to try to find what screws up when?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>