<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Random radeonsi crashes" href="https://bugs.freedesktop.org/show_bug.cgi?id=79980#c212">Comment # 212</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Random radeonsi crashes" href="https://bugs.freedesktop.org/show_bug.cgi?id=79980">bug 79980</a> from <a class="email" href="mailto:marti@juffo.org" title="Marti Raudsepp <marti@juffo.org>"> Marti Raudsepp</a> <pre>(In reply to Jacob from <a href="show_bug.cgi?id=79980#c211">comment #211</a>) > I looked back through kern.log and found the last time I encountered a > crash, which happened to be with kernel 3.15.10 from the Ubuntu repo. > That crash seemed to have been caused by dpm: > [drm:si_dpm_set_power_state] *ERROR* si_set_sw_state failed Jacob, please report a separate bug about your symptoms. (In reply to Michel Dänzer from <a href="show_bug.cgi?id=79980#c210">comment #210</a>) > One thing I find interesting is that only Southern Islands seems affected. And Pitcairn too. (In reply to Michel Dänzer from <a href="show_bug.cgi?id=79980#c207">comment #207</a>) > In general, it's much better to > track things separately. Should the two bugs resolved as "duplicate" be de-duplicated then? <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Fails to page flip multiple time, queue overflows waiting for one to finish that never does crashing entire system." href="show_bug.cgi?id=80141">Bug 80141</a> and <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - [RadeonSI]GPU Lockup with Linux 3.16 & Mesa Git" href="show_bug.cgi?id=82886">Bug 82886</a>.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>