Public bug reported:
I'm seeing an issue on an isolated host, howzit, in which it fails to
remove boot entries. In my limited testing this worked with the
6.2.0-20.20 kernel, but not the 21.21 or 23.23 kernel. I have not yet
tried any of the 6.3 kernels.
I've only seen this on one host so far, howzit, which is an arm64
server. I have tested on three other arm64 servers and they don't appear
to be impacted, so this could be some firmware issue. It adversely
impacts maas installs and will cause a mantic install (which is using
6.2.0-21.21) to fail because it can't modify the boot paths.
Here's what I see trying to remove a boot entry:
ubuntu@howzit-kernel:~$ efibootmgr -v
BootCurrent: 0005
Timeout: 5 seconds
BootOrder: 0005,0007,0004,0006
Boot0004 UEFI: Built-in EFI Shell
VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0005* UEFI: PXE IPv4 Mellanox Network Adapter - 0C:42:A1:52:3D:4C
PcieRoot(0x30000)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(0c42a1523d4c,1)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0006 UEFI: PXE IPv4 Mellanox Network Adapter - 0C:42:A1:52:3D:4D
PcieRoot(0x30000)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(0c42a1523d4d,1)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0007* ubuntu
HD(1,GPT,6d8df92f-72ad-4c24-bc8d-8236a4c5e222,0x800,0x100000)/File(\EFI\UBUNTU\GRUBAA64.EFI)..BO
ubuntu@howzit-kernel:~$ sudo efibootmgr -B -b 0007
Could not delete variable: Invalid argument
The same command will work with the 6.2.0-20.20 kernel.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: lunar
** Tags added: lunar
--
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/2023611
Title:
Unable to remove efi variable with 6.2.0-21.21 or newer lunar kernel
Status in linux package in Ubuntu:
New
Bug description:
I'm seeing an issue on an isolated host, howzit, in which it fails to
remove boot entries. In my limited testing this worked with the
6.2.0-20.20 kernel, but not the 21.21 or 23.23 kernel. I have not yet
tried any of the 6.3 kernels.
I've only seen this on one host so far, howzit, which is an arm64
server. I have tested on three other arm64 servers and they don't
appear to be impacted, so this could be some firmware issue. It
adversely impacts maas installs and will cause a mantic install (which
is using 6.2.0-21.21) to fail because it can't modify the boot paths.
Here's what I see trying to remove a boot entry:
ubuntu@howzit-kernel:~$ efibootmgr -v
BootCurrent: 0005
Timeout: 5 seconds
BootOrder: 0005,0007,0004,0006
Boot0004 UEFI: Built-in EFI Shell
VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0005* UEFI: PXE IPv4 Mellanox Network Adapter - 0C:42:A1:52:3D:4C
PcieRoot(0x30000)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(0c42a1523d4c,1)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0006 UEFI: PXE IPv4 Mellanox Network Adapter - 0C:42:A1:52:3D:4D
PcieRoot(0x30000)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(0c42a1523d4d,1)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0007* ubuntu
HD(1,GPT,6d8df92f-72ad-4c24-bc8d-8236a4c5e222,0x800,0x100000)/File(\EFI\UBUNTU\GRUBAA64.EFI)..BO
ubuntu@howzit-kernel:~$ sudo efibootmgr -B -b 0007
Could not delete variable: Invalid argument
The same command will work with the 6.2.0-20.20 kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023611/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
