Ubuntu
gnome-settings-daemon package

vblank counter failed - screen hung

Bug #868684 reported by Dave Russell on 2011-10-05

This bug affects 9 people

Affects		Status	Importance	Assigned to	Milestone
	xf86-video-intel	New	Undecided	Unassigned
	gnome-settings-daemon (Ubuntu)	Confirmed	High	Unassigned

Bug Description

Just came back to the screen to find it hung, I could still move the mouse but nothing else. Unable to interact with the system graphically. Was able to ssh in and gather this information before rebooting.

[ 23113.957] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 23113.957] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 23113.957] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 23113.957] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 23114.030] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 23114.031] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 23114.031] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 23114.031] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 23114.065] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 23114.065] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 23114.084] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 23114.105] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 23212.685] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 23379.328] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 23379.409] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 23442.436] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 24649.942] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 24650.051] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 24730.542] (WW) intel(0): first get vblank counter failed: Invalid argument

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xorg 1:7.6+7ubuntu7
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
Date: Wed Oct 5 21:30:51 2011
DistUpgraded: Log time: 2011-09-22 20:36:49.680898
DistroCodename: oneiric
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Within the last few days
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:20e4]
   Subsystem: Lenovo Device [17aa:20e4]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
MachineType: LENOVO 2241B48
PccardctlIdent:
Socket 0:
   no product info available
PccardctlStatus:
Socket 0:
   no card
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=4587a2fe-b540-495f-ab91-999ee1b53a2a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to oneiric on 2011-09-30 (4 days ago)
dmi.bios.date: 04/22/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET66WW (2.16 )
dmi.board.name: 2241B48
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6FET66WW(2.16):bd04/22/2009:svnLENOVO:pn2241B48:pvrThinkPadT500:rvnLENOVO:rn2241B48:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2241B48
dmi.product.version: ThinkPad T500
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

See original description

Tags:

Revision history for this message

Dave Russell (drussell) wrote on 2011-10-05:

BootDmesg.txt Edit (185.4 KiB, text/plain; charset="utf-8")
BootLog.gz Edit (420 bytes, application/x-gzip)
CurrentDmesg.txt Edit (4.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (4.9 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (197.1 KiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (28.2 KiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (1002 bytes, text/plain; charset="utf-8")
LightdmGreeterLog.txt Edit (45.7 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (5.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (17.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (748 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.4 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (129.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (282.5 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (45.0 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (55.8 KiB, text/plain; charset="utf-8")

Bryce Harrington (bryce) on 2011-10-05

affects:	xorg (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Changed in xserver-xorg-video-intel (Ubuntu):
importance:	Undecided → High
status:	New → Confirmed
description:	updated

Revision history for this message

Bryce Harrington (bryce) wrote on 2011-10-05:

There is no evidence in the logs that there was a GPU lockup event (the prototypical X freeze with -intel graphics). Just the vblank counter failure errors in the log. I assume those messages correspond to when the system became unresponsive?

You indicated this happens multiple times per day under certain circumstances. Do you know a specific activity that tends to trigger it more often than others?

Looking at your dpkg.log file, it doesn't look like any X packages upgraded recently, but perhaps some other package changed and is triggering it. Most of the packages appear to have received only minor version bumps, but I see unity moved from 4.20 to 4.22. Are you able to reproduce this bug with unity-2d (or gnome classic desktop)? If not, you might try seeing if downgrading to an earlier unity version also prevents the issue (apt-get install unity=4.20.0-0ubuntu2 perhaps)

Other than that, do you happen to know which day you first noticed these lockups? That would help narrow down what package might be at fault.

Changed in xserver-xorg-video-intel (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Dave Russell (drussell) wrote on 2011-10-06:

Yes those times correspond to when the system became unresponsive.

Unfortunately I've not found an activity that provokes it more often than anything else. I'm getting about 1-2 of these per day currently.

I will try using unity2d to see if the events occur there.

As for when it started happening, I can't be more specific than some time after the 3rd of October.

Changed in xserver-xorg-video-intel (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Achim (ach1m) wrote on 2011-10-09:

The problem occurs for me while I wasn't using my computer. Gnome put the monitor into standby.
After moving my mouse the screen came back but it was like frozen. I could click on a launcher but it showed no reaction.
Then I switched to tty1 and back to graphical desktop and the screen was alive again.

But everything was slow, If I take a look at Xorg.0.log I see the following messages.

[ 5333.504] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 5333.504] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 5333.504] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 5333.504] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 5333.524] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 5333.525] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 5333.525] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 5333.525] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 5333.555] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 5333.555] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 5333.555] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 5333.578] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 5333.579] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 5333.612] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 5333.612] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 5333.652] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 5333.826] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 5338.138] (WW) intel(0): first get vblank counter failed: Invalid argument

Somehow this reminds me of an old bug where the vblank counter got confused because of "DPMS off".

I hope this Information is somehow helpful.

But everything was slow, If I take a look at Xorg.0.log I see the following messages.

[  5333.504] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[  5333.504] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[  5333.504] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[  5333.504] (WW) intel(0): first get vblank counter failed: Invalid argument
[  5333.524] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[  5333.525] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[  5333.525] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[  5333.525] (WW) intel(0): first get vblank counter failed: Invalid argument
[  5333.555] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[  5333.555] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[  5333.555] (WW) intel(0): first get vblank counter failed: Invalid argument
[  5333.578] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[  5333.579] (WW) intel(0): first get vblank counter failed: Invalid argument
[  5333.612] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[  5333.612] (WW) intel(0): first get vblank counter failed: Invalid argument
[  5333.652] (WW) intel(0): first get vblank counter failed: Invalid argument
[  5333.826] (WW) intel(0): first get vblank counter failed: Invalid argument
[  5338.138] (WW) intel(0): first get vblank counter failed: Invalid argument

Somehow this reminds me of an old bug where the vblank counter got confused because of "DPMS off".

I hope this Information is somehow helpful.

Bryce Harrington (bryce) on 2011-10-12

Changed in xserver-xorg-video-intel:
importance:	Unknown → Undecided
status:	Unknown → New
summary:	- Xorg freeze + vblank counter failed - screen hung

Revision history for this message

Bryce Harrington (bryce) wrote on 2011-10-12:

Looks likely to be this.

gnome-settings-daemon (3.2.0-0ubuntu4) oneiric; urgency=low
  * debian/patches/00git_dont_sleep_on_idle_by_default.patch:
    - Don't sleep on idle by default (LP: #860485)
  * debian/patches/00git_dont_revert_pre_idle_brigthness.patch:
    - Do not revert to the pre-idle brightness if idle dimming is disabled
  * debian/patches/50_add_dell_backlight.patch:
    - Add 'dell_backlight' module to gsd-backlight-helper (LP: #862474)

That's the only thing that changed on the 3rd/4th that looks relevant. No X or kernel packages changed; there was one change to compiz but it looks innocuous. So, probably a regression g-s-d.

If you find the issue is still reproducible with current oneiric, you could maybe try downgrading to 3.2.0-0ubuntu3, and/or back out each of the changes to see which caused the vblank problem.

affects:

xserver-xorg-video-intel (Ubuntu) → gnome-settings-daemon (Ubuntu)

Revision history for this message

Sebastien Bacher (seb128) wrote on 2011-10-12:

there was also 2 gnome-desktop3 uploads:

https://launchpad.net/ubuntu/+source/gnome-desktop3/3.2.0-0ubuntu3

"gnome-desktop3 (3.2.0-0ubuntu3) oneiric; urgency=low

* debian/patches/00git_disable_dpms_timeouts.patch:
- Disable DPMS timeouts (LP: #863038)"

https://launchpad.net/ubuntu/+source/gnome-desktop3/3.2.0-0ubuntu2

"gnome-desktop3 (3.2.0-0ubuntu2) oneiric; urgency=low

* debian/patches/02_refuse_to_break_GL_compositors.patch:
..."

the first one could perhaps create such issues. Do you get the issue every time?

Revision history for this message

Achim (ach1m) wrote on 2011-10-12:

No, I don't get the issue every time. I have to say that I don't have found a reliable way to reproduce the problem.
At the moment I would say that it happens sporadically. Today I had no problems so far.

Revision history for this message

Dave Russell (drussell) wrote on 2011-10-12:

I agree, for me it's "mostly" when the system has been running for a while, so I've seen it 2-3 times first thing in the morning when the system has been left running overnight.

I'm able to ssh into the machine and poke about, look at logs, report bugs etc, but the display is hung.

Unfortunately I'm travelling at the moment so not much chance of having a system running for very long.

Revision history for this message

Achim (ach1m) wrote on 2012-05-14:

#10

As far as I can tell this problem seems to be fixed with the new intel driver.

xserver-xorg-video-intel:
  Installiert: 2:2.19.0-0ubuntu1~xup1
  Kandidat: 2:2.19.0-0ubuntu1~xup1
  Versionstabelle:
*** 2:2.19.0-0ubuntu1~xup1 0
        500 http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status
     2:2.17.0-1ubuntu4 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

With the default packages in ubuntu precise I still had failing vblank counters in my Xorg.0.log

If you take a look at the release notes[1] you can see the following line.
- Prevent waiting on scanlines whilst not in control of the VT and therefore whilst referencing foreign CRTC configurations.

To my mind this may have solved the problem.
I hope this information is helpful for the others that have this issue.

––––––––––––––––––
[1] http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/plain/NEWS?id=444da84c47266bcbbdf5121507901de8eb36f11b

Revision history for this message

Dmitry (df2) wrote on 2012-09-02:

#11

Recent solution did not helped me, install latest 2.19.0 drivers and still got this error

Revision history for this message

Dmitry (df2) wrote on 2012-09-02:

#12

I'd wish to use VESA driver as poor man's solution, but X.org says something like "Not using vesa while intel kernel module loaded"

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

freedesktop-bugs #41727
[CLOSED NOTOURBUG] Edit

Bug watches keep track of this bug in other bug trackers.

Ubuntugnome-settings-daemon package

vblank counter failed - screen hung

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
gnome-settings-daemon package