Hi On Samstag, 26. Juli 2008, you wrote: > On Sun, Jun 1, 2008 at 20:45:54 +0200, Stefan Lippers-Hollmann wrote: > > > Hi > > > > On Sonntag, 1. Juni 2008, you wrote: > > [...] > > > Is the machine completely dead with the plain 2.2.1 driver? Can you > > > ping? ssh? catch the log? > > > > Yes, it is completely dead, open ssh connections trying to gather last bits > > from tail -f /var/log/messages stall immediately (unfortunately the > > notebook has no serial connectors for a serial console), pings get no > > answer - a hard poweroff is the only recovery. > > > Hi, In the mean time I've been setting up netconsole, which (I can only start it just before invoking kdm, as the ethernet driver (tulip) doesn't really like netconsole) only shows the following: netconsole: network logging started [drm] Initialized drm 1.1.0 20060810 mtrr: no more MTRRs available [drm] Initialized savage 2.4.1 20050313 on minor 0 mtrr: no more MTRRs available mtrr: base(0xf2000000) is not aligned on a size(0x5000000) boundary agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode Then, as soon as the X server tries to start, the system locks up immediately with a black screen and the fan humming at full speed. > could you try to find out where the hang occurs? You can put some calls > to ErrorF() at various points in the driver, and add Option "Log" "sync" > in the ServerFlags section of xorg.conf. I'll try this today, thanks for your hints > If we don't manage to track this down soon, I'd be tempted to revert to > an earlier version of the savage driver for lenny. The current version with 02_temporary_revert_pciaccess.diff applied and the following commits reverted a01c9d12938f977a4310e0547866f01517059a3e 69eca3b8340966874ee3ffdc0d0a3f73de7a816a 908b155161ebb6cd506f43a3987e4d146ef5b330 88141fd21214c501cafed73b1bba084b8a2bb929 fd2a598e64a522c028a20444379fa200a5724e62 works reliably for me since early june, (the earlier version did as well, of course). Just now, I managed to start X with xserver-xorg-video-savage 1:2.2.1-1 (without any changes) once (Xorg.0.log_2.2.1-1-working.log.gz attached), it failed/ crashed for the following reboots though (attached as Xorg.0.log_2.2.1-1-crashed.log.gz). (II) SAVAGE(0): [agp] agpTextures handle = 0xec100000 (II) SAVAGE(0): [drm] aperture handle = 0xf2000000 (II) SAVAGE(0): [drm] Enabling ShadowStatus for DRI. -(II) SAVAGE(0): [drm] Status handle = 0x09d62000 -(II) SAVAGE(0): [drm] Status page mapped at 0xb19c7000 +(II) SAVAGE(0): [drm] Status handle = 0x0e6ae000 +(II) SAVAGE(0): [drm] Status page mapped at 0xb1833000 (II) SAVAGE(0): [dri] visual configs initialized (**) SAVAGE(0): DRI is enabled (--) SAVAGE(0): Chose mode 118 at 60Hz. -(II) SAVAGE(0): virtualX:1024,virtualY:768 -[...] > Cheers, > Julien Regards Stefan Lippers-Hollmann
Attachment:
Xorg.0.log_2.2.1-1-crashed.log.gz
Description: GNU Zip compressed data
Attachment:
Xorg.0.log_2.2.1-1-working.log.gz
Description: GNU Zip compressed data
Attachment:
xorg.conf.gz
Description: GNU Zip compressed data
Attachment:
signature.asc
Description: This is a digitally signed message part.