Package: linux-2.6 Version: 2.6.17-3 Severity: important See also: #391955 (same machine) My X40 laptop hangs itself up with both 2.6.17-2-686 and 2.6.18-1-686 kernels *without sending a kernel panic via netconsole* during the rc2.d startup sequence. lapse:~# ls /etc/rc2.d K00nstxcd@ S20cpufrequtils@ S20openbsd-inetd@ S89anacron@ K00openvpn@ S20cupsys@ S20postfix@ S89atd@ K08vmware@ S20dbus@ S20rsync@ S89cron@ README S20dictd@ S20smartmontools@ S90vmware@ S10syslog-ng@ S20gpm@ S20ssh@ S99fail2ban@ S15ibm-acpi@ S20hotkey-setup@ S20sysfsutils@ S99rc.local@ S19xdm@ S20ifplugd@ S23ntp@ S99rmnologin@ S20acpid@ S20laptop-mode@ S25bluetooth@ S99stop-bootlogd@ S20apt-index-watcher@ S20makedev@ S30mpd@ S20cpufreqd@ S20mixmaster@ S30squid@ With 2.6.17, the machine prints "Starting printing deamon: cupsd" and hangs itself up hard. No sysrq-b or ctrl-alt-del make it restart, I have to cold-cycle it (no reset button on the X40). With 2.6.18, X blanks the screen just after starting cupsd, then hangs. In both cases, the machine becomes equally unresponsive to everything. No lights flash; hard lock. If I boot into single-mode and start acpid manually, then reboot, it freezes during the reboot as well. It shuts down processes and then says "Will now reboot" followed by "Rebooting system" and hangs right there and requires a cold-cycle. If I move xdm to S99, where it is normally, or even just S21, the boot process gets past cupsd and X starts fine, and it does not hang itself up on reboot. The problem does *not* occur with 2.6.16-1-686, and I have always started xdm at S19. The problem with the machine freezing while starting X first appeared after the support technician replaced a defective keyboard in the middle of July, so probably after the 2.6.17-3 upgrade; I do remember not using 2.6.17 right from the start due to madwifi-related problems a friend of mine was experiencing. In July, it was possible then to work around it by going to single-user mode and pressing ctrl-d, so I thought it was a simple timing issue. The machine would then run pretty stable. I did not have dm-crypt partitions back then. Since then, I have reinstalled the machine. The problem resurfaced two weeks ago, and I called the technician, suspecting a hardware defect. Together, we replaced the motherboard/CPU/RAM/e1000/graphics card combo, tried with and without the WLAN and Bluetooth cards, tried two mirrored harddisks, and replaced the keyboard again; the problem persists -- it is thus somewhat unlikely to be a hardware problem. Please refer to #391955 for information about the machine hardware. And please let me know whether you need more information. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-2-amd64 Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- .''`. martin f. krafft <madduck@debian.org> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems
Attachment:
signature.asc
Description: Digital signature (GPG/PGP)