[Bug 111805] Constant "Resetting rcs0 for hang on rcs0" and machine lockup

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Nov 8 12:42:51 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=111805

--- Comment #39 from Kenneth C <kenny at panix.com> ---
(In reply to Leho Kraav (:macmaN :lkraav) from comment #38)

> 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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20191108/8514707e/attachment.html>


More information about the intel-gfx-bugs mailing list