= Setup =
- the linux-crashdump need to be installed.
- kdump should be enabled by /etc/default/kdump-tools or dpkg-configurate.
- kexec-tools will be installed, but we don't want kexec-tools handle reboots, only use kexe for kdump.
- the system needs to have enough memory to load the kernel and save the crash file, the current default settings is 512M-:192M. It may not enough to dump the file. I think Ubuntu should change it using auto[1], and does not store any crash on a machine less than 4G memory.
- we may consider to use kernel panic to capture other sockup issues[2].
= Bug report =
- there are several tools can be used to submit the crash file to launchpad. But I think it would best to use a checkbox test job capture the crash file, and use apport via qabro to submit the bug to launchpad.
There are a few things that should be considered.
= Setup = kdump-tools or dpkg-configurate.
- the linux-crashdump need to be installed.
- kdump should be enabled by /etc/default/
- kexec-tools will be installed, but we don't want kexec-tools handle reboots, only use kexe for kdump.
- the system needs to have enough memory to load the kernel and save the crash file, the current default settings is 512M-:192M. It may not enough to dump the file. I think Ubuntu should change it using auto[1], and does not store any crash on a machine less than 4G memory.
- we may consider to use kernel panic to capture other sockup issues[2].
= Bug report =
- there are several tools can be used to submit the crash file to launchpad. But I think it would best to use a checkbox test job capture the crash file, and use apport via qabro to submit the bug to launchpad.
[1] [0/7] Implement crashkernel=auto - Patchwork - https:/ /lore.kernel. org/patchwork/ cover/166256/ CrashdumpRecipe - Ubuntu Wiki - https:/ /wiki.ubuntu. com/Kernel/ CrashdumpRecipe
[2] Kernel/