aboutsummaryrefslogtreecommitdiffstats
path: root/package/boot/kexec-tools/files
Commit message (Collapse)AuthorAgeFilesLines
* kexec-tools: issue warning when dd'ing vmcorePhilip Prindeville2018-02-111-0/+2
| | | | | | | | With no warning, it just looks like the box has hung during boot. We don't want users resetting it without having captured a crashdump. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* kexec-tools: bump version and add support for crashdump kernelDaniel Golle2017-06-093-0/+200
split kexec-tools into two packages, kexec and kdump. * kexec to simply execute a new kernel * kdump is for loading and collecting debris of a crashed kernel with support for kdump forensics. In order to properly support booting into a crashkernel, an init script as well as UCI configuration has been added. As modifying the kernel cmdline is required for this to work in x86 platforms use an uci-defaults script to modify /boot/grub/grub.cfg. To test collecting crash information, use the 'c' sysrq-trigger, ie. echo c > /proc/sysrq-trigger This should result in the crash kernel being executed and (depending on the configution) dmesg and/or vmcore getting saved. To check if the crash kernel was loaded properly, use the 'status' command of the kdump init script. Signed-off-by: Daniel Golle <daniel@makrotopia.org>