<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#c194">Comment # 194</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 Alex Deucher from <a href="show_bug.cgi?id=79980#c193">comment #193</a>) > Unfortunately, this bug has become a dumping ground for any kind of > stability issue with radeonsi so I'm not really sure how useful it is > anymore. I suspect there are actually multiple issues that are now all > mixed up. What's the way forward? Shouldn't it be up to the developers to try and make sense of the reports and split up the bug entry appropriately? Should there be one report per affected user, or is there a better way to group them together? Christian König from <a href="show_bug.cgi?id=79980#c175">comment #175</a> made one suggestion, is that what we should be doing? > In general you can split the issues into two categories one is with VM > faults in the logs and the other ones are without.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>