[i945gme] xorg crashes after upgrade to 9.10 netbook remix
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-intel (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xorg
X crashes after a long time (45 minutes, minimum, many hours maximum) after starting. Did not crash for 9.04, only after upgrade to 9.10.
Using netbook remix on ACER Atheros AR5BXB63, 16 GB hdd.
Sorry, but I haven't yet found any pattern / cause that triggers the crash.
X quits, I get a bunch of messages (too fast to see) on the console, then X restarts automatically with the login screen.
ProblemType: Bug
Architecture: i386
Date: Mon Dec 28 13:36:26 2009
DistroRelease: Ubuntu 9.10
MachineType: Acer AOA150
Package: xorg 1:7.4+3ubuntu10
ProcCmdLine: root=UUID=
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu10
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-
xserver-
SourcePackage: xorg
Tags: ubuntu-unr
Uname: Linux 2.6.31-16-generic i686
dmi.bios.date: 10/06/2008
dmi.bios.vendor: Acer
dmi.bios.version: v0.3310
dmi.board.
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: AOA150
dmi.product.
dmi.sys.vendor: Acer
fglrx: Not loaded
system:
distro: Ubuntu
architecture: i686kernel: 2.6.31-16-generic
[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03)
Subsystem: Acer Incorporated [ALI] Device [1025:015b]
affects: | xorg (Ubuntu) → xserver-xorg-video-intel (Ubuntu) |
tags: | added: 945gme crash karmic |
description: | updated |
Thank you for reporting this bug and helping make ubuntu better. It is at this point in time a little late to get bugs like this fixed in Karmic. We would like to ship Lucid without this bug, though. Since Karmic isn't working for you anyway, would it be okay for you to upgrade to Lucid, which is the current development release. There is a chance that this bug has already been fixed there. If it hasn't we would like a full backtrace from Lucid. There are some explanations for how to get such a backtrace at https:/ /wiki.ubuntu. com/X/Backtraci ng . It may seem a bit daunting at first, but there are several methods on that page, and usually at least one of them will work.