Comment 8 for bug 1228109

Christopher Penalver, my apologies for having been imprecise. I know that the instructions in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1228109/comments/5 were not related to linux-crashdump.

According to https://wiki.ubuntu.com/Kernel/CrashdumpRecipe?action=show&redirect=KernelTeam%2FCrashdumpRecipe ,
linux-crashdump should also create a crash log in /var/crash. This is part of your instructions in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1228109/comments/3, which is what I followed. However, /var/crash is empty after the crashes. I uploaded the crash file in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1228109/comments/4 because it was the only one that was in the folder after a crash. I did not realize that it was unrelated to the system crash. I then deleted all the crash logs as per your post https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1228109/comments/5, which then made me realize that the system crashes do not produce logs.

I did not try the remote capture procedure, since https://help.ubuntu.com/community/DebuggingSystemCrash#Remote_debugging says "Some crashes [...] are impossible to reproduce on the text console. The best way is then to use a second computer [...] using ssh."

The crash is reproducible on the text console. It does not produce any output there. I will try the remote login next and see if it provides any additional information. SSH to the affected machine after it has crashed is not possible.