Bug#700418: kdump-tools: default debug kernel search path is incorrect
Package: kdump-tools
Version: 1.3.5-1
Severity: normal
In /usr/share/doc/kdump-tools/README.Debian the following text appears:
4. Debug Kernel
You *should* have a debug kernel in order for makedumpfile to process
the vmcore file. Without a debug kernel, the transfer process is
reduced to using "makedumpfile -d 1". Options:
A) If /usr/lib/debug/vmlinux-$(uname -r) exists, kdump-tools will
use that kernel.
B) Explicitly set DEBUG_KERNEL in /etc/default/kdump-tools to
point to your debug kernel.
C) None of the above. makedumpfile will still work, but your
dumpfile will be larger and take longer to save to disk.
However all (?) the default -dbg Debian kernel packages put the kernels
in /usr/lib/debug/boot/:
http://packages.debian.org/squeeze/amd64/linux-image-2.6.32-5-amd64-dbg/filelisthttp://packages.debian.org/squeeze/amd64/linux-image-2.6.32-5-xen-amd64-dbg/filelist
http://packages.debian.org/squeeze-backports/amd64/linux-image-3.2.0-0.bpo.4-amd64-dbg/filelist
http://packages.debian.org/wheezy/amd64/linux-image-3.2.0-4-amd64-dbg/filelist
IMHO it would make sense to change (A) so that things worked automagically.
If someone had a truly custom kernel, then tweaking DEBUG_KERNEL per (B)
would make sense, but the 'standard' Debian tools should work with the
standard Debian kernels.
The other options would be to remove the boot/ from the debug kernel path.
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-0.bpo.4-amd64 (SMP w/24 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages kdump-tools depends on:
ii kexec-tools 1:2.0.1-4 kexec tool for kexec reboots
ii makedumpfile 1.3.5-1 VMcore extraction tool
kdump-tools recommends no packages.
kdump-tools suggests no packages.
-- Configuration Files:
/etc/default/kdump-tools changed [not included]
-- no debconf information
Reply to: