nothing noticeable occurred computer just stated there was a gpu lockup

Bug #767475 reported by Andrew Jimenez
54
This bug affects 10 people
Affects Status Importance Assigned to Milestone
module-init-tools (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

[Problem]
The i915 kernel module seems to dislike having other kernel modules using the GPU. In some cases i915 will do a GPU reset and fire off a "GPU locked up!" event. The reset is successful and i915 carries on normally, so the user doesn't notice anything unusual and there's no symptoms other than the error messages in the dmesg log. However, this is enough to trigger the apport GPU lockup reporting tool to pop up on a subsequent reboot and prompt the user to file a bug report.

Essentially, module-init-tools (and other plumbing layer packages) don't always ensure a clean handoff between the vesafb driver and the i915 driver. However, when you know that i915 is going to load properly, you don't really need vesafb anyway.

[Workarounds]
Use xdiagnose to disable the vesafb framebuffer driver.
Or add it to the kernel blacklist.
Or direct apport not to file bug reports for gpu lockups. [This is the step taken for the natty release]

[Original Report]
Happens at every login. Not sure what is actually failing because everything seems to work fine.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xserver-xorg-video-intel 2:2.14.0-4ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
Architecture: i386
Chipset: i945gm
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CurrentDmesg: [ 21.095517] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro,user_xattr,commit=600
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///////wAGEF+cAAAAAAgQAQOAHRJ4Ci8wl1hTiyklUFQAAAABAQEBAQEBAQEBAQEBAQEBvBsAoFAgFzAwIDYAHrMQAAAYAAAAAQAGECAAAAAAAAAAAAogAAAA/gBMUDEzM1dYMS1UTEExAAAA/gBDb2xvciBMQ0QKICAgAMI=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Wed Apr 20 10:45:36 2011
DistUpgraded: Log time: 2011-04-13 08:09:13.779453
DistroCodename: natty
DistroVariant: ubuntu
DuplicateSignature: (ESR: 0x00000010 PGTBL_ER: 0x00000102 IPEHR: 0x01000000)
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
GraphicsCard:
 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:7270]
   Subsystem: Intel Corporation Device [8086:7270]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
MachineType: Apple Inc. MacBook2,1
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae root=UUID=5411928a-b3f0-49c2-b510-b7fe6fd5a9d9 ro quiet splash vt.handoff=7
ProcKernelCmdLine_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae root=UUID=5411928a-b3f0-49c2-b510-b7fe6fd5a9d9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.6+4ubuntu3
 libdrm2 2.4.23-1ubuntu6
 xserver-xorg-video-intel 2:2.14.0-4ubuntu7
Renderer: Unknown
SourcePackage: xserver-xorg-video-intel
Title: [i945gm] GPU lockup (ESR: 0x00000010 PGTBL_ER: 0x00000102 IPEHR: 0x01000000)
UpgradeStatus: Upgraded to natty on 2011-04-13 (7 days ago)
UserGroups:

dmi.bios.date: 06/27/07
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB21.88Z.00A5.B07.0706270922
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F4208CA9
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F4208CA9
dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CA9:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CA9:
dmi.product.name: MacBook2,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
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-4ubuntu7
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7

Revision history for this message
Andrew Jimenez (asjimene) wrote :
Bryce Harrington (bryce)
affects: xserver-xorg-video-intel (Ubuntu) → module-init-tools (Ubuntu)
Revision history for this message
Bryce Harrington (bryce) wrote :

Basically a dupe of #752940 but this is a "single-gpu" case. We believe the i915 driver conflicts with the vesafb driver. Typically there are no overt symptoms but sometimes it causes permanent lockup.

You can work around this by disabling the vesafb driver from loading (the xdiagnose utility helps here). But if your system isn't locking up, these error messages are harmless and can be ignored.

module-init-tools does perhaps need some massaging to better avoid these conflicts. Refiling bug.

Bryce Harrington (bryce)
summary: - nothing noticeable occurred computer just stated there was a crash
+ nothing noticeable occurred computer just stated there was a gpu lockup
Bryce Harrington (bryce)
description: updated
tags: removed: need-duplicate-check
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

Since this bug has four duplicates, and one of the duplicates (bug 767341) is itself Confirmed, it seems that this bug should be marked Confirmed as well. Any objections?

Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

Changed in module-init-tools (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.