I can reproduce, and I've attached the full console log (!quiet, +debug). Here's some interesting pieces of the log:
EFI stub: Booting Linux Kernel... EFI stub: Generating empty DTB error: couldn't send network packet. EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Exiting boot services... [ 0.000000] Booting Linux on physical CPU 0x0000120000 [0x413fd0c1] [ 0.000000] Linux version 5.15.0-25-generic (buildd@bos02-arm64-058) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #25-Ubuntu SMP Wed Mar 30 15:57:31 UTC 2022 (Ubuntu 5.15.0-25.25-generic 5.15.30) [...] [ 15.338070] Trying to unpack rootfs image as initramfs... [ 15.439137] Initramfs unpacking failed: invalid magic at start of compressed archive [ 15.461425] Freeing initrd memory: 103244K [...] We can see at the end there that the initrd failed to unpack, and that will definitely lead to a "Unable to mount root fs" panic. But why did it fail to unpack? One possibility is that the initrd failed to download. The TFTP server does report that it downloaded: Apr 8 19:38:59 avoton02 in.tftpd[4218]: RRQ from 10.229.58.47 filename /casper/vmlinuz Apr 8 19:39:02 avoton02 in.tftpd[4220]: RRQ from 10.229.58.47 filename /casper/vmlinuz Apr 8 19:39:06 avoton02 in.tftpd[4221]: RRQ from 10.229.58.47 filename /casper/initrd OK, then maybe it only partially downloaded? Well, the amount of memory the kernel reports freeing is close to the size of the initrd, so that's probably not it: $ du -s /srv/tftp/casper/initrd 103248 /srv/tftp/casper/initrd Then perhaps the kernel doesn't support decompressing this compression format. What is the compression format? $ file /srv/tftp/casper/initrd /srv/tftp/casper/initrd: Zstandard compressed data (v0.8+), Dictionary ID: None Does the kernel support that? Let's look at the kernel config: ubuntu@avoton02:/tmp$ dpkg-deb -x linux-modules-5.15.0-25-generic_5.15.0-25.25_arm64.deb x ubuntu@avoton02:/tmp$ grep ZSTD_DECOMPRESS x/boot/config-5.15.0-25-generic CONFIG_ZSTD_DECOMPRESS=y hm.. it does. That's weird. The other mystery is that this all seems to work when booted from the ISO. Let's take a look at that boot log and see if we can spot anything different. ** Attachment added: "howzit-pxe-console.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+attachment/5578333/+files/howzit-pxe-console.log ** Changed in: subiquity (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
