[i945gm] GPU lockup (ESR: 0x00000010 PGTBL_ER: 0x00000102)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xf86-video-intel |
Invalid
|
High
|
|||
xserver-xorg-video-intel (Ubuntu) |
Triaged
|
High
|
Unassigned |
Bug Description
Binary package hint: xserver-
Running Ubuntu 11.04 32bit on an intel MacBook 1.1. This error is present all the time whilst using the system
Description: Ubuntu Natty (development branch)
Release: 11.04
xserver-
Installed: 2:2.14.0-4ubuntu6
Candidate: 2:2.14.0-4ubuntu6
Version table:
*** 2:2.14.0-4ubuntu6 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xserver-
ProcVersionSign
Uname: Linux 2.6.38-8-lowlatency i686
Architecture: i386
Chipset: i945gm
CurrentDmesg:
Date: Mon Mar 28 20:52:31 2011
DistroCodename: natty
DistroVariant: ubuntu
DuplicateSignature: (ESR: 0x00000010 PGTBL_ER: 0x00000102)
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
InterpreterPath: /usr/bin/python2.7
MachineType: Apple Computer, Inc. MacBook1,1
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.6~3ubuntu11
libdrm2 2.4.23-1ubuntu5
xserver-
SourcePackage: xserver-
Title: [i945gm] GPU lockup (ESR: 0x00000010 PGTBL_ER: 0x00000102)
UdevDb: Error: [Errno 2] No such file or directory
UpgradeStatus: Upgraded to natty on 2011-03-25 (7 days ago)
UserGroups:
dmi.bios.date: 10/12/06
dmi.bios.vendor: Apple Computer, Inc.
dmi.bios.version: MB11.88Z.
dmi.board.
dmi.board.name: Mac-F4208CC8
dmi.board.vendor: Apple Computer, Inc.
dmi.board.version: PVT
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Computer, Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAppleCom
dmi.product.name: MacBook1,1
dmi.product.
dmi.sys.vendor: Apple Computer, Inc.
version.
version.
Changed in xserver-xorg-video-intel (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in xserver-xorg-video-intel: | |
importance: | Unknown → High |
status: | Unknown → Invalid |
This crash has the same stack trace characteristics as bug #738066. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.