Forwarding this bug from Ubuntu reporter Loïc Minier: http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/710594 [Problem] We don't know the root cause, but some issue is triggering a lot of "get vblank counter failed: Invalid argument" error messages to fill up the user's /var/log/Xorg.0.log file. [Original Description] Hey My gdm log is 39 MB and full of: (WW) intel(0): I830DRI2GetMSC:1062 get vblank counter failed: Invalid argument (WW) intel(0): I830DRI2ScheduleWaitMSC:1118 get vblank counter failed: Invalid argument after only a couple of days of running Cheers, DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-intel 2:2.14.0-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2 Uname: Linux 2.6.38-1-generic x86_64 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/allscreens/options/active_plugins' CompositorRunning: compiz DRM.card0.DP.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: DRM.card0.DP.2: status: disconnected enabled: disabled dpms: Off modes: edid-base64: DRM.card0.HDMI.A.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1440x900 1440x900 edid-base64: AP///////wAwrnRAAAAAAAsTAQOAHRJ46tCjlltXlCYjUlkAAAABAQEBAQEBAQEBAQEBAQEB2CegjFGEGjAwIDYAH7QQAAAYNCGgjFGEGjAwIDYAH7QQAAAYAAAADwCVCjKVCigeAQAwZABVAAAA/gBMVEQxMzNFUTFCCiAgAIc= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Mon Jan 31 12:06:03 2011 DistUpgraded: Yes, recently upgraded Log time: 2009-12-07 12:44:27.512249 DistroCodename: natty DistroVariant: ubuntu GraphicsCard: Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] MachineType: LENOVO 2777CTO ProcEnviron: LANGUAGE=fr_FR:fr:en_GB:en PATH=(custom, user) LANG=fr_FR.UTF-8 LC_MESSAGES=fr_FR.utf8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-1-generic root=/dev/mapper/hostname--vg0-ubuntu--root ro quiet splash vt.handoff=7 Renderer: Hardware acceleration SourcePackage: xserver-xorg-video-intel UnitySupportTest: dmi.bios.date: 03/12/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 6EET27WW (1.08 ) dmi.board.name: 2777CTO 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:bvr6EET27WW(1.08):bd03/12/2009:svnLENOVO:pn2777CTO:pvrThinkPadX301:rvnLENOVO:rn2777CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2777CTO dmi.product.version: ThinkPad X301 dmi.sys.vendor: LENOVO version.libdrm2: libdrm2 2.4.23-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10-1ubuntu1 version.xserver-xorg: xserver-xorg 1:7.5+6ubuntu8 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
Bugzilla won't allow upload of the Xorg.0.log as too large, but the file is in launchpad if curious: http://launchpadlibrarian.net/63210535/XorgLog.txt
Created attachment 43416 [details] [review] 0001-Quell-excessively-verbose-vblank-counter-failed-erro.patch In the spirit of commit 0ad6d6e1, quell output after 5 prints of the message. (Perhaps this suggests a need for a wrapper routine around xf86DrvMsg that does this.)
I applied the patch to limit the damage. Is this an isolated case, or do we have more instances of broken vblanks? The goal is to work out just what the kernel is complaining about. For EINVAL, there is a forfeit of error messages...
(In reply to comment #3) > I applied the patch to limit the damage. Is this an isolated case, or do we > have more instances of broken vblanks? Isolated case. But a good tester/reporter.
Merging with 32571 for the time being, as the investigation will be the same, but the resolution may be subtly different. *** This bug has been marked as a duplicate of bug 32571 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.