[Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

[Heinrich Schuchardt]

As the log below shows grub_net_fini_hw() is called before entering the
kernel and before the LoadFile2 protocol is executed:

loader/efi/linux.c:478: kernel @ 0xf63d8000
net/net.c:1559: fs_close() name: /casper/vmlinuz
net/net.c:1510: fs_open() name: /casper/initrd
loader/efi/linux.c:396: LoadFile2 initrd loading protocol installed
net/net.c:1819: grub_net_fini_hw()
net/drivers/efi/efinet.c:232: efi_net close_card
loader/efi/linux.c:141: Installed/updated FDT configuration table @ 0x0
loader/efi/linux.c:191: linux command line: 'BOOT_IMAGE=/casper/vmlinuz
efi=debug earlyprintk
url=https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/jammy-live-serv
er-arm64.iso'
loader/efi/peimage.c:215: PE-COFF header checked
loader/efi/peimage.c:282: sections loaded
loader/efi/peimage.c:493: no relocations
loader/efi/peimage.c:709: Executing image loaded at 0xf3640000
Entry point 0xf55473c8
Size 0x02d90000
EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable
EFI stub: Generating empty DTB
loader/efi/linux.c:348: Providing initrd via LOAD_FILE2_PROTOCOL
net/net.c:1685: fs_read_real() name: /casper/initrd
net/drivers/efi/efinet.c:169: efi_net open_card
net/drivers/efi/efinet.c:75: Timeout: limit_time 50680, new_time 50681
error: couldn't send network packet.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1967562

Title:
  jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  Invalid

Bug description:
  = Description =
  Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht)
  Image: Jammy Beta (220330)

  I setup my pxe server to provision jammy beta and got the following
  kernel panic message after grub stage:

  log from console log

  [    1.176614] integrity: Couldn't parse dbx signatures: -74^M
  [    1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M
  [    1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M
  [    1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M
  [    1.400215] Call trace:^M
  [    1.402649]  dump_backtrace+0x0/0x1ec^M
  [    1.406310]  show_stack+0x24/0x30^M
  [    1.409614]  dump_stack_lvl+0x68/0x84^M
  [    1.413271]  dump_stack+0x18/0x34^M
  [    1.416573]  panic+0x18c/0x39c^M
  [    1.419616]  mount_block_root+0x160/0x210^M
  [    1.423622]  mount_root+0x12c/0x14c^M
  [    1.427097]  prepare_namespace+0x140/0x1a0^M
  [    1.431182]  kernel_init_freeable+0x1c8/0x214^M
  [    1.435527]  kernel_init+0x30/0x160^M
  [    1.439006]  ret_from_fork+0x10/0x20^M
  [    1.442573] SMP: stopping secondary CPUs^M
  [    1.447323] Kernel Offset: 0x55263ee90000 from 0xffff800008000000^M
  [    1.453404] PHYS_OFFSET: 0x80000000^M
  [    1.456879] CPU features: 0x000085c1,a3302e42^M
  [    1.461225] Memory Limit: none^M
  [    1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M

  = Steps to Reproduce =
  1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso
  1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso`
  2. Boot the system via PXE
  3. Select Ubuntu at Grub menu

  = Expected Result =
  The image is loaded to the system locally via PXE, and subiquity is launched

  = Actual Result =
  Console log simply shows nothing for 10 seconds and then the kernel panic shows up.

  = Additional Information =
  - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully.
  - MAAS could deploy Jammy to the Mt. Jade server as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions