On Sun, May 13, 2007 at 04:47:32PM -0700, Matthew Dillon wrote: > > :I made this change and shortly got another hang. I was in X messing > :around with a vkernel and was typing away when everything froze. I > :waited a bit after trying CTRL-ALT-ESC, CTRL-ALT-BKSP, CTRL-ALT-DEL, > :and anything else I could think of, but the machine was frozen. So I > :held the power button down for 5s or so and rebooted. After checking > :my filesystems, what do you know another coredump was found and it is > :the same as last time. I am positive that I'm not looking at the > :wrong vmcore. I am inclined to believe that no coredump was ever > :written to my swap partition or perhaps only a part of a coredump was > :written before I power cycled the laptop. I'm going to try to trigger > :this running from the system console versus in X and see if I can get > :into the debugger. > : > :Joe > > If you have a serial port you can run a serial console to another > machine. If not you do have another option, and that is to compile > a kernel with: > > options DDB_UNATTENDED > > Hopefully when it crashes it will be able to write the core out. If > it does, you should see the hard drive light for your laptop flicker > or go solid for however long it takes to write out the core. > > Note: Do *NOT* hard power cycle your machine while it is writing to the > hard drive. That's a great way to destroy the hard drive. >
This has happened again. The same as the first time the machine locks up hard when doing a 'shutdown -h now' via icewm's shutdown function. I had DDB_UNATTENDED compiled in my kernel but to no avail. I did notice the fan ramp up in speed but there was absolutely no HDD activity indicated by the HDD LED. I certainly can't rule out icewm/xorg as the culprit. Joe
