Forwarding this bug from Ubuntu reporter Asier: http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/747100 [Problem] Haven't seen many with PGTBL_ER: 0x00000003 but the IPEHR value looks mighty familiar. This one is with pineviewgm. [Original Description] Thrown at the time to execute command "sudo apt-get autoremove && sudo apt-get autoclean" after updating ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-intel 2:2.14.0-4ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic i686 Architecture: i386 Chipset: IGDgm CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1024x600 edid-base64: AP///////wAiZOkD+JQEABEUAQOAFg14CoYmlFdRkCchT1QAAAABAQEBAQEBAQEBAQEBAQEBlBEAsEBYGSA1I0UA3IEAAAAZFhQA2EBYJiBdIxUE3IEAAAAAAAAA/gAAAAAAAAAAAAAAAAAAAAAA/gAAAAAAAAAAAAEAAAAAADc= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Fri Apr 1 11:12:32 2011 DistUpgraded: Log time: 2011-03-31 10:19:21.338233 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: dkms.conf: Error! No 'BUILT_MODULE_NAME' directive specified for record #0. ndiswrapper, 1.56, 2.6.35-28-generic, i686: installed (WARNING! Missing some built modules!) blcr, 0.8.2: added DuplicateSignature: (ESR: 0x00000011 PGTBL_ER: 0x00000003 IPEHR: 0x01000000) ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GraphicsCard: Intel Corporation N10 Family Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928.2) InterpreterPath: /usr/bin/python2.7 MachineType: ASUSTeK Computer INC. 1001PX ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic root=UUID=30f906ac-077b-42cb-a9b1-4ef539f13160 ro quiet splash acpi_osi=Linux vt.handoff=7 ProcKernelCmdLine_: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic root=UUID=30f906ac-077b-42cb-a9b1-4ef539f13160 ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.6~3ubuntu11 libdrm2 2.4.23-1ubuntu5 xserver-xorg-video-intel 2:2.14.0-4ubuntu4 Renderer: Unknown SourcePackage: xserver-xorg-video-intel Title: [IGDgm] GPU lockup (ESR: 0x00000011 PGTBL_ER: 0x00000003 IPEHR: 0x01000000) UpgradeStatus: Upgraded to natty on 2011-03-31 (0 days ago) UserGroups: dmi.bios.date: 04/30/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x00000000 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd04/30/2010:svnASUSTeKComputerINC.:pn1001PX:pvrx.x:rvnASUSTeKComputerINC.:rn1001PX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.4git20110322-0ubuntu5 version.libdrm2: libdrm2 2.4.23-1ubuntu5 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6
Created attachment 45254 [details] BootDmesg.txt
Created attachment 45255 [details] CurrentDmesg.txt
Created attachment 45256 [details] i915_error_state.txt
Created attachment 45257 [details] XorgLog.txt
*** This bug has been marked as a duplicate of bug 32396 ***
Closing resolved+duplicate as duplicate of closed+fixed.
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.