Comment 5 for bug 1913639

Hi Anders, thanks for your testing. You can show all the initrd scripts debug output to console, for that you'd need to add the kernel parameter "debug=vc" for example. But I don't suggest to do that here, since you seem not able to capture the full console log in plain/text form. Pictures/snapshots might help to spot some issue, but they are very limited.

So, instead of dumping the output to console, I'll suggest you 2 more tests:

a) Add the following parameter to kernel command-line: "debug" . With that, boot normally, and collect/save the following file, in order to attach it here: "/run/initramfs/initramfs.debug" . This is the full output of initrd scripts executed. After that, try the kdump - you need to be sure it inherited this "debug" flag (check the kdump command-line in "kdump-config show" output to validate it's there). Kdump will fail, and you can try to SSH the file from the (initramfs) failure shell (or even dump it there using the "cat" command and grab some pictures, specially from the final portions of it). You may try to disconnect and reconnect the keyboard, or use another USB port to see if you can get that working in the failing (initramfs) shell.

b) Please execute the following 2 commands and submit the 2 resulting files here:

lsinitramfs /boot/initrd.img-$(uname -r) > regular_initrd.out
lsinitramfs /var/lib/kdump/initrd.img-$(uname -r) > kdump_initrd.out

Thanks in advance!