<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [GM45] loss of driver acceleration after some time (bisected)" href="https://bugs.freedesktop.org/show_bug.cgi?id=103025#c71">Comment # 71</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [GM45] loss of driver acceleration after some time (bisected)" href="https://bugs.freedesktop.org/show_bug.cgi?id=103025">bug 103025</a> from <a class="email" href="mailto:promarbler14@gmail.com" title="Adric Blake <promarbler14@gmail.com>"> Adric Blake</a> <pre>I decided to test on a few other different machines that I had around but couldn't test until now. System 1: Almador (gen2) - An 845G system Testing with the cinnamon desktop, I can load the desktop, but the moment the gnome-terminal window opens the window flickers/glitches like it would do on my gm45 and the GPU hangs. No resizing required. I collected three dumps for each boot I tested this. First dump was on the stock xf86-video-intel, and the cinnamon desktop Second dump was an assert-enabled build with a patch to ignore some problematic asserts. Oddly enough, it hung without hitting any of the kgem/pitch asserts that I was expecting, despite the same flicker I saw. Running the cinnamon desktop. Third dump was an assert-enabled build like before, but I started with the mate desktop and attempted to replace it with cinnamon from within. It hung without me opening gnome-terminal, though I already had a terminal window open. System 2: Haswell (gen7.5, gt3) - Intel Iris Pro? No msg in kernel log so I'm not sure. EFI. I tested this system like I would with my gm45 (cinnamon, resizing gnome-terminal as stated before), but I could not observe any flickering using the stock xf86-video-intel driver. I maxed the cpu and spun up as many instances of glxgears as possible, but resizing the window still failed to trigger the bug.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>