@Brian Thanks for the suggestion. I enabled apport on my 10.04 server. I forced the crash. The server seemed to reboot extremely fast. However, there was not file written to /var/crash. If I reboot and try perform the crash again, I get the same results.
I tried forcing a crash again after the very fast reboot(Without rebooting after the first crash attempt). I get a stack trace on the console, which I will attach. The file name is LucidCrashdumpConsole.jpg Here is the crashdump specific info from dmesg: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-2.6.32-27-server root=/dev/mapper/dl3802--1-root ro crashkernel=384M-2G:64M,2G-:128M quiet [ 0.000000] Reserving 128MB of memory at 32MB for crashkernel (System RAM: 4863MB) [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-27-server root=/dev/mapper/dl3802--1-root ro crashkernel=384M-2G:64M,2G-:128M quiet I also enabled apport on my netbook, which is running Natty. I get a little better results. I force the crash, and the system reboots, but takes a long time. It appears this is because its generating a crash file. It eventually hangs and I have to power cycle it. Looking in the /var/crash directory I get a directory with the timestamp. But then in that directory, I see a file named dump-incomplete. I will test further and see what else I can find. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/710733 Title: LKCD Not Executing kexec Properly -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
