[i945gme] GPU lockup 17ff1d5833203e30cd78c259b1ba75ab
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-intel (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
This is on daily snapshot of Lucid
ProblemType: Crash
Architecture: i386
Chipset: i945gme
Date: Wed Mar 10 01:07:03 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
DumpSignature: 17ff1d5833203e3
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100221)
InterpreterPath: /usr/bin/python2.6
MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
Package: xserver-
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
ProcVersionSign
SourcePackage: nvidia-
Title: [i945gme] GPU lockup 17ff1d5833203e3
Uname: Linux 2.6.32-16-generic i686
UserGroups:
dmi.bios.date: 09/08/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 11CA.M015.
dmi.board.name: NC10
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: NC10
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucidarchitecture: i686kernel: 2.6.32-16-generic
[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03)
Subsystem: Samsung Electronics Co Ltd Device [144d:ca00]
affects: | nvidia-graphics-drivers (Ubuntu) → xserver-xorg-video-intel (Ubuntu) |
tags: | added: crash |
Changed in xserver-xorg-video-intel (Ubuntu): | |
status: | New → Confirmed |
description: | updated |
Thank you for reporting this bug. Unfortunately, the automatic GPU dump utility has in this case not succeeded in capturing the part of the GPU state where the error happened. This seems to have happened on all bugs of this kind for 945GME chipsets. In order to help us troubleshoot this issue, you may install the newest drm-intel-next or 2.6.34-rcX kernel (see https:/ /wiki.ubuntu. com/KernelTeam/ MainlineBuilds for how) and (preferably) add the kernel option drm.debug=0x02. An automatic bug report filed from that setup should hopefully contain all the information we can dream of. If the automatic bug reporting does not trigger, you can ssh in from another computer while the computer is hung, copy /sys/debug/ kernel/ dri/0/i915_ error_state, /var/log/ Xorg.0. log, and the output of dmesg, and attach that to a bug report.
Since the easiest way to upload the new information probably is to file a new automatic bug report, and so that we don't keep visiting this bug reports which has broken logs, I'm closing this bug report.