------- Comment From boris.m...@de.ibm.com 2023-05-03 11:10 EDT------- After further investigation, it looks like a backport of the fix to Ubuntu 22.04 would be too big in terms of size and effort (touching up to 59 files with around 4000 insertions/deletions). The only "easy" option would be a version bump to s390-tools v2.22 which is not possible for SRUs.
Therefore, we are closing this bug as "will not fix" ==> Changing the status to CLOSED -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016920 Title: [UBUNTU 22.04] Standalone dump does not work on NVMe device Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in linux source package in Jammy: New Status in s390-tools source package in Jammy: New Status in linux source package in Kinetic: New Status in s390-tools source package in Kinetic: New Status in linux source package in Lunar: New Status in s390-tools source package in Lunar: New Bug description: Problem Description: -------------------- I installed Ubuntu 22.04.1. and created a dump partition on an NVMe disk. However, this dump partition is not able to capture a dump: [414340.280553] kdump-tools[15167]: * unloaded kdump kernel [414376.146205] sysrq: Trigger a crash [414376.146215] Kernel panic - not syncing: sysrq triggered crash [414376.146218] CPU: 13 PID: 16009 Comm: bash Not tainted 5.15.0-69-generic #76-Ubuntu [414376.146222] Hardware name: IBM 3931 A01 704 (LPAR) [414376.146224] Call Trace: [414376.146225] [<0000000176c3e31a>] dump_stack_lvl+0x62/0x80 [414376.146233] [<0000000176c3913a>] panic+0x152/0x340 [414376.146237] [<00000001768d5cfe>] sysrq_handle_crash+0x2e/0x30 [414376.146242] [<00000001768d6952>] __handle_sysrq+0xf2/0x280 [414376.146245] [<00000001768d7244>] write_sysrq_trigger+0x54/0x70 [414376.146248] [<0000000176597faa>] proc_reg_write+0x9a/0xf0 [414376.146252] [<00000001764e64dc>] vfs_write+0xbc/0x280 [414376.146255] [<00000001764e8a18>] ksys_write+0x68/0x100 [414376.146258] [<0000000176c4288c>] __do_syscall+0x1bc/0x1f0 [414376.146261] [<0000000176c4fc98>] system_call+0x78/0xa0 System version 9. Watchdog enabled. Running 'ZBootLoader' version '3.1.5' level 'D51C.D51C_328.13'. OK00000000 Success [ 2.131284] zdump: The dump process started for a 64-bit operating system Linux System Dumper starting Version 3.0 (64 bit) Linux version 5.15.27 (buildd@bos02-s390x-003) (gcc (Ubuntu 11.2.0-18ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Mon Mar 21 16:33:41 UTC 2022 ERROR: open /sys/firmware/ipl/device failed No such file or directory ERROR: Could not enable dump device Dump failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2016920/+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
