On some Xscreensaver (i have put it to random) and also once in Google Chrome Xorg Crashed went out and didnt restart but even freeze and nothing responds. Not even Raw Mode.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-xorg-core 2:1.7.6-2ubuntu7.1
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
CurrentDmesg:
[ 24.966742] svc: failed to register lockdv1 RPC service (errno 97).
[ 24.969769] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 24.982557] NFSD: starting 90-second grace period
Date: Thu Jun 17 09:21:29 2010
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Xubuntu 9.10 "Karmic Koala" - Release i386 (20091028.3)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=6e59ee69-8a9c-4b6a-9f96-f153a5f28f93 ro quiet splash modeset=0
ProcEnviron:
LANG=lv_LV.utf8
SHELL=/bin/bash
SourcePackage: xorg-server
dmi.bios.date: 06/27/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.30
dmi.board.name: 775i65G.
dmi.board.version: 2.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd06/27/2006:svn:pn775i65G.:pvr2.00:rvn:rn775i65G.:rvr2.00:
dmi.product.name: 775i65G.
dmi.product.version: 2.00
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-22-generic
i865 is supported on Lucid but we are not backporting fixes any longer. We've found the driver support for the 8xx chips is quite fragile - a fix for one particular chip can break others that are only slightly different, so SRUs have too high a risk of regression to pursue them.
Often with random screensaver settings the flaw is due to a 3D opengl effect triggering an underlying bug in the mesa driver for 8xx. Disabling 3D and/or not using 3D screensavers is the workaround in this case. I do not know if Chrome uses opengl or 3d in any form, but if it does it could be affected similarly.