Forwarding this bug from Ubuntu reporter Jan D: http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/982415 [Problem] This GPU lockup happened right after a reboot after an update ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu3 Architecture: i386 Chipset: i915gm CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Tue Apr 10 14:02:14 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.5.0, 3.2.0-18-generic-pae, i686: installed v4l2loopback, 0.5.0, 3.2.0-20-generic-pae, i686: installed v4l2loopback, 0.5.0, 3.2.0-22-generic-pae, i686: installed v4l2loopback, 0.5.0, 3.2.0-23-generic-pae, i686: installed DuplicateSignature: [i915gm] GPU lockup render.IPEHR: 0x3f800000 Ubuntu 12.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: IBM Device [1014:0582] Subsystem: IBM Device [1014:0582] InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) InterpreterPath: /usr/bin/python2.7 MachineType: IBM 1858CLG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic-pae root=UUID=df6b9369-3a50-48c5-8036-5f5bba4f7300 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.6+12ubuntu1 libdrm2 2.4.32-1ubuntu1 xserver-xorg-video-intel 2:2.17.0-1ubuntu4 SourcePackage: xserver-xorg-video-intel Title: [i915gm] False GPU lockup render.IPEHR: 0x3f800000 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/25/2005 dmi.bios.vendor: IBM dmi.bios.version: 70ET62WW (1.22 ) dmi.board.name: 1858CLG dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr70ET62WW(1.22):bd11/25/2005:svnIBM:pn1858CLG:pvrThinkPadR52:rvnIBM:rn1858CLG:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 1858CLG dmi.product.version: ThinkPad R52 dmi.sys.vendor: IBM version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2
Created attachment 60210 [details] BootDmesg.txt
Created attachment 60211 [details] CurrentDmesg.txt
Created attachment 60212 [details] i915_error_state.txt
Created attachment 60213 [details] XorgLog.txt
Incoherent batch buffer, sounds like another instance of: commit 14667a4bde4361b7ac420d68a2e9e9b9b2df5231 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Apr 3 17:58:35 2012 +0100 drm/i915: Finish any pending operations on the framebuffer before disabling Similar to the case where we are changing from one framebuffer to another, we need to be sure that there are no pending WAIT_FOR_EVENTs on the pipe for the current framebuffer before switching. If we disable the pipe, and then try to execute a WAIT_FOR_EVENT it will block indefinitely and cause a GPU hang.
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.