Verification done for Bionic. bionic-updates: failure.
$ dpkg -s makedumpfile | grep -i version Version: 1:1.6.5-1ubuntu1~18.04.4 [ 8.369266] kdump-tools[513]: Starting kdump-tools: * running makedumpfile -c -d 31 /home/ubuntu/201909170743/vmcore.201909170743 /var/crash/202006171242/dump-incomplete [ 8.382379] kdump-tools[513]: mv: cannot stat '/var/crash/202006171242/dump-incomplete': No such file or directory [ 8.385529] kdump-tools[513]: * kdump-tools: saved vmcore in /var/crash/202006171242 [ 8.405479] kdump-tools[513]: * running makedumpfile --dump-dmesg /home/ubuntu/201909170743/vmcore.201909170743 /var/crash/202006171242/dmesg.202006171242 [ 8.422223] kdump-tools[513]: readmem: Can't convert a virtual address(6a2) to physical address. [ 8.424872] kdump-tools[513]: readmem: type_addr: 0, addr:6a2, size:1032 [ 8.428291] kdump-tools[513]: validate_mem_section: Can't read mem_section array. [ 8.429779] kdump-tools[513]: get_mem_section: Could not validate mem_section. [ 8.432257] kdump-tools[513]: get_mm_sparsemem: Can't get the address of mem_section. [ 8.436297] kdump-tools[513]: makedumpfile Failed. [ 8.439351] kdump-tools[513]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 8.442197] kdump-tools[513]: * kdump-tools: failed to save dmesg content in /var/crash/202006171242 [ 8.448570] kdump-tools[513]: Wed, 17 Jun 2020 12:42:16 +0000 [ 8.455630] kdump-tools[513]: Rebooting. [ 8.514560] reboot: Restarting system bionic-proposed: success. $ dpkg -s makedumpfile | grep -i version Version: 1:1.6.5-1ubuntu1~18.04.5 [ 7.628682] kdump-tools[517]: Starting kdump-tools: * running makedumpfile -c -d 31 /home/ubuntu/201909170743/vmcore.201909170743 /var/crash/202006171249/dump-incomplete [ 7.642186] kdump-tools[517]: mv: cannot stat '/var/crash/202006171249/dump-incomplete': No such file or directory [ 7.644850] kdump-tools[517]: * kdump-tools: saved vmcore in /var/crash/202006171249 [ 7.662102] kdump-tools[517]: * running makedumpfile --dump-dmesg /home/ubuntu/201909170743/vmcore.201909170743 /var/crash/202006171249/dmesg.202006171249 [ 7.695277] kdump-tools[517]: The dmesg log is saved to /var/crash/202006171249/dmesg.202006171249. [ 7.697111] kdump-tools[517]: makedumpfile Completed. [ 7.699346] kdump-tools[517]: * kdump-tools: saved dmesg content in /var/crash/202006171249 [ 7.711560] kdump-tools[517]: Wed, 17 Jun 2020 12:49:41 +0000 [ 7.720149] kdump-tools[517]: Rebooting. [ 7.776421] reboot: Restarting system -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(ffff9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:ffff9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
