Bug#483989: xserver-xorg-video-savage: system freeze while starting X
Hello, I have prepared savage 2.2.1-2 to fix this. Could all of you please test the package available at http://newpeople.debian.org/~bgoglin/savage/ and report back whether it works? I want to be sure it doesn't break for anybody. thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
On Friday 05 September 2008, you wrote: Joseph Neal wrote: On Friday 05 September 2008, you wrote: Hello, I have prepared savage 2.2.1-2 to fix this. Could all of you please test the package available at http://newpeople.debian.org/~bgoglin/savage/ and report back whether it works? I want to be sure it doesn't break for anybody. thanks, Brice It was fixed quite a while back for me. I know, but I want to be sure that this new packages fixes #483989 without breaking anything else. Gottcha. Seems to work OK. thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
Hi On Freitag, 5. September 2008, Brice Goglin wrote: Hello, I have prepared savage 2.2.1-2 to fix this. Could all of you please test the package available at http://newpeople.debian.org/~bgoglin/savage/ and report back whether it works? I want to be sure it doesn't break for anybody. Working reliably for me, thanks! Regards Stefan Lippers-Hollmann Post scriptum: I still intend to debug it even further, but I'm physically away from the notebook during the week. signature.asc Description: This is a digitally signed message part.
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
Hi Sorry, I've been physically away from the notebook since early august till last weekend. On Dienstag, 26. August 2008, Brice Goglin wrote: On Sun, Jun 01, 2008 at 08:49:18PM +0200, Stefan Lippers-Hollmann wrote: 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. Pinging again to make sure the bug didn't disappear by chance :) Unfortunately it hasn't gone away and is still present on today's sid and kernel 2.6.26.3. Otherwise, we need to decide between: 1) reverting to 2.1.3-5 which worked fine except bug #481739 (which looks strange to me) This version did/ does work fine for me. 2) reapplying 02_temporary_revert_pciaccess.diff and reverting 5 pciaccess commits (merging all of them in the 02_revert). Not sure how stable this one would be. I've been running this[1] reliably since I first encountered the problem, sorry I'm not too familiar with git and X.org's buildsystem generation, so the quilt series looks a bit messy, but was nevertheless quite helpful for me to pinpoint the problematic commits. Maybe we can start with (2) for now, and switch to (1) as the ultimate solution if needed before Lenny gets released? Now I notice Tormod's suggestions and will try them tonight, hopefully I get around to adding some ErrorF() breakpoints to the source tommorow, like you suggested. Regards Stefan Lippers-Hollmann [1] http://sidux.com/debian/pool/fix.main/x/xserver-xorg-video-savage/xserver-xorg-video-savage_2.2.1-1+c0.sidux.1.dsc signature.asc Description: This is a digitally signed message part.
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
Hi
strace Xorg over ssh and a wired connection freezes at:
ioctl(9, MTRRIOC_GET_ENTRY, 0xbfd7caec) = 0
ioctl(9, MTRRIOC_GET_ENTRY, 0xbfd7caec) = 0
ioctl(9, MTRRIOC_GET_ENTRY, 0xbfd7caec) = 0
ioctl(9, MTRRIOC_GET_ENTRY, 0xbfd7caec) = 0
ioctl(9, MTRRIOC_GET_ENTRY, 0xbfd7caec) = 0
ioctl(9, MTRRIOC_GET_ENTRY, 0xbfd7caec) = 0
ioctl(9, MTRRIOC_GET_ENTRY, 0xbfd7caec) = 0
ioctl(9, MTRRIOC_GET_ENTRY, 0xbfd7caec) = 0
ioctl(9, MTRRIOC_GET_ENTRY, 0xbfd7caec) = -1 EINVAL (Invalid argument)
write(0, (II) SAVAGE(0): 9348 kB of Videor..., 82) = 82
fsync(0)= 0
write(0, (II) SAVAGE(0): Sufficient Videor..., 53) = 53
fsync(0)= 0
write(0, (II) SAVAGE(0): [drm] bpp: 32 dep..., 40) = 40
fsync(0)= 0
write(0, (II) SAVAGE(0): [drm] Sarea 2200+..., 43) = 43
fsync(0)= 0
geteuid32() = 0
write(0, drmOpenDevice: node name is /dev/..., 43) = 43
fsync(0)= 0
stat64(/dev/dri, 0xbfd7c968) = -1 ENOENT (No such file or directory)
mkdir(/dev/dri, 0755) = 0
chown32(/dev/dri, 0, 0) = 0
chmod(/dev/dri, 0755) = 0
stat64(/dev/dri/card0, 0xbfd7c968)= -1 ENOENT (No such file or directory)
unlink(/dev/dri/card0)= -1 ENOENT (No such file or directory)
mknod(/dev/dri/card0, S_IFCHR|0666, makedev(226, 0)) = 0
chown32(/dev/dri/card0, 0, -1)= 0
chmod(/dev/dri/card0, 0666) = 0
open(/dev/dri/card0, O_RDWR|O_LARGEFILE) = -1 ENXIO (No such device or
address)
write(0, drmOpenDevice: open result is -1,..., 62) = 62
fsync(0)= 0
unlink(/dev/dri/card0)= 0
mknod(/dev/dri/card0, S_IFCHR|0666, makedev(226, 0)) = 0
chown32(/dev/dri/card0, 0, -1)= 0
chmod(/dev/dri/card0, 0666) = 0
open(/dev/dri/card0, O_RDWR|O_LARGEFILE) = -1 ENXIO (No such device or
address)
write(0, drmOpenDevice: open result is -1,..., 62) = 62
fsync(0)= 0
write(0, drmOpenDevice: Open failed\n..., 27) = 27
fsync(0)= 0
unlink(/dev/dri/card0)= 0
access(/proc/dri/0, R_OK) = -1 ENOENT (No such file or directory)
geteuid32() = 0
write(0, drmOpenDevice: node name is /dev/..., 43) = 43
fsync(0)= 0
stat64(/dev/dri, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
stat64(/dev/dri/card0, 0xbfd7c948)= -1 ENOENT (No such file or directory)
unlink(/dev/dri/card0)= -1 ENOENT (No such file or directory)
mknod(/dev/dri/card0, S_IFCHR|0666, makedev(226, 0)) = 0
chown32(/dev/dri/card0, 0, -1)= 0
chmod(/dev/dri/card0, 0666) = 0
open(/dev/dri/card0, O_RDWR|O_LARGEFILE) = -1 ENXIO (No such device or
address)
write(0, drmOpenDevice: open result is -1,..., 62) = 62
fsync(0)= 0
unlink(/dev/dri/card0)= 0
mknod(/dev/dri/card0, S_IFCHR|0666, makedev(226, 0)) = 0
chown32(/dev/dri/card0, 0, -1)= 0
chmod(/dev/dri/card0, 0666) = 0
open(/dev/dri/card0, O_RDWR|O_LARGEFILE) = -1 ENXIO (No such device or
address)
write(0, drmOpenDevice: open result is -1,..., 62) = 62
fsync(0)= 0
write(0, drmOpenDevice: Open failed\n..., 27) = 27
fsync(0)= 0
unlink(/dev/dri/card0)= 0
access(/proc/dri/0, R_OK) = -1 ENOENT (No such file or directory)
open(/proc/sys/kernel/modprobe, O_RDONLY) = 10
read(10, /sbin/modprobe\n..., 1023) = 15
close(10) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0xb7d546f8) = 2546
waitpid(2546, [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0) = 2546
--- SIGCHLD (Child exited) @ 0 (0) ---
write(0, drmOpenByBusid: Searching for Bus..., 53) = 53
fsync(0)= 0
geteuid32() = 0
write(0, drmOpenDevice: node name is /dev/..., 43) = 43
fsync(0)= 0
stat64(/dev/dri, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
stat64(/dev/dri/card0, 0xbfd7c8d8)= -1 ENOENT (No such file or directory)
unlink(/dev/dri/card0)= -1 ENOENT (No such file or directory)
mknod(/dev/dri/card0, S_IFCHR|0666, makedev(226, 0)) = 0
chown32(/dev/dri/card0, 0, -1)= 0
chmod(/dev/dri/card0, 0666) = 0
open(/dev/dri/card0, O_RDWR|O_LARGEFILE) = 10
write(0, drmOpenDevice: open result is 10,..., 39) = 39
fsync(0)= 0
write(0, drmOpenByBusid: drmOpenMinor retu..., 40) = 40
fsync(0)= 0
ioctl(10, DECODER_SET_PICTURE, 0xbfd7c9e0) = 0
ioctl(10, DECODER_GET_CAPABILITIES, 0xbfd7c9e4) = 0
ioctl(10, DECODER_GET_CAPABILITIES, 0xbfd7c9e4) = 0
write(0, drmOpenByBusid: drmGetBusid repor..., 53) = 53
fsync(0)= 0
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
On Sun, Jun 01, 2008 at 08:49:18PM +0200, Stefan Lippers-Hollmann wrote: 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. Pinging again to make sure the bug didn't disappear by chance :) Otherwise, we need to decide between: 1) reverting to 2.1.3-5 which worked fine except bug #481739 (which looks strange to me) 2) reapplying 02_temporary_revert_pciaccess.diff and reverting 5 pciaccess commits (merging all of them in the 02_revert). Not sure how stable this one would be. Maybe we can start with (2) for now, and switch to (1) as the ultimate solution if needed before Lenny gets released? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
You listed 5 reverted commits above. Did you try to narrow down which ones you need to revert? Or are they all broken by the 02_temporary_revert_pciaccess.diff? You can also try to start the server with sudo strace Xorg from another machine, or sudo gdb Xorg. Sometimes the debugging makes the execution slow enough that you will get something in the log. If you try gdb, setting breakpoints around/inside SavageMapMem might be an idea as well, to find where it blows up. And does the standard tricks of Option BusType PCI and Option DRI off make any change? Cheers, Tormod -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
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(0xf200) is not aligned on a size(0x500) boundary agpgart: Found an AGP 2.0 compliant device at :00:00.0. agpgart: Putting AGP V2 device at :00:00.0 into 0x mode agpgart: Putting AGP V2 device at :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 = 0xec10 (II) SAVAGE(0): [drm] aperture handle = 0xf200 (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 Xorg.0.log_2.2.1-1-crashed.log.gz Description: GNU Zip compressed data Xorg.0.log_2.2.1-1-working.log.gz Description: GNU Zip compressed data xorg.conf.gz Description: GNU Zip compressed data signature.asc Description: This is a digitally signed message part.
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
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, 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. 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. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
On Sun, 01 Jun 2008 20:30:38 +0200 Brice Goglin [EMAIL PROTECTED] wrote: I am adding to CC 2 person that may experience the same problem since 2.1.3-4 was broken for them. Joseph and Pascal, can you report back whether savage 2.2.1 from unstable is broken for you as well? No problem here I have been getting a lot of this in kern.log and on vt0 when X is running: Jun 2 19:03:04 dsl017-124-002 kernel: [258139.997754] mtrr: MTRR 3 not used Jun 2 19:03:04 dsl017-124-002 kernel: [258139.999159] mtrr: MTRR 4 not used Jun 2 19:03:04 dsl017-124-002 kernel: [258139.999804] mtrr: MTRR 6 not used Jun 2 19:03:11 dsl017-124-002 kernel: [258148.007481] mtrr: no more MTRRs available Jun 2 19:03:11 dsl017-124-002 kernel: [258148.007603] mtrr: base(0xd200) is not aligned on a size(0x500) boundary Jun 2 19:03:11 dsl017-124-002 kernel: [258148.008695] mtrr: no more MTRRs available Jun 2 19:03:11 dsl017-124-002 kernel: [258148.008783] mtrr: base(0xd200) is not aligned on a size(0x500) boundary Jun 2 19:03:11 dsl017-124-002 kernel: [258148.009607] mtrr: no more MTRRs available Jun 2 19:03:11 dsl017-124-002 kernel: [258148.009681] mtrr: base(0xd200) is not aligned on a size(0x500) boundary Compositing doesn't work in KDE 4.1 beta but I don't know if it should be expected to. Otherwise everything seems to work as well as it ever has. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
On Sun, Jun 01, 2008 at 08:30:38PM +0200, Brice Goglin wrote: severity 483989 grave thank you Stefan Lippers-Hollmann wrote: Package: xserver-xorg-video-savage Version: 1:2.2.1-1 Severity: important After upgrading xserver-xorg-video-savage from 1:2.1.3-5 to current unstable (1:2.2.1-1), the system freezes immediately with a black screen (no flashing cursor) while trying to start X, without any recoverable error messages. Changing DefaultColorDepth from 24 to 16 bit shows no results. As disabling 02_temporary_revert_pciaccess.diff from 1:2.1.3-5 seems to result in the same system freeze, re- enabling it for 1:2.2.1-1 and dropping conflicting upstream commits: a01c9d12938f977a4310e0547866f01517059a3e 69eca3b8340966874ee3ffdc0d0a3f73de7a816a 908b155161ebb6cd506f43a3987e4d146ef5b330 88141fd21214c501cafed73b1bba084b8a2bb929 fd2a598e64a522c028a20444379fa200a5724e62 results in a working system again. Is the machine completely dead with the plain 2.2.1 driver? Can you ping? ssh? catch the log? I was kind of expecting that upstream did not fix in 2.2.1 everything we disabled in 2.1.3-5. Let's bump the severity to prevent 2.2.1 from entering testing, it's better to keep 2.1.3-5 for now. I am adding to CC 2 person that may experience the same problem since 2.1.3-4 was broken for them. Joseph and Pascal, can you report back whether savage 2.2.1 from unstable is broken for you as well? Hello, using 2.2.1 from unstable, without problems, on my laptop. I reported problems a long time ago, and the driver works fine since. A few hints: which version of gcc do you use to compile the kernel ? I remember having troubles with gcc-4.3, while gcc-4.2 is fine. Regards Pascal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
Hi On Montag, 2. Juni 2008, Pascal A. Dupuis wrote: On Sun, Jun 01, 2008 at 08:30:38PM +0200, Brice Goglin wrote: [...] After upgrading xserver-xorg-video-savage from 1:2.1.3-5 to current unstable (1:2.2.1-1), the system freezes immediately with a black screen (no flashing cursor) while trying to start X, without any recoverable error messages. Changing DefaultColorDepth from 24 to 16 bit shows no results. As disabling 02_temporary_revert_pciaccess.diff from 1:2.1.3-5 seems to result in the same system freeze, re- enabling it for 1:2.2.1-1 and dropping conflicting upstream commits: a01c9d12938f977a4310e0547866f01517059a3e 69eca3b8340966874ee3ffdc0d0a3f73de7a816a 908b155161ebb6cd506f43a3987e4d146ef5b330 88141fd21214c501cafed73b1bba084b8a2bb929 fd2a598e64a522c028a20444379fa200a5724e62 results in a working system again. [...] I am adding to CC 2 person that may experience the same problem since 2.1.3-4 was broken for them. Joseph and Pascal, can you report back whether savage 2.2.1 from unstable is broken for you as well? Hello, using 2.2.1 from unstable, without problems, on my laptop. I reported problems a long time ago, and the driver works fine since. A few hints: which version of gcc do you use to compile the kernel ? I remember having troubles with gcc-4.3, while gcc-4.2 is fine. [...] The kernel has been built with gcc-4.2.4 [1], but to rule out kernel related issues, I've just (re-) tested linux-image-2.6.25-2-686 2.6.25-4 [2] from current sid with the same results in combination with xserver-xorg-video-savage 1:2.2.1-1. As soon as X starts, the system locks up hard, while it works well with 1:2.1.3-5 or 1:2.2.1-1 and 02_temporary_revert_pciaccess.diff etc. applied. Regards Stefan Lippers-Hollmann [1] Linux version 2.6.25-4.slh.3-sidux-686 (Debian 2.6.25-19) ([EMAIL PROTECTED]) (gcc version 4.2.4 (Debian 4.2.4-1)) #1 SMP PREEMPT Fri May 23 21:58:49 UTC 2008 [2] Linux version 2.6.25-2-686 (Debian 2.6.25-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 SMP Tue May 27 15:38:35 UTC 2008 signature.asc Description: This is a digitally signed message part.
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
severity 483989 grave thank you Stefan Lippers-Hollmann wrote: Package: xserver-xorg-video-savage Version: 1:2.2.1-1 Severity: important After upgrading xserver-xorg-video-savage from 1:2.1.3-5 to current unstable (1:2.2.1-1), the system freezes immediately with a black screen (no flashing cursor) while trying to start X, without any recoverable error messages. Changing DefaultColorDepth from 24 to 16 bit shows no results. As disabling 02_temporary_revert_pciaccess.diff from 1:2.1.3-5 seems to result in the same system freeze, re- enabling it for 1:2.2.1-1 and dropping conflicting upstream commits: a01c9d12938f977a4310e0547866f01517059a3e 69eca3b8340966874ee3ffdc0d0a3f73de7a816a 908b155161ebb6cd506f43a3987e4d146ef5b330 88141fd21214c501cafed73b1bba084b8a2bb929 fd2a598e64a522c028a20444379fa200a5724e62 results in a working system again. Is the machine completely dead with the plain 2.2.1 driver? Can you ping? ssh? catch the log? I was kind of expecting that upstream did not fix in 2.2.1 everything we disabled in 2.1.3-5. Let's bump the severity to prevent 2.2.1 from entering testing, it's better to keep 2.1.3-5 for now. I am adding to CC 2 person that may experience the same problem since 2.1.3-4 was broken for them. Joseph and Pascal, can you report back whether savage 2.2.1 from unstable is broken for you as well? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
Hi [sorry that you get this mail twice, I accidentally answered you privately and didn't address the bug ] 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. I was kind of expecting that upstream did not fix in 2.2.1 everything we disabled in 2.1.3-5. Let's bump the severity to prevent 2.2.1 from entering testing, it's better to keep 2.1.3-5 for now. Thanks, the other upstream changes from 2.2.1 seem to be fine so far. I am adding to CC 2 person that may experience the same problem since 2.1.3-4 was broken for them. Joseph and Pascal, can you report back whether savage 2.2.1 from unstable is broken for you as well? Brice Regards Stefan Lippers-Hollmann signature.asc Description: This is a digitally signed message part.
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
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. I was kind of expecting that upstream did not fix in 2.2.1 everything we disabled in 2.1.3-5. Let's bump the severity to prevent 2.2.1 from entering testing, it's better to keep 2.1.3-5 for now. Thanks, the other upstream changes from 2.2.1 seem to be fine so far. I am adding to CC 2 person that may experience the same problem since 2.1.3-4 was broken for them. Joseph and Pascal, can you report back whether savage 2.2.1 from unstable is broken for you as well? Brice Regards Stefan Lippers-Hollmann signature.asc Description: This is a digitally signed message part.
