<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [gen4] GPU Crash During Google Chrome Operation" href="https://bugs.freedesktop.org/show_bug.cgi?id=80568#c76">Comment # 76</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [gen4] GPU Crash During Google Chrome Operation" href="https://bugs.freedesktop.org/show_bug.cgi?id=80568">bug 80568</a> from <a class="email" href="mailto:alexsecret@hotmail.com" title="Alex <alexsecret@hotmail.com>"> Alex</a> <pre>(In reply to nikolak from <a href="show_bug.cgi?id=80568#c75">comment #75</a>) > (In reply to Daniel Vetter from <a href="show_bug.cgi?id=80568#c73">comment #73</a>) > > Just aside to everyone suffering from gen4 gpu hangs: If your kernel doesn't > > manage to reset the gpu after a hang please grab the latest > > drm-intel-nightly branch from <a href="http://cgit.freedesktop.org/drm-intel">http://cgit.freedesktop.org/drm-intel</a> It has > > fixed up gen4 gpu reset from Ville. I'll try to get this into 3.19 (but the > > drm subsystem merge window is kinda gone already). > > It works - as in it doesn't crash the GPU, but screen flickers (goes black > quickly and then shows content again) and system becomes unresponsive until > the page is finished rendering. What you're describing, is the way they've programmed the new Chrome 39 to handle the problem. This happens if you don't issue the "always_flush..." settings or if they don't work for some reason. The point is that if the symptoms you're describing happen, it means that the driver is switching off hardware acceleration completely for the whole system and it uses software rendering for all apps afterwards. That's why you can see the contents afterwards. You can verify this by checking the Xorg.0.log file in /var/log. You will see a line near the end of the file saying "Disabling hardware acceleration...". Personally, I'm using this method to start Chrome on my system which is Ubuntu based. I am opening a terminal and I'm pasting the line "always_flush_cache=true always_flush_batch=true /usr/bin/google-chrome-stable & exit". After pressing ENTER, the terminal is closed automatically and Chrome starts as usual.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>