Package: kdump-tools
Version: 1:1.6.5-1
Severity: important
Dear Maintainer,
Installed kdump-tools appear to work, echo 'c' | sudo tee /proc/sysrq-trigger
boots the crashkernel and
takes a dump and reboots, but attempting to use "crash" on the dump in a way
that works
in other configurations (e.g. crash /usr/lib/debug/boot/vmlinux-1234
/var/crash/1234/dump.1234) reports
(in this example, on buster, with -d1):
crash: page excluded: kernel virtual address: c19546a4 type: "possible"
WARNING: cannot read cpu_possible_map
crash: page excluded: kernel virtual address: c195469c type: "present"
WARNING: cannot read cpu_present_map
crash: page excluded: kernel virtual address: c19546a0 type: "online"
WARNING: cannot read cpu_online_map
crash: page excluded: kernel virtual address: c1954698 type: "active"
WARNING: cannot read cpu_active_map
crash: page excluded: kernel virtual address: c18c769c type: "pv_init_ops"
crash: page excluded: kernel virtual address: c1a92268 type:
"shadow_timekeeper xtime_sec"
xtime timespec.tv_sec: 9aee2b: Tue Apr 28 08:25:15 1970
crash: page excluded: kernel virtual address: c18bb1c4 type: "init_uts_ns"
utsname:
sysname:
nodename:
release:
version:
machine:
domainname:
base kernel version: 0.0.0
crash: page excluded: kernel virtual address: c16a9160 type: "accessible check"
crash: /usr/lib/debug/vmlinux-4.19.0-16-686-pae and
/var/crash/202106110101/dump.202106110101 do not match!
And:
# ls -al /var/crash/202106110101/dump.202106110101;file
/var/crash/202106110101/dump.202106110101;
-rw------- 1 root root 21422351 Jun 11 01:01
/var/crash/202106110101/dump.202106110101
/var/crash/202106110101/dump.202106110101: Kdump compressed dump v6, system
Linux, node debian32, release 4.19.0-16-686-pae, version #1 SMP Debian
4.19.181-1 (2021-03-19), machine i686, domain (none)
crashkernel=512M-:192M, on here, changes the behavior to what #989714 describes
on x86_64 -
no printouts from a crashkernel or anything else, no dump ever saved, just an
indefinite hang.
crashkernel=384M-:192M (or 256M) does not hang, but produces an equally useless
"dump".
According to the console output when this happens, "makedumpfile Completed"
both times, and
dmesg's output appears intact and complete.
(I neglected to mention this in #989714, but these are all on VirtualBox-backed
VMs.)
Please let me know if there's anything further I can do to help debug this.
- Rich
-- System Information:
Debian Release: 10.9
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.19.0-16-686-pae (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages kdump-tools depends on:
ii bsdmainutils 11.1.2+b1
ii debconf [debconf-2.0] 1.5.71
ii file 1:5.35-4+deb10u2
ii kexec-tools 1:2.0.18-1
ii linux-base 4.6
ii lsb-base 10.2019051400
ii makedumpfile 1:1.6.5-1
ii ucf 3.0038+nmu1
Versions of packages kdump-tools recommends:
ii initramfs-tools-core 0.133+deb10u1
kdump-tools suggests no packages.
-- debconf information:
* kdump-tools/use_kdump: true
