When making something fullscreen (e.g.: a webpage or YouTube video) the entire screen goes black and for instance when launching a video with sound, after the screen has gone black, I can still hear the sound.
Although sometimes it only crashes after I try to exit fullscreen, and it does something like either go fully black, or the top bar and mouse disappear.
But whatever type of crash it is, it does it basically every time that I make anything full screen in my browser and forces me to have to restart my machine by holding down my computer's power button.
For more information on this as well as my debugging logs etc, and what other people have said about the issue please go here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1413710
Description: Ubuntu 14.10
*** 1:7.7+7ubuntu2 0
500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
I suspect this may be another duplicate of the bug 80568, fixed (worked-around) by this commit:
Author: Kenneth Graunke <firstname.lastname@example.org>
Date: Sat Jan 17 23:21:15 2015 -0800
i965: Work around mysterious Gen4 GPU hangs with minimal state changes.
Gen4 hardware appears to GPU hang frequently when using Chromium, and
also when running 'glmark2 -b ideas'. Most of the error states contain
3DPRIMITIVE commands in quick succession, with very few state packets
between them - usually VERTEX_BUFFERS/ELEMENTS and CONSTANT_BUFFER.
I trimmed an apitrace of the glmark2 hang down to two draw calls with a
glUniformMatrix4fv call between the two. Either draw by itself works
fine, but together, they hang the GPU. Removing the glUniform call
makes the hangs disappear. In the hardware state, this translates to
removing the CONSTANT_BUFFER packet between the two 3DPRIMITIVE packets.
Flushing before emitting CONSTANT_BUFFER packets also appears to make
the hangs disappear. I observed a slowdown in glxgears by doing it all
the time, so I've chosen to only do it when BRW_NEW_BATCH and
BRW_NEW_PSP are unset (i.e. we haven't done a CS_URB_STATE change or
already flushed the whole pipeline).
I'd much rather understand the problem, but at this point, I don't see
how we'd ever be able to track it down further. We have no real tools,
and the hardware people moved on years ago. I've analyzed 20+ error
states and read every scrap of documentation I could find.
Signed-off-by: Kenneth Graunke <email@example.com>
Acked-by: Matt Turner <firstname.lastname@example.org>
Cc: "10.4 10.3" <email@example.com>
It's in git, and backports are in Mesa 10.4.x for x >= 3. Please try upgrading to >=10.4.3. If it's resolved by such an upgrade, please mark as a duplicate of bug 80568.
*** This bug has been marked as a duplicate of bug 80568 ***