<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Constant "Resetting rcs0 for hang on rcs0" and machine lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=111805#c39">Comment # 39</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Constant "Resetting rcs0 for hang on rcs0" and machine lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=111805">bug 111805</a> from <a class="email" href="mailto:kenny@panix.com" title="Kenneth C <kenny@panix.com>"> Kenneth C</a> <pre>(In reply to Leho Kraav (:macmaN :lkraav) from <a href="show_bug.cgi?id=111805#c38">comment #38</a>) > do you have any interest in trying to bisect this problem. I've reported a couple of bugs here that I've determined the bad commit via sometimes lengthy bisection sessions, but those have been unique where they've been easily or uniquely reproducible; the problem with this set of GPU HANGs was they could happen with anywhere from 20 mins to 20 hours of uptime, and in the time between when I'd given up on the stuff in Linus's trees and when it was fixed there's been so many commits the series could easily be 15+ bisection trials, and I unfortunately don't have the time. But IIRC, like you you need Linus' master trees for PM improvements (for me, it's 'cause of s01x stuff I need), and if that's the case, you can always do what I do, and that's maintain several git remotes in your kernel tree- I keep Linus' tip, drm-tip, and RJW's PM tip as remotes. I can then pull a branch for drm-tip, then "git merge" Linus' master on top of that (and merge or cherry-pick from the PM tree from time-to-time); I don't recall much in the way of fixups, and I'm now running a kernel that's got the latest from both trees.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>