<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - 845G: crtc active state doesn't match with hw state" href="https://bugs.freedesktop.org/show_bug.cgi?id=64764#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - 845G: crtc active state doesn't match with hw state" href="https://bugs.freedesktop.org/show_bug.cgi?id=64764">bug 64764</a> from <a class="email" href="mailto:mlsemon35@gmail.com" title="mlsemon35@gmail.com">mlsemon35@gmail.com</a> <pre>(In reply to <a href="show_bug.cgi?id=64764#c20">comment #20</a>) > So if you do a > > $ xset dpms force off > > in X, do you still see the backtrace or not? > > If you still get it, please attach the output of dmesg with drm.debug=0xe It's looking very good right now, no issues in three days. My experiment with the setterm -powerdown settings did not give the expected results, going like this: powerdown: stack trace off: nothing hsync: nothing vsync: nothing powerdown: nothing There were a few reboots in there, and I can't help but wonder if one of them let your fix do its job. This PC is more than capable of creating confusing results like this. I'm keeping this patch, despite the lack of absolute science behind the great success so far. Thanks! Michael</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> </ul> </body> </html>