<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#c35">Comment # 35</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>Since Chris W has fixed an issue with the drm-tip I'd had with increased current draw when in S0 (see <a class="bz_bug_link bz_status_NEW " title="NEW - commit c1132367 "Extract GT render sleep (rc6) management" prevents entering s2idle" href="show_bug.cgi?id=111909">https://bugs.freedesktop.org/show_bug.cgi?id=111909</a>) in commit c601cb2135, I'd decided to try drm-tip again. So last night, I took the drm-tip as of 9d229bec4f5, merged Linus' tip with that, and have been running with an external monitor and running continuous videos for hours now, and have run several suspend cycles (which seems to have exacerbated this issue). I'm glad to say I haven't seen a hiccup in over 15 hours and only a couple of "Atomic update failure" and "Failed to enable link training" messages in dmesg (which appear to be normal, but I can post them if needed). So to make sure, apparently the best way to get something to break is to publicly announce it "fixed", so here I go: I think this is now fixed in the drm-tip. ... fingers crossed</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>