[915gm] X Crash (Needs nomodeset). Backtrace included.

[Jane Atkinson]

Binary package hint: xorg

X runs for a short while (some minutes, sometimes longer, then crashes to a blank screen. Pressing an arrow key reveals a command-line screen. Attempting to run 'startx' gets a message that x is still running. Rebooting is the only remedy.

This is a minimal install with Openbox and xdm. Earlier in the development cycle, it was very solid. Recently (a few weeks) it's been exiting X unexpectedly. No particular pattern is apparent.

I installed the xserver version from ppa:ubuntu-x-swat/x-updates, which is currently running, and it's made no difference.

[XorgLogOld.txt]
(II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/mouse0)
(II) No input driver/identifier specified (ignoring)

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80b1e8b]
1: /usr/bin/X (0x8048000+0x6988d) [0x80b188d]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0x933410]
3: /usr/bin/X (0x8048000+0x3dd30) [0x8085d30]
4: /usr/bin/X (0x8048000+0x1ed7a) [0x8066d7a]
5: /lib/tls/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0x50abd6]
6: /usr/bin/X (0x8048000+0x1e961) [0x8066961]

Caught signal 3 (Quit). Server aborting
[/XorgLogOld.txt]

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Thu Apr 22 10:15:29 2010
DkmsStatus: Error: [Errno 2] No such file or directory
GdmLog: Error: command ['sudo', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: cat: /var/log/gdm/:0.log: No such file or directory
GdmLog1: Error: command ['sudo', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['sudo', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
MachineType: ASUSTeK Computer INC. 900
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=8a839476-cd55-4abb-91be-9d0929a9da94 ro quiet
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 05/12/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0501
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 900
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.:bvr0501:bd05/12/2008:svnASUSTeKComputerINC.:pn900:pvr0405:rvnASUSTeKComputerINC.:rn900:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 900
dmi.product.version: 0405
dmi.sys.vendor: ASUSTeK Computer INC.
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-21-generic

[Jane Atkinson (irihapeti)]

Adding "i915.modeset=0" to the kernel line in grub seems to prevent the crashes. I probably need to leave the machine going all day to be really certain of that.

[Jane Atkinson (irihapeti)]

Update to previous message:

From time to time, when using i915.modeset=0 option, I find that the display becomes pixellated. That is, the lettering and objects are still all there, but instead of being solid black, they will display as partly black and partly coloured.

Logging out and in again fixes the issue - for a while, anyway. I've been unable to figure out any specific thing that's causing this.

[Stenten (stenten)]

Can you confirm that you're still experiencing this bug?

[Jane Atkinson (irihapeti)]

I've run a couple of tests with a standard grub boot line, i.e. removed "i915.modeset=0"

Uptime was 4.5 hours and 6 hours, with no problems.

Seems like the bug has been fixed. :)

[Launchpad Janitor (janitor)]

[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no activity for 60 days.]