touch-packages team mailing list archive

[Bug Watch Updater <1388612@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 86 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=80568.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2014-06-26T18:49:02+00:00 Haineb wrote:

Created attachment 101821
/sys/class/drm/card0/error as requested

Normal browsing, no other significant applications running. Crash has
occurred 3+ times. Kernel remains up after display crash. Able to use
other vtys normally, but restarting mdm after display crash results in
full kernel lock.

Google Chrome 35.0.1916.153

Linux host3 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/0

------------------------------------------------------------------------
On 2014-06-26T18:49:48+00:00 Haineb wrote:

Unable to consistently replicate with any specific use case.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/1

------------------------------------------------------------------------
On 2014-06-26T18:50:19+00:00 Haineb wrote:

Created attachment 101823
dmesg tail after GPU crash

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/2

------------------------------------------------------------------------
On 2014-06-26T19:48:34+00:00 Haineb wrote:

Issue replicated. Browsing in chrome again. No GPU crash reported this
time. I'm lost on what component is truly causing the failure at this
point.

[   18.736862] init: plymouth-upstart-bridge main process ended, respawning
[ 2738.952528] perf samples too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[ 4610.808077] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... render ring idle
[ 4616.535139] Watchdog[2389]: segfault at 0 ip 00007fae73e88b4e sp 00007fae638ae670 error 6 in chrome[7fae6fe97000+4f39000]
[ 4638.603458] Watchdog[4588]: segfault at 0 ip 00007f2827619b4e sp 00007f281703f670 error 6 in chrome[7f2823628000+4f39000]
[ 4648.644352] Watchdog[4627]: segfault at 0 ip 00007f2c06ceeb4e sp 00007f2bf6714670 error 6 in chrome[7f2c02cfd000+4f39000]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/3

------------------------------------------------------------------------
On 2014-11-14T19:24:13+00:00 Mattst88 wrote:

*** Bug 83627 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/6

------------------------------------------------------------------------
On 2014-11-14T19:24:49+00:00 Mattst88 wrote:

*** Bug 84781 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/7

------------------------------------------------------------------------
On 2014-11-14T19:25:25+00:00 Mattst88 wrote:

*** Bug 84971 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/8

------------------------------------------------------------------------
On 2014-11-14T19:25:45+00:00 Mattst88 wrote:

*** Bug 85344 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/9

------------------------------------------------------------------------
On 2014-11-14T19:26:12+00:00 Mattst88 wrote:

*** Bug 85406 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/10

------------------------------------------------------------------------
On 2014-11-14T19:26:26+00:00 Mattst88 wrote:

*** Bug 85656 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/11

------------------------------------------------------------------------
On 2014-11-14T19:26:38+00:00 Mattst88 wrote:

*** Bug 85726 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/12

------------------------------------------------------------------------
On 2014-11-14T19:27:02+00:00 Mattst88 wrote:

*** Bug 85749 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/13

------------------------------------------------------------------------
On 2014-11-14T19:27:16+00:00 Mattst88 wrote:

*** Bug 85824 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/14

------------------------------------------------------------------------
On 2014-11-14T19:27:28+00:00 Mattst88 wrote:

*** Bug 86108 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/15

------------------------------------------------------------------------
On 2014-11-14T19:27:39+00:00 Mattst88 wrote:

*** Bug 85874 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/16

------------------------------------------------------------------------
On 2014-11-14T19:28:00+00:00 Mattst88 wrote:

*** Bug 86167 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/17

------------------------------------------------------------------------
On 2014-11-14T19:28:27+00:00 Mattst88 wrote:

*** Bug 81394 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/18

------------------------------------------------------------------------
On 2014-11-14T19:32:26+00:00 Mattst88 wrote:

I've just marked a lot of bugs as duplicates of this one, so that we can
hopefully get to the bottom of the Great Gen4 Chrome Hang of 2014.

Firstly, apologies if your bug is not actually the same bug as all of
the rest. It's hard to determine that in advance.

It looks like this report was the first, and it's from the end of June.
What changed when you started experiencing the hang? Did you update
Mesa, the kernel, or Chrome itself?

Does reverting to a version of one of these from, say, April avoid the
problem? If so, that's great and we should be able to bisect it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/19

------------------------------------------------------------------------
On 2014-11-14T19:34:18+00:00 Mattst88 wrote:

*** Bug 83807 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/20

------------------------------------------------------------------------
On 2014-11-14T19:35:14+00:00 Mattst88 wrote:

*** Bug 84561 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/21

------------------------------------------------------------------------
On 2014-11-14T19:36:28+00:00 Mattst88 wrote:

*** Bug 85249 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/22

------------------------------------------------------------------------
On 2014-11-14T19:46:02+00:00 Mattst88 wrote:

*** Bug 78483 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/23

------------------------------------------------------------------------
On 2014-11-14T19:46:39+00:00 Mattst88 wrote:

*** Bug 74094 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/24

------------------------------------------------------------------------
On 2014-11-14T19:48:27+00:00 mikbini wrote:

Well, it never worked for me (I'm the reporter of bug 85824) but I tried
chrome only very recently (v 38.0.2125.111).

On the other hand I have a case that reproduces bug 85824 100% of the
times: bootstrap, login, launch chrome, go to the chrome store, don't
touch anything, wait a few instants ... video hangs.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/25

------------------------------------------------------------------------
On 2014-11-14T20:35:09+00:00 Haineb wrote:

The mainboard that this graphics chipset was embedded in has failed and
I no longer have it available for testing. (Failure seemed to be DIMM
related; probably not relevant to this bug.)

I rolled out Mint 17 with Chrome perhaps two weeks after its release/two
weeks before opening this report. These intermittent failures started
happening immediately. The failures persisted throughout all subsequent
system/Chrome updates until the board died a few weeks ago.

Unfortunately, I was not able to identify any cases under which this set
of packages worked stably on this graphics chipset.

(The new system with different mainboard is running the same packages;
just moved the hard disc over. No failures have occurred since swapping
to a different mainboard/graphics chipset.)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/26

------------------------------------------------------------------------
On 2014-11-14T22:49:40+00:00 Jarno Suni wrote:

I have upgraded chromium-browser from 37.0.2062.120 to 38.0.2125.111
recently, but my OS (Ubuntu Trusty) provides only version 34 as the
alternative version to downgrade to.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/27

------------------------------------------------------------------------
On 2014-11-15T03:25:00+00:00 RafaelFelipe.SL wrote:

I downgraded chromium from the current 38 version to the 34.0.1847.116
Built on Ubuntu 14.04, running on LinuxMint 17 aura (260972). It was
available from the official repositories selecting the option to force
version in synaptic.

Since I made it, I never experienced the gpu hang again.

PS: I'm running Linux Mint 17. On previous versions this bug didn't
exist.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/28

------------------------------------------------------------------------
On 2014-11-15T03:41:36+00:00 RafaelFelipe.SL wrote:

That leads me to the conclusion that the problem doesn't reside on
intel's driver, but on chromium itself.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/29

------------------------------------------------------------------------
On 2014-11-15T03:52:39+00:00 txtsd wrote:

lagreca can you please visit the Google Chrome Store and multiple random
videos on Youtube and see if Chrome still doesn't hang?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/30

------------------------------------------------------------------------
On 2014-11-15T04:02:39+00:00 RafaelFelipe.SL wrote:

txtsd, I've already done that. I have browsed multiple tabs on youtube,
other video websites, outlook website (which made the hang happen when
clicking the instanst messenger button), and so on.

The bug just doesn't happen on Chromium Version 34.0.1847.116 Built on
Ubuntu 14.04, running on LinuxMint 17 aura (260972).

I have tested it with and without the chromium ffmpeg extra codecs
package.

I have tested flash videos and html5 videos.

There is no bug with this version.

Of course I'd like to use the newer versions of Chrome and Chromium.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/31

------------------------------------------------------------------------
On 2014-11-15T04:03:34+00:00 RafaelFelipe.SL wrote:

I've entered chrome store while testing other tabs.

It's ok.

There's no gpu hang anymore.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/32

------------------------------------------------------------------------
On 2014-11-15T04:07:19+00:00 Alexsecret wrote:

lagreca, I think Chrome was still using software acceleration for page rendering in version 34.  It hadn't changed it to hardware acceleration yet.  I am not 100% sure though.
Another factor that is not mentioned here is that Chrome is not the only app that causes the crash.  Glmark2, an OpenGL benchmark app, causes exactly the same issue when it reaches the "Idea" test.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/33

------------------------------------------------------------------------
On 2014-11-15T04:08:24+00:00 txtsd wrote:

I've encountered the bug with github's Atom too.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/34

------------------------------------------------------------------------
On 2014-11-15T04:16:22+00:00 RafaelFelipe.SL wrote:

Alex,

But I checked the box to enable hardware acceleration when available.

If there are other programs affected, then I must agree with you that
it's really a driver's bug.

But the Chromium version I installed works for me.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/35

------------------------------------------------------------------------
On 2014-11-15T04:32:01+00:00 Alexsecret wrote:

It used to work for all of us, I remember it too.  The bug first
appeared in version 36 and it was only a couple of times in 4 months.
It got worse in 37 and finally it's permanent in 38.

They keep changing things.  The fact that hardware acceleration is
enabled, doesn't mean that all functions are enabled too.  If you type
chrome://gpu on your search bar, you will see a more thorough list of
what is actually enabled and what's not yet.  They keep certain
functions disabled till they become stable.

On my system, the Web store is crashing the GPU each and every time I go
there without disabling hardware acceleration first.  It's not random.
The web store has no videos.  hotmail is doing it too but randomly.
Google Chrome download page caused it once too.  It has to be something
else or there maybe 2 or 3 factors causing this.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/36

------------------------------------------------------------------------
On 2014-11-15T04:35:14+00:00 Alexsecret wrote:

(In reply to Alex from comment #34)
> It used to work for all of us, I remember it too.  The bug first appeared in
> version 36 and it was only a couple of times in 4 months.  It got worse in
> 37 and finally it's permanent in 38.
> 
> They keep changing things.  The fact that hardware acceleration is enabled,
> doesn't mean that all functions are enabled too.  If you type chrome://gpu
> on your search bar, you will see a more thorough list of what is actually
> enabled and what's not yet.  They keep certain functions disabled till they
> become stable.
> 
> On my system, the Web store is crashing the GPU each and every time I go
> there without disabling hardware acceleration first.  It's not random.  The
> web store has no videos.  hotmail is doing it too but randomly.  Google
> Chrome download page caused it once too.  It has to be something else or
> there maybe 2 or 3 factors causing this.

4 months is probably wrong.  It was a long time though.  :)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/37

------------------------------------------------------------------------
On 2014-11-15T04:40:52+00:00 RafaelFelipe.SL wrote:

Created attachment 109501
The content of "chrome://gpu " in Chrome 38.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/38

------------------------------------------------------------------------
On 2014-11-15T04:41:27+00:00 RafaelFelipe.SL wrote:

Created attachment 109502
The content of "chrome://gpu " in Chromium 34.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/39

------------------------------------------------------------------------
On 2014-11-15T04:42:54+00:00 RafaelFelipe.SL wrote:

I attached two pdf files showing the content of chrome://gpu both in 38
and 34 versions.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/40

------------------------------------------------------------------------
On 2014-11-15T09:02:19+00:00 Johny-quest wrote:

Hello,

I have tried to found first version of kernel / intel drivers / chroem
drivers which was cousing problems from apt-get logs:


root@Dell-LD830:~# grep -i Start-Date apt/* | perl -n -e 'BEGIN{my %hn;} $hn{$1}->{$2} = 1 if m/(\w+\.?\w*\.?\w*\.?\w*):.*?:\s+(\d+-\d+-\d+)/imgs; END{ print $_.": ".join(", ", sort keys %{$hn{$_}})."\n" for (sort(keys %hn)); }'

history.log: 2014-11-02, 2014-11-11
history.log.1: 2014-10-02, 2014-10-13, 2014-10-16, 2014-10-20
history.log.10: 2014-01-06, 2014-01-16
history.log.11: 2013-12-01, 2013-12-04, 2013-12-08, 2013-12-18, 2013-12-27, 2013-12-30
history.log.12: 2013-11-17, 2013-11-24
history.log.2: 2014-09-09, 2014-09-21, 2014-09-26
history.log.3: 2014-08-24
history.log.4: 2014-07-03, 2014-07-19
history.log.5: 2014-06-08
history.log.6: 2014-05-28
history.log.7: 2014-04-15
history.log.8: 2014-03-01, 2014-03-05, 2014-03-09, 2014-03-11, 2014-03-16
history.log.9: 2014-02-06, 2014-02-10, 2014-02-22


The GPU-Hung bug first occured about 2 weeks beforei've reported it here. So I should check versions before 2014-06-12. Probably bug was introduced in one of this upgrades:

history.log.5: 2014-06-08
history.log.6: 2014-05-28


Here are version that i was using at that time (extracted from logs):

>From history.log.9:
Start-Date: 2014-02-06  19:28:45
Commandline: apt-get upgrade ...
linux-image-3.11.0-15-generic:i386 (3.11.0-15.23, 3.11.0-15.25)
linux-firmware:i386 (1.116, 1.116.1)
xserver-xorg-video-intel:i386 (2.99.904-0ubuntu2, 2.99.904-0ubuntu2.1)
flashplugin-installer:i386 (11.2.202.335ubuntu0.13.10.1, 11.2.202.336ubuntu0.13.10.1)
...

>From history.log.7:
Start-Date: 2014-04-15  16:41:31
Commandline: apt-get upgrade ...
google-chrome-stable:i386 (33.0.1750.152-1, 34.0.1847.116-1)
...

>From history.log.6:
Start-Date: 2014-05-28  21:05:02
Commandline: apt-get upgrade ...
linux-firmware:i386 (1.127, 1.127.2)
linux-image-extra-3.13.0-24-generic:i386 (3.13.0-24.46, 3.13.0-24.47)
linux-libc-dev:i386 (3.13.0-24.46, 3.13.0-27.50)
linux-headers-3.13.0-24:i386 (3.13.0-24.46, 3.13.0-24.47)
linux-headers-3.13.0-24-generic:i386 (3.13.0-24.46, 3.13.0-24.47)
linux-image-3.13.0-24-generic:i386 (3.13.0-24.46, 3.13.0-24.47)
...

>From history.log.5:
Start-Date: 2014-06-08  20:15:24
Commandline: apt-get upgrade ...
libegl1-mesa:i386 (10.1.0-4ubuntu5, 10.1.3-0ubuntu0.1)
libosmesa6:i386 (10.1.0-4ubuntu5, 10.1.3-0ubuntu0.1)
libegl1-mesa-drivers:i386 (10.1.0-4ubuntu5, 10.1.3-0ubuntu0.1)
libwayland-egl1-mesa:i386 (10.1.0-4ubuntu5, 10.1.3-0ubuntu0.1)
...


For further reference I will include whole apt-get history as zip file.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/41

------------------------------------------------------------------------
On 2014-11-15T09:04:23+00:00 Johny-quest wrote:

Created attachment 109507
apt-get logs to bisect changes

Added apt.zip log files;

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/42

------------------------------------------------------------------------
On 2014-11-15T10:04:32+00:00 Johny-quest wrote:

Created attachment 109509
more logs drom current GPU Crash

Today I was able to reproduce this bug with:

Linux Dell-LD830 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:31:23
UTC 2014 i686 i686 i686 GNU/Linux

Google Chrome 38.0.2125.111

and glmark2 installed via apt-get install:

glmark2-data:i386 (2012.08-0ubuntu2, automatic), glmark2:i386
(2012.08-0ubuntu2)

I'm attaching logs for more information.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/43

------------------------------------------------------------------------
On 2014-11-15T10:12:12+00:00 Johny-quest wrote:

Created attachment 109510
When crash happens (screenshot from glmark2 demo)

I was able to reproduce error using glmark2 demo on Dell D830.

I've also got other PC with Intel GPU (ThinkPad T430s). I've tried to
reproduce error on ThinkPad Ivy Bridge Mobile GPU but the bug is not
there. I'm attaching screenshot to show exact moment from demo when
crash happens (the screen is from ThinkPad Ivy Bridge not Dell D830).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/44

------------------------------------------------------------------------
On 2014-11-16T08:09:45+00:00 Mattst88 wrote:

*** Bug 83423 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/45

------------------------------------------------------------------------
On 2014-11-18T02:09:10+00:00 RafaelFelipe.SL wrote:

Any news?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/46

------------------------------------------------------------------------
On 2014-11-18T02:26:47+00:00 RafaelFelipe.SL wrote:

Why is Intel ignoring us?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/47

------------------------------------------------------------------------
On 2014-11-18T02:27:10+00:00 RafaelFelipe.SL wrote:

We should file a class action!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/48

------------------------------------------------------------------------
On 2014-11-18T03:15:58+00:00 Mattst88 wrote:

Good grief. Take it easy. I work for Intel.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/49

------------------------------------------------------------------------
On 2014-11-18T06:32:20+00:00 shacharr wrote:

The glmark2 issue might be related to https://www.libreoffice.org/bugzilla/show_bug.cgi?id=85367 .
It is reproducing on my machine as well (GLmark2 ideas crashes the GPU, "render ring stuck"). Can provide the error file/log files if needed. Can't bisect, as for me the issue showed up when jumping from ubuntu 10.04 to ubuntu 14.04.
However, I'm not sure that the glmark issue and the chrome issue are related.
Matt Turner, any way I can help diagnose/resolve the issue?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/50

------------------------------------------------------------------------
On 2014-11-18T10:26:24+00:00 Daniel-ffwll wrote:

*** Bug 85958 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/51

------------------------------------------------------------------------
On 2014-11-18T11:06:17+00:00 Coladict wrote:

Created attachment 109667
Error log dump

Sending my latest dump from the crash as well.
I'll give it a few tries on my home computer as well tonight.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/52

------------------------------------------------------------------------
On 2014-11-18T13:00:16+00:00 RafaelFelipe.SL wrote:

I've found this topic which seems to be related to our bug:
https://bugs.archlinux.org/task/38518?project=1

It says:
"Description:
The new xf86-video-intel (2.99.907-1) causes the display to crash. Reverting to previous version (2.21.15-2) resolves the issue."

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/53

------------------------------------------------------------------------
On 2014-11-18T15:25:32+00:00 Alexsecret wrote:

This bug exists in driver version 2.99.911 too.  This is the latest one.
I have installed this driver using the graphics installer offered by
Intel.

I don't think there's any way for us to go back to version 2.21.15-2.
There's nowhere in the Ubuntu repos.

Intel will have to correct it eventually since reverting to older
drivers is not the right solution for any driver, is it?  ;)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/54

------------------------------------------------------------------------
On 2014-11-18T16:05:14+00:00 RafaelFelipe.SL wrote:

(In reply to Alex from comment #52)
> This bug exists in driver version 2.99.911 too.  This is the latest one.  I
> have installed this driver using the graphics installer offered by Intel.
> 
> I don't think there's any way for us to go back to version 2.21.15-2. 
> There's nowhere in the Ubuntu repos.
> 
> Intel will have to correct it eventually since reverting to older drivers is
> not the right solution for any driver, is it?  ;)

You're right, Alex.

I only hope that it helps to identify when the bug first happened and
why. Maybe it's enough to eliminate it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/55

------------------------------------------------------------------------
On 2014-11-18T18:30:55+00:00 RafaelFelipe.SL wrote:

(In reply to Matt Turner from comment #47)
> Good grief. Take it easy. I work for Intel.

Matt, what then can you tell us about Intel's efforts to solve this
issue?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/56

------------------------------------------------------------------------
On 2014-11-20T00:43:09+00:00 Alexsecret wrote:

Ok.  There's an update for our case here.

Yesterday I installed and tested the new Chrome 39.  If we re-enable
hardware acceleration on it and visit the Web store, the screen does not
switch off any more BUT, there is a huge BUT...  The driver switches off
hardware acceleration for the whole system after that and unless the
system is rebooted, it stays off.  This of course means that we have to
keep hardware acceleration off in Chrome if we don't want to have the
driver switch it off for the entire system.

It would be nice if Intel could solve this issue soon.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/57

------------------------------------------------------------------------
On 2014-11-20T13:09:53+00:00 RafaelFelipe.SL wrote:

(In reply to Alex from comment #55)
> Ok.  There's an update for our case here.
> 
> Yesterday I installed and tested the new Chrome 39.  If we re-enable
> hardware acceleration on it and visit the Web store, the screen does not
> switch off any more BUT, there is a huge BUT...  The driver switches off
> hardware acceleration for the whole system after that and unless the system
> is rebooted, it stays off.  This of course means that we have to keep
> hardware acceleration off in Chrome if we don't want to have the driver
> switch it off for the entire system.
> 
> It would be nice if Intel could solve this issue soon.

It's up to intel then.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/58

------------------------------------------------------------------------
On 2014-11-21T05:05:42+00:00 shacharr wrote:

I did few tests to see if I can narrow down the cause of the issue, here
are my insights so far:

- It seems that the bug is triggered only if AccelMethod is SNA. Setting
the AccelMethod to UXA seems to be hiding the issue with
chrome/chromium. Issue still shows up when running glmark2 -b ideas
(though this might be a different issue)

- I tried changing the Xorg/XFree driver versions. I used the
freedesktop git, and went all the way back to 2.20.0, where SNA was
officially introduced. Bug is reproducing there as well. I attach a
small patch to make the code from 2.20.0 compile on modern Xorg version.

- Last April was when Ubuntu released their new "long term support"
version, this (and derivatives) might explain part of the spike in the
bug reports at this point, as large number of people jumped ship to have
SNA enabled by default in their distro

- The ArchLinux page on Intel graphics (
https://wiki.archlinux.org/index.php/Intel_graphics ) contains few
pointers to additional tweaking knobs to try out. Going to try them next
when I have some free time.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/59

------------------------------------------------------------------------
On 2014-11-21T05:06:55+00:00 shacharr wrote:

Created attachment 109788
Compilation helper for old code versions, to assist future bisects (though it seems the issue is not bisectable)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/60

------------------------------------------------------------------------
On 2014-11-21T15:51:45+00:00 Alexsecret wrote:

(In reply to shachar from comment #57)
> I did few tests to see if I can narrow down the cause of the issue, here are
> my insights so far:
> 
> - It seems that the bug is triggered only if AccelMethod is SNA. Setting the
> AccelMethod to UXA seems to be hiding the issue with chrome/chromium. Issue
> still shows up when running glmark2 -b ideas (though this might be a
> different issue)
> 
> - I tried changing the Xorg/XFree driver versions. I used the freedesktop
> git, and went all the way back to 2.20.0, where SNA was officially
> introduced. Bug is reproducing there as well. I attach a small patch to make
> the code from 2.20.0 compile on modern Xorg version.
> 
> - Last April was when Ubuntu released their new "long term support" version,
> this (and derivatives) might explain part of the spike in the bug reports at
> this point, as large number of people jumped ship to have SNA enabled by
> default in their distro
> 
> - The ArchLinux page on Intel graphics (
> https://wiki.archlinux.org/index.php/Intel_graphics ) contains few pointers
> to additional tweaking knobs to try out. Going to try them next when I have
> some free time.


I'm really surprised to see that switching to UXA really helped you because that exact test was the very first I did when the bug first appeared and it didn't work at all.  Actually, I didn't even have to visit the Web Store in order to produce it.  I just attempted to watch a random video on Youtube and the screen went black at once.  I didn't even need a second test.  :)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/61

------------------------------------------------------------------------
On 2014-11-21T16:25:39+00:00 RafaelFelipe.SL wrote:

I tried changing accel mode to uxa again. Surprise, it doesn't work for
me. The bug persists. Chrome still crashes X11.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/62

------------------------------------------------------------------------
On 2014-11-21T16:26:49+00:00 RafaelFelipe.SL wrote:

Intel must intervene as soon as possible.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/63

------------------------------------------------------------------------
On 2014-11-21T17:26:46+00:00 Idr wrote:

There is some evidence (see bug #85267) that always_flush_cache=true or
always_flush_batch=true may help.

always_flush_cache=true always_flush_batch=true chromium-browser

This suggests that we're missing a flush somewhere... but finding where
is like finding a needle in all the haystacks. :(

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/64

------------------------------------------------------------------------
On 2014-11-21T17:28:03+00:00 Idr wrote:

(In reply to Ian Romanick from comment #62)
> There is some evidence (see bug #85267) that always_flush_cache=true or
                      Oops... bug #85367

> always_flush_batch=true may help.
> 
> always_flush_cache=true always_flush_batch=true chromium-browser
> 
> This suggests that we're missing a flush somewhere... but finding where is
> like finding a needle in all the haystacks. :(

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/65

------------------------------------------------------------------------
On 2014-11-21T18:03:10+00:00 Alexsecret wrote:

So, are you suggesting that we create a launcher using this as command
line?

always_flush_cache=true always_flush_batch=true /usr/bin/google-chrome

or

always_flush_cache=true always_flush_batch=true glark2

I am not sure I understand correctly.  :)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/66

------------------------------------------------------------------------
On 2014-11-21T18:18:51+00:00 Mattst88 wrote:

(In reply to Alex from comment #64)
> So, are you suggesting that we create a launcher using this as command line?
> 
> always_flush_cache=true always_flush_batch=true /usr/bin/google-chrome

Yes.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/67

------------------------------------------------------------------------
On 2014-11-21T20:45:29+00:00 Alexsecret wrote:

Ok.  I tested all three, Chrome, glmark2 and glmark2-es2 running them
from the terminal using your suggestion.

All three are working fine, the web store is loading fine, videos play
ok.

I wish I knew how to incluse those two "always_flush_cache=true
always_flush_batch=true" in a launcher command line though since the
only way I can launch chrome this way, is through a terminal and that
terminal becomes so crowded with data after a while.

I think this trick can be used till the final fix is released.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/68

------------------------------------------------------------------------
On 2014-11-21T21:42:41+00:00 RafaelFelipe.SL wrote:

(In reply to Alex from comment #66)
> Ok.  I tested all three, Chrome, glmark2 and glmark2-es2 running them from
> the terminal using your suggestion.
> 
> All three are working fine, the web store is loading fine, videos play ok.
> 
> I wish I knew how to incluse those two "always_flush_cache=true
> always_flush_batch=true" in a launcher command line though since the only
> way I can launch chrome this way, is through a terminal and that terminal
> becomes so crowded with data after a while.
> 
> I think this trick can be used till the final fix is released.

Yes, it really helps!!! Everything's fine with this workaround.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/69

------------------------------------------------------------------------
On 2014-11-22T01:52:13+00:00 Idr wrote:

Another method is to set those options in either the user or system
drirc.  I'm posting this from my phone, so I'll leave finding the
details as an exercise for the reader. :)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/70

------------------------------------------------------------------------
On 2014-11-22T03:09:46+00:00 Alexsecret wrote:

(In reply to Ian Romanick from comment #68)
> Another method is to set those options in either the user or system drirc. 
> I'm posting this from my phone, so I'll leave finding the details as an
> exercise for the reader. :)

First of all thank you for showing us this workaround.  I read about
drirc and found about driconf too and how we can set those options.
Using this syntax though: "always_flush_cache=true
always_flush_batch=true /usr/bin/google-chrome-stable & exit" runs
chrome and closes the terminal right after and I guess this seems to be
a better way to handle a temporary situation than changing dri settings
and then changing them back to what they were when a fix is released.

I'd like to ask what the drawbacks for these two settings are though.
Are they slowing things down for the specific app that's using them for
example?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/71

------------------------------------------------------------------------
On 2014-11-25T15:21:32+00:00 Alexsecret wrote:

Today, kernel 3.16 was officially released for 14.04 LTS in the
Canonical repos.  Do you think installing it would solve the problem
we're facing or would we still have to use the same workaround anyway
please?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/72

------------------------------------------------------------------------
On 2014-11-25T19:35:43+00:00 Ryan C. Underwood wrote:

Don't bother, unless it contains a special patch it doesn't help (also
tested with 3.17.x and 3.18-rc5)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/73

------------------------------------------------------------------------
On 2014-11-27T19:02:48+00:00 Mattst88 wrote:

*** Bug 86757 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/74

------------------------------------------------------------------------
On 2014-11-27T19:15:50+00:00 Daniel-ffwll wrote:

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 http://cgit.freedesktop.org/drm-intel 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).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/75

------------------------------------------------------------------------
On 2014-11-28T09:53:17+00:00 Nikola Kovacevic wrote:

I can confirm that starting chrome as "always_flush_cache=true
always_flush_batch=true google-chrome" mitigates the issue. I can not
seem to set that option in ~/.drirc file though, neither by changing
default settings or adding chrome as an application using driconf tool,
so if someone could post more info on how to do that until the issue
gets fixed I'd really appreciate it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/76

------------------------------------------------------------------------
On 2014-11-28T17:25:42+00:00 Nikola Kovacevic wrote:

(In reply to Daniel Vetter from comment #73)
> 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 http://cgit.freedesktop.org/drm-intel 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.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/77

------------------------------------------------------------------------
On 2014-11-28T17:46:32+00:00 Alexsecret wrote:

(In reply to nikolak from comment #75)
> (In reply to Daniel Vetter from comment #73)
> > 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 http://cgit.freedesktop.org/drm-intel 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.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/78

------------------------------------------------------------------------
On 2014-11-28T19:26:28+00:00 Nikola Kovacevic wrote:

(In reply to Alex from comment #76)
[...]
> 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.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/79

------------------------------------------------------------------------
On 2014-12-04T22:08:11+00:00 Mattst88 wrote:

*** Bug 87000 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/80

------------------------------------------------------------------------
On 2014-12-21T15:54:12+00:00 Warrickguy-n wrote:

Has anyone had success in either creating a desktop launcher or
configuring .drirc to set the always_flush_cache=true and
always_flush_batch=true parameters?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/81

------------------------------------------------------------------------
On 2014-12-21T20:15:00+00:00 txtsd wrote:

(In reply to Warren from comment #79)
> Has anyone had success in either creating a desktop launcher or configuring
> .drirc to set the always_flush_cache=true and always_flush_batch=true
> parameters?

I use this in my chrome.desktop
Exec=env always_flush_cache=true always_flush_batch=true /usr/bin/google-chrome-unstable %U

But my chrome has been failing to paint tabs, and refreshing them does
nothing. I have to open a new tab and enter the same links, or duplicate
the tabs.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/82

------------------------------------------------------------------------
On 2014-12-21T20:21:33+00:00 Alexsecret wrote:

(In reply to txtsd from comment #80)
> (In reply to Warren from comment #79)
> > Has anyone had success in either creating a desktop launcher or configuring
> > .drirc to set the always_flush_cache=true and always_flush_batch=true
> > parameters?
> 
> I use this in my chrome.desktop
> Exec=env always_flush_cache=true always_flush_batch=true
> /usr/bin/google-chrome-unstable %U
> 
> But my chrome has been failing to paint tabs, and refreshing them does
> nothing. I have to open a new tab and enter the same links, or duplicate the
> tabs.

This "unstable" I see in the path, wouldn't have something to do with
that, would it?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/83

------------------------------------------------------------------------
On 2014-12-22T01:13:48+00:00 Warrickguy-n wrote:

(In reply to txtsd from comment #80)
> (In reply to Warren from comment #79)
> > Has anyone had success in either creating a desktop launcher or configuring
> > .drirc to set the always_flush_cache=true and always_flush_batch=true
> > parameters?
> 
> I use this in my chrome.desktop
> Exec=env always_flush_cache=true always_flush_batch=true
> /usr/bin/google-chrome-unstable %U
> 
> But my chrome has been failing to paint tabs, and refreshing them does
> nothing. I have to open a new tab and enter the same links, or duplicate the
> tabs.

Thank you. I am unfamiliar with the env parameter for the Exec= entry. I
had tried basically the same Exec= statement as your suggestion less the
env and it failed. Afer adding the env it works fine. Thanks again.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/84

------------------------------------------------------------------------
On 2014-12-22T08:27:53+00:00 txtsd wrote:

(In reply to Alex from comment #81)
> (In reply to txtsd from comment #80)
> > (In reply to Warren from comment #79)
> > > Has anyone had success in either creating a desktop launcher or configuring
> > > .drirc to set the always_flush_cache=true and always_flush_batch=true
> > > parameters?
> > 
> > I use this in my chrome.desktop
> > Exec=env always_flush_cache=true always_flush_batch=true
> > /usr/bin/google-chrome-unstable %U
> > 
> > But my chrome has been failing to paint tabs, and refreshing them does
> > nothing. I have to open a new tab and enter the same links, or duplicate the
> > tabs.
> 
> This "unstable" I see in the path, wouldn't have something to do with that,
> would it?

Yea, I run the dev version, and that was actually a bug in the previous
version.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/85

------------------------------------------------------------------------
On 2015-01-09T00:05:04+00:00 Alexsecret wrote:

Guys, this is a bit irrelevant but since all the driver updates and stuff are done using these servers, I thought I'd post these errors they report for the past two days during apt-get update:
--------------------------------------------------
Err https://download.01.org trusty/main amd64 Packages                         
  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Err https://download.01.org trusty/main i386 Packages
  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Ign https://download.01.org trusty/main Translation-en_US
Ign https://download.01.org trusty/main Translation-en
Fetched 738 kB in 34s (21.4 kB/s)
W: Failed to fetch https://download.01.org/gfx/ubuntu/14.04/main/dists/trusty/main/binary-amd64/Packages  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

W: Failed to fetch
https://download.01.org/gfx/ubuntu/14.04/main/dists/trusty/main/binary-i386/Packages
server certificate verification failed. CAfile: /etc/ssl/certs/ca-
certificates.crt CRLfile: none

E: Some index files failed to download. They have been ignored, or old ones used instead.
--------------------------------------------------
Is anyone else facing this issue please?  Do we know anything about it?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/86

------------------------------------------------------------------------
On 2015-01-09T02:54:40+00:00 Ryan C. Underwood wrote:

*** Bug 86847 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388612/comments/87


** Changed in: mesa
       Status: Unknown => Confirmed

** Changed in: mesa
   Importance: Unknown => Medium

** Bug watch added: LibreOffice Bugzilla #85367
   https://www.libreoffice.org/bugzilla/show_bug.cgi?id=85367

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1388612

Title:
  [GM965] GPU lockup running OpenGL applications on Dell Vostro 1510

Status in Mesa:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  Hello, I'm suffering a GPU lockup problem with Ubuntu 14.10 64-bit on
  a Dell Vostro 1510 laptop with Intel graphics. The problem used to
  arise also with Ubuntu 14.04 and is always reproducible with glmark2
  on the LiveCD. Just to run the "ideas" benchmark of glmark2 to trigger
  the lockup in few seconds (glmark2 -b ideas). Other OpenGL
  applications also causes the lockup (e.g. FooBillard++, my self-made
  SDL applications). Memory test passed, BIOS at the latest version.
  Don't know if the following is a good point but I think that the
  problem is not caused by a failing hardware because it works fine on
  Windows. I tried with the latest Intel upstream kernel
  (http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-
  next/current/) and upstream X.org (https://launchpad.net/~xorg-
  edgers/+archive/ubuntu/ppa), no change.

  [Personal Notes]
  I'm new to Ubuntu's world, I hope I've done things right, if not please tell me and I will resend the report or supply more information. I've created the bug report with "ubuntu-bug xorg --save" from another machine via SSH while the sick machine was frozen. It seemed to me more logical than using ubuntu-bug directly when the system is working fine. I've collected other information via SSH during the same lockup: dmesg, Xorg.0.log, i915_error_state. The latter was added as attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Nov  2 19:24:31 2014
  DistUpgraded: 2014-10-25 12:05:51,479 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.13.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.16.0-23-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.16.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:0273]
     Subsystem: Dell Device [1028:0273]
  InstallationDate: Installed on 2014-10-11 (22 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
  MachineType: Dell Inc. Vostro1510
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=9b3612b7-c4bf-4840-885b-9fae75d6342c ro splash quiet vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (8 days ago)
  dmi.bios.date: 03/18/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0M277C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnDellInc.:bvrA15:bd03/18/2009:svnDellInc.:pnVostro1510:pvrNull:rvnDellInc.:rn0M277C:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro1510
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
  xserver.bootTime: Sun Nov  2 18:41:51 2014
  xserver.configfile: default
  xserver.errors:
   intel(0): Detected a hung GPU, disabling acceleration.
   intel(0): When reporting this, please include /sys/class/drm/card0/error and the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id                               15873 
   vendor                                     LPL
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1388612/+subscriptions