Originally reported for Ubuntu by Benny Hult at: https://bugs.launchpad.net/bugs/611951 Binary package hint: xserver-xorg-video-intel Running Lubuntu 10.10 and I was resuming from suspend with my Dell Latitude D420 and I got notified about GPU error. Seems like it might happen after every resume from suspend. DistroRelease: Ubuntu 10.10 Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu2 xserver-xorg 1:7.5+6ubuntu2 libgl1-mesa-glx 7.8.2-2ubuntu1 libdrm2 2.4.21-1ubuntu1 xserver-xorg-video-intel 2:2.12.0-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-12.17-generic 2.6.35-rc6 Uname: Linux 2.6.35-12-generic i686 Architecture: i386 Chipset: i945gm DRM.card0.DVI.D.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1280x800 edid-base64: AP///////wAwZOJYMTQwNCsQAQOAGhB4CoeumVdPjCYiUFQAAAABAQEBAQEBAQEBAQEBAQEBKhwAqFAgHjAQMCIABaMQAAAYAAAAAAAAAAAAAAAAAAAAAAAAAAAA/gBHRjk1MaUxMjFFWEVEAAAA/gAnNkJKaYmp6wEBCiAgAOg= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Sat Jul 31 07:38:58 2010 DumpSignature: d0c69edf ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py InstallationMedia: Lubuntu 10.10 "Maverick Meerkat" - i386 (20100702) InterpreterPath: /usr/bin/python2.6 MachineType: Dell Inc. Latitude D420 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-12-generic root=UUID=1cf4549c-fcec-494d-8878-a1f00cc09b3f ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: SourcePackage: xserver-xorg-video-intel UserGroups: dmi.bios.date: 02/02/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0TJ984 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0TJ984:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D420 dmi.sys.vendor: Dell Inc. glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.35-12-generic
Created attachment 37505 [details] i915_error_state Running intel_error_decode on the attached i915_error_state.txt shows that there is a page table error and that the ringbuffer is completely empty: Time: 1280551135 s 109870 us PCI ID: 0x27a2 EIR: 0x00000010 PGTBL_ER: 0x00000001 INSTPM: 0x00000000 IPEIR: 0x00000000 IPEHR: 0x00000000 INSTDONE: 0x7fffffc0 busy: Secondary ring 3 busy: Secondary ring 2 busy: Secondary ring 1 busy: Secondary ring 0 busy: Primary ring 1 busy: Primary ring 0 ACTHD: 0x00000000 seqno: 0x00000000 ringbuffer at 0x0d4b8000: 0x0d4b8000: 0x00000000: MI_NOOP 0x0d4b8004: 0x00000000: MI_NOOP 0x0d4b8008: 0x00000000: MI_NOOP .... 0x0d4d7ff4: 0x00000000: MI_NOOP 0x0d4d7ff8: 0x00000000: MI_NOOP 0x0d4d7ffc: 0x00000000: MI_NOOP
Created attachment 37506 [details] dmesg from boot (GPU error not shown here)
Created attachment 37507 [details] dmesg showing GPU error on suspend
Created attachment 37508 [details] Xorg.0.log
Page table error on resume, presuming fixed with the following commit unless the bug can be verified on the current kernel. commit ac0c6b5ad3b3b513e1057806d4b7627fcc0ecc27 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu May 27 13:18:18 2010 +0100 drm/i915: Rebind bo if currently bound with incorrect alignment. Whilst pinning the buffer, check that that its current alignment matches the requested alignment. If it does not, rebind. This should clear up any final render errors whilst resuming, for reference: Bug 27070 - [i915] Page table errors with empty ringbuffer https://bugs.freedesktop.org/show_bug.cgi?id=27070 Bug 15502 - render error detected, EIR: 0x00000010 https://bugzilla.kernel.org/show_bug.cgi?id=15502 Bug 13844 - i915 error: "render error detected" https://bugzilla.kernel.org/show_bug.cgi?id=13844
(In reply to comment #5) > Page table error on resume, presuming fixed with the following commit unless > the bug can be verified on the current kernel. > > commit ac0c6b5ad3b3b513e1057806d4b7627fcc0ecc27 This bug was reported with a 2.6.35-rc6 based kernel which included that commit. The original reporter should show up here soon, and I hereby ask him to verify with the 2.6.35 mainline build to confirm this is not Ubuntu specific and reopen the bug once verified.
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.