Mantic and Jammy built successfully in all supported architectures. (riscv64 fails, but it also fails on mantic/jammy-release; it's OK.)
Uploaded! Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/2038249 Title: The dump file parsing issue arises from structural changes in Linux kernel 6.2 Status in crash package in Ubuntu: Fix Released Status in crash source package in Jammy: In Progress Status in crash source package in Lunar: Won't Fix Status in crash source package in Mantic: In Progress Status in crash source package in Noble: Fix Released Bug description: [Impact] Linux kernel 6.2 includes patches with structural changes that may render the crash utility in Mantic (release kernel 6.5) and Jammy (HWE kernel 6.5) unable to parse the dump file. For example (there are more, in other areas): ========== d122019bf061 mm: Split slab into its own type 401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations 07f910f9b729 mm: Remove slab from struct page 0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array allocation 130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head ac3b43283923 module: replace module_layout with module_memory b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array ========== [Fix] It is advisable to adopt commits that address the structural changes: - 10 patches from crash 8.0.1 into Jammy - 02 patches from crash 8.0.2 into Jammy - 12 patches from crash 8.0.3 into Jammy/Mantic - 12 patches from crash 8.0.4 into Jammy/Mantic [Test Plan] On Jammy (LTS), which provides HWE (6.5) and release/GA (5.15) kernels, perform testing on both HWE (verify fixes) and GA (verify no regressions). There are detailed/per-commit test plans in the attachments: `crash_jammy_test_plan.txt.txt` and `crash_lunar_test_plan.txt`. A. Test the live mode (live-system form; without a dumpfile), and B. Test the dump mode (dumpfile form: sysrq-trigger/makedumpfile/crash): 1. Install the required packages and then proceed to reboot the machine. # sudo apt install crash linux-crashdump -y # reboot 2. To check the status of kdump, use the `kdump-config show` command. # kdump-config show DUMP_MODE: kdump USE_KDUMP: 1 KDUMP_COREDIR: /var/crash crashkernel addr: 0x64000000 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-6.2.0-33-generic current state: ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 3. To trigger a crash dump forcefully, execute the `echo c | sudo tee /proc/sysrq-trigger` command. 4. Download the kernel .ddeb file, which will be used for analyzing the dump file. # sudo -i # cd /var/crash # pull-lp-ddebs linux-image-unsigned-$(uname -r) # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r) 5. Utilize the "crash" utility to parse and analyze the dump file. crash 8.0.0 Copyright (C) 2002-2021 Red Hat, Inc. Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation Copyright (C) 1999-2006 Hewlett-Packard Co Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited Copyright (C) 2006, 2007 VA Linux Systems Japan K.K. Copyright (C) 2005, 2011, 2020-2021 NEC Corporation Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc. Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc. Copyright (C) 2015, 2021 VMware, Inc. This program is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Enter "help copying" to see the conditions. This program has absolutely no warranty. Enter "help warranty" for details. WARNING: VA_BITS: calculated: 46 vmcoreinfo: 48 GNU gdb (GDB) 10.2 Copyright (C) 2021 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "aarch64-unknown-linux-gnu". Type "show configuration" for configuration details. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... crash: seek error: kernel virtual address: ffffd59a92d48ae8 type: "possible" WARNING: cannot read cpu_possible_map crash: seek error: kernel virtual address: ffffd59a92d48b68 type: "present" WARNING: cannot read cpu_present_map crash: seek error: kernel virtual address: ffffd59a92d48aa8 type: "online" WARNING: cannot read cpu_online_map crash: seek error: kernel virtual address: ffffd59a92d48bb0 type: "active" WARNING: cannot read cpu_active_map crash: seek error: kernel virtual address: ffffd59a93288928 type: "shadow_timekeeper xtime_sec" crash: seek error: kernel virtual address: ffffd59a9317b8f0 type: "init_uts_ns" crash: dbgsym-6 and 202309251539/dump.202309251539 do not match! Usage: crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form) crash [OPTION]... [NAMELIST] (live system form) Enter "crash -h" for details. [Where problems could occur] Significant structural changes have occurred between Linux kernel versions 5.15 and 6.2. We are only incorporating patches to ensure the functionality of the "crash" command. However, please be aware that these patches will alter the parsing logic and could potentially result in the "crash" utility being unable to parse the dump file in the worst-case scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2038249/+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
