Forwarding this bug from Ubuntu reporter Dave Russell: http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/868684 [Problem] Graphics blank and can't be woken or interacted with. Doesn't appear to be a GPU hang; perhaps bad interaction with DPMS? [Original 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. The messages below 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. As for when it started happening, I can't be more specific than some time after the 3rd of October. Another reporter with the same set of error messages believes the problem occurs when Gnome puts 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. Somehow this reminds me of an old bug where the vblank counter got confused because of "DPMS off"." [ 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 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-8ProcKernelCmdLine: 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
Created attachment 52264 [details] BootDmesg.txt
Created attachment 52265 [details] CurrentDmesg.txt
Created attachment 52266 [details] XorgLog.txt
Created attachment 52267 [details] XorgLogOld.txt
Actually nevermind; looking more closely at the logs I bet this is a bug in gnome instead.
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.