<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - display turns off with intel(0): sna_mode_redisplay: page flipping failed, disabling CRTC:3 (pipe=0)" href="https://bugs.freedesktop.org/show_bug.cgi?id=70905#c39">Comment # 39</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - display turns off with intel(0): sna_mode_redisplay: page flipping failed, disabling CRTC:3 (pipe=0)" href="https://bugs.freedesktop.org/show_bug.cgi?id=70905">bug 70905</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to <a href="show_bug.cgi?id=70905#c38">comment #38</a>) > (In reply to <a href="show_bug.cgi?id=70905#c37">comment #37</a>) > > You underestimate the value of your debugging - it was very, very useful. > > Thank you. > > Good to know! :) > > > Time to try again! > > OK, pulled git and rebuilt this morning... Good news, I think. New files > are in the same place: Heh, apparently '%D' is a typo that we need to be told about at 60Hz. > <a href="http://data.boulder.swri.edu/~joe/">http://data.boulder.swri.edu/~joe/</a> > > > > Xorg.0.log2 happened with TearFree off just going into Chromium - unusual. > > > > Another assertion - not sure which, at a guess it decided the pointer was > > incoherent, which looks more like a bogus assertion... > > I tried a similar case (starting X and running Chromium with TearFree off). > No crash (but maybe that assertion is hard to hit). Log files named with > "_noTearFree_chromium". Had another bug report that revealed I screwed up in one of the patches yesterday which can explain all manner of strange failures. > I tried the Spotify with TearFree case, and no crash there, either! Log > files names with "_TearFree_spotify". > > I'll keep running with the debug version for a while with TearFree on. I > wonder if this last round of changes did the trick - fingers crossed! *fingers crossed* Certainly the issue in theory fixed by the patch this morning has the right hallmarks of being a random, hard to trigger bug that would end up not only causing the page-flip error but also the blit failure -- i.e. I think it explains this bug...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>