<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Radeon HD6950: Failed to parse relocation -35 (Linux 3.11-rc regression)" href="https://bugs.freedesktop.org/show_bug.cgi?id=68125#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Radeon HD6950: Failed to parse relocation -35 (Linux 3.11-rc regression)" href="https://bugs.freedesktop.org/show_bug.cgi?id=68125">bug 68125</a> from <a class="email" href="mailto:aeb@debian.org" title="Andreas Bombe <aeb@debian.org>"> Andreas Bombe</a> <pre>(In reply to <a href="show_bug.cgi?id=68125#c1">comment #1</a>) > Can you bisect? I will have a go at it tomorrow then. That is going to be very time consuming, I expect, what with the bug only showing itself after quite some time. What I also meant to mention is that the complexity of whatever it is doing does not seem to affect the likelihood of the bug occuring. For example, I played Team Fortress 2 for quite some time on the 3.11-rc5 run, and that resulted only in one reset and successful recovery. They don't appear to occur when the system is really idle though, often they happen just as I start to move the mouse or scroll in gvim.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>