** Description changed: I feel a bit silly reporting this bug seeing as it's not consistently reproducible. It just sort of happens on occasion. The only thing that seems to be constant is that the computer's fairly busy when it happens and rather than the CPU idling afterward, it goes nuts. By "goes nuts" I mean the CPU fan spins up and *lots* of hot air come out. I've heard idling is usually what happens after the crash. It's a laptop, always running in GUI mode, so no console for a backtrace. No serial or com ports, so I can't use a serial console to try to catch it. Even if I could, that whole thing about "not reliably reproducible" would mean that even if I *could* rig a USB console to do the job, I'd still need to find some way to reproduce it. I'd say this happens once every few days. This time, KVM was being very busy, so that may have contributed, but it was the first time I've used KVM and definitely not my first kernel panic on this system. I believe it's a kernel panic based on the fact that everything locks up and the Caps Lock light is blinking (I have no NumLock or ScrollLock light). Ctrl+Alt+Backspace, switching TTYs, and "Magic SysRq" are all useless. I'm guessing the kernel is so hard-locked it won't accept any interrupts. 2.6.24-21-generic #1 SMP Mon Aug 25 16:57:51 UTC 2008 x86_64 GNU/Linux Ubuntu 2.6.24-21.42-generic Hardy 8.04.1 - I'm not sure about dmesg. It just gives the output for the current - boot. /var/log/dmesg seems to also just be the current boot. - /var/log/dmesg.0 doesn't have any record of the kernel panic. + There's nothing in dmesg, and nothing in syslog in the 18 minutes before + the crash (last thing being some iptables junk about a printer on + broadcast).
-- Kernel panic (hard lockup) on Asus Z37E with Hardy https://bugs.launchpad.net/bugs/278030 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
