<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#c77">Comment # 77</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:nikolak@outlook.com" title="nikolak@outlook.com">nikolak@outlook.com</a> <pre>(In reply to Alex from <a href="show_bug.cgi?id=80568#c76">comment #76</a>) [...] > 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...". Doesn't seem to be it. Xorg.0.log doesn't show anything like that. The only difference error is in my syslog: Nov 28 20:13:20 mint kernel: [ 7497.992041] [drm] stuck on render ring Nov 28 20:13:20 mint kernel: [ 7497.993305] [drm] GPU HANG: ecode 4:0:0x9f47f9fd, in chrome [4630], reason: Ring hung, action: reset Nov 28 20:13:20 mint kernel: [ 7498.016208] drm/i915: Resetting chip after gpu hang Nov 28 20:13:21 mint kernel: [ 7498.445210] ------------[ cut here ]------------ Nov 28 20:13:21 mint kernel: [ 7498.445258] WARNING: CPU: 1 PID: 1830 at /home/apw/COD/linux/drivers/gpu/drm/drm_irq.c:1081 drm_wait_one_vblank+0x125/0x130 [drm]() Nov 28 20:13:21 mint kernel: [ 7498.445262] vblank not available on crtc 1, ret=-22 ...etc And if it did turn off hardware rendering it probably wouldn't happen on each page refresh like it does currently. > 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. Starting chrome with those parameters does the trick, but doesn't work if chrome gets started by clicking link in an external application for example. Hopefully better fix, either by intel or google, will make it in official repositories.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>