Well, MythTV wasn't the problem. It's happened again, this time after I restarted from an update to clamAV and a few other programs. They symptoms were the same, except that this time the deadlock was preceded by a loud CLICK as my disk head parked. I was able to close most of my running applications cleanly, then attempt to log out. Eventually my Xorg session died but I'm not sure if it died cleanly. I was then stuck on the console right where the login screen should start up, but no dice.
The packages I installed before the reboot were (courtesy of synaptic): Upgraded the following packages: clamav (0.94.dfsg.2-1ubuntu0.3~hardy3) to 0.94.dfsg.2-1ubuntu0.3~hardy4 clamav-base (0.94.dfsg.2-1ubuntu0.3~hardy3) to 0.94.dfsg.2-1ubuntu0.3~hardy4 clamav-freshclam (0.94.dfsg.2-1ubuntu0.3~hardy3) to 0.94.dfsg.2-1ubuntu0.3~hardy4 gparted (0.3.5-1ubuntu3) to 0.3.5-1ubuntu5 libclamav5 (0.94.dfsg.2-1ubuntu0.3~hardy3) to 0.94.dfsg.2-1ubuntu0.3~hardy4 libwmf0.2-7 (0.2.8.4-6) to 0.2.8.4-6ubuntu0.8.04.1 linux-generic (2.6.24.23.25) to 2.6.24.24.26 linux-headers-generic (2.6.24.23.25) to 2.6.24.24.26 linux-image-generic (2.6.24.23.25) to 2.6.24.24.26 linux-libc-dev (2.6.24-23.52) to 2.6.24-24.53 linux-restricted-modules-common (2.6.24.16-23.56) to 2.6.24.17-24.1 linux-restricted-modules-generic (2.6.24.23.25) to 2.6.24.24.26 nvidia-glx-new (169.12+2.6.24.16-23.56) to 169.12+2.6.24.17-24.1 Installed the following packages: linux-headers-2.6.24-24 (2.6.24-24.53) linux-headers-2.6.24-24-generic (2.6.24-24.53) linux-image-2.6.24-24-generic (2.6.24-24.53) linux-restricted-modules-2.6.24-24-generic (2.6.24.17-24.1) linux-ubuntu-modules-2.6.24-24-generic (2.6.24-24.39) After which I installed a load of Ruby packages. I'm going to post all of the relevant files (strangely /var/crash was empty) after this one. ** Attachment added: "commit log from synaptic" http://launchpadlibrarian.net/26332475/commit.log.5.4.1231 -- Hardy: ksoftirqd, dd, klogd use 100% CPU, Disk https://bugs.launchpad.net/bugs/368324 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
