LKCD Not Executing kexec Properly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Canonical Kernel Team | ||
Oneiric |
Invalid
|
High
|
Canonical Kernel Team |
Bug Description
I'm attempting to use linux-crashdump to debug an issue. I've been following the documentation at:
https:/
The exact steps I've done are:
Installed linux-crashdump:
sudo apt-get install linux-crashdump
Rebooted system to enable crashdump.
My test to force a crash:
echo 1 | sudo tee /proc/sys/
echo c | sudo tee /proc/sysrq-trigger
However, I no files are ever generated in /var/crash. In fact the /var/crash directory didn't exist until I created it. After executing echo c | sudo tee /proc/sysrq-trigger the system locks up. There is a stack trace on the console, but I have not been able to get the system write this trace to a file. I captured some screen shots, which are attached. I also attached an "alt+sysrq t" trace.
I am able to execute kexec manually, and the system will reboot:
/sbin/kexec --command-
I've tried this on Lucid, Maverick and Natty using both KVM VMs and physical machines(AMD Based, and Intel based. All these tests fail with the same results(The system flocks up and not crashdump data is generated).
For a consistant test case, I am using a netbook, but I can also reproduce this on a server if that is preferred. The netbooks cpu is: Single CPU: Intel(R) Atom(TM) CPU N455 @ 1.66GHz
I have also tried booting with nosmp, with no change.
I will attach the output from ubuntu-bug to this report.
Changed in linux-meta (Ubuntu): | |
importance: | Undecided → High |
affects: | linux-meta (Ubuntu) → linux (Ubuntu) |
tags: | added: rls-mgr-o-tracking |
tags: | added: rls-mgr-o-tracking |
I haven't tried to recreate this yet myself but looking at the bug it occurred to me that apport is disabled for all those releases. Could you make sure apport is on by editing /etc/default/ apport? Thanks in advance.