This bug was fixed in the package linux - 5.8.0-36.40+21.04.1
---
linux (5.8.0-36.40+21.04.1) hirsute; urgency=medium
* Packaging resync (LP: #1786013)
- update dkms package versions
[ Ubuntu: 5.8.0-36.40 ]
* debian/scripts/file-downloader does not handle positive
This bug was fixed in the package linux - 4.15.0-126.129
---
linux (4.15.0-126.129) bionic; urgency=medium
* bionic/linux: 4.15.0-126.129 -proposed tracker (LP: #1905305)
* CVE-2020-4788
- SAUCE: powerpc/64s: Define MASKABLE_RELON_EXCEPTION_PSERIES_OOL
- SAUCE:
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 4.4.0-197.229
---
linux (4.4.0-197.229) xenial; urgency=medium
* xenial/linux: 4.4.0-197.229 -proposed tracker (LP: #1905489)
* sha1_ce and sha2_ce modules no longer load on arm64 (LP: #1905336)
- SAUCE: Revert "crypto: arm64/sha -
This bug was fixed in the package linux - 5.4.0-56.62
---
linux (5.4.0-56.62) focal; urgency=medium
* focal/linux: 5.4.0-56.62 -proposed tracker (LP: #1905300)
* CVE-2020-4788
- selftests/powerpc: rfi_flush: disable entry flush if present
- powerpc/64s: flush L1D on
= xenial verification -
ubuntu@ubuntu:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.4.0-195-generic
root=UUID=6f35ed47-31af-4f66-b33f-5863971f8df0 ro console=tty1 console=ttyS0
ubuntu@ubuntu:~$ ls /sys/firmware/efi/efivars/ | grep FOO
FOO!BAR-8ed72b3f-ad26-4d5c-aa36-38689635cac3
** Tags
= bionic verification =
ubuntu@ubuntu:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.15.0-125-generic
root=UUID=9e45081a-7e2b-4294-8b2f-4ccb8139ed67 ro console=tty1 console=ttyS0
ubuntu@ubuntu:~$ ls /sys/firmware/efi/efivars/ | grep FOO
FOO!BAR-8ed72b3f-ad26-4d5c-aa36-38689635cac3
** Tags
= groovy verification =
ubuntu@ubuntu:~$ cat /proc/version
Linux version 5.8.0-30-generic (buildd@lgw01-amd64-009) (gcc (Ubuntu
10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #32-Ubuntu
SMP Mon Nov 9 21:03:15 UTC 2020
ubuntu@ubuntu:~$ ls /sys/firmware/efi/efivars | grep FOO
= focal verification =
ubuntu@ubuntu:~$ cat /proc/version
Linux version 5.4.0-55-generic (buildd@lcy01-amd64-013) (gcc version 9.3.0
(Ubuntu 9.3.0-17ubuntu1~20.04)) #61-Ubuntu SMP Mon Nov 9 20:49:56 UTC 2020
ubuntu@ubuntu:~$ ls /sys/firmware/efi/efivars/ | grep FOO
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
** Description changed:
[Impact]
MAAS installs fail on systems that have EFI Variables that include a "/" in
the name.
Split out of bug 1894217.
[Test Case]
$ ls /sys/firmware/efi/efivars | grep ^Boot
ls: reading directory '/sys/firmware/efi/efivars': Input/output error
Boot
** Description changed:
+ [Impact]
+ MAAS installs fail on systems that have EFI Variables that include a "/" in
the name.
+
Split out of bug 1894217.
- We're seeing a situation where curtin fails when the variable
- BootCurrent references does not exist.
+ [Test Case]
+ $ ls
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Groovy)
Status:
** Changed in: linux (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
**
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Xenial)
Status: New => In
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Patch backport to stable:
https://www.spinics.net/lists/stable/msg423555.html
** Changed in: curtin (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With the above patch applied, we can see the culprit directories:
$ sudo find /sys/firmware/efi/vars/ -type d | grep \!
/sys/firmware/efi/vars/Pwr!Perf Profiles-7683c190-9523-4402-81ff-a11e93dc389c
/sys/firmware/efi/vars/Intel(R) VT for Directed I!O
(VT-d)-7683c190-9523-4402-81ff-a11e93dc389c
Ah:
commit 336af6a4686d885a067ecea8c3c3dd129ba4fc75 (refs/bisect/bad)
Author: Michael Schaller
Date: Fri Sep 25 09:45:02 2020 +0200
efivarfs: Replace invalid slashes with exclamation marks in dentries.
Without this patch efivarfs_alloc_dentry creates dentries with slashes in
I tried to prove whether or not this is a firmware issue or, perhaps, a
bug in efibootmgr or curtin's calling of it. I deployed an affected
system w/ MAAS w/ init=/bin/bash on the cmdline, and was surprised to
see that efibootmgr showed the full expected set of Boot variables.
However, if I ssh'd
@nb This issue is *slightly* different than the other bug related to
missing BootCurrent value.
The previous bug which is fixed in curtin happens when the BootCurrent
value is not present in the efibootmgr output.
This bug has a BootCurrent value, like 0003, however, the Entries
provided by
@Dann
For this firmware bug where we have missing entries; Have you ever
booted this up and had efibootmgr show all of the entries?
Looking at this output here:
BootCurrent: 0003
Timeout: 10 seconds
@dann @ryan
FYI - I refreshed to Snap 2.9.0~beta6-9039-g.5a2ba747e and it looks like
my boot order woes are fixed now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
EFI: Fails when
@dann @ryan
RE: I'm also assuming a firmware bug here, but I need to consult the
specification. If it is a clear firmware bug then I think plan A should
certainly be to pressure the vendor to release a fix.
Is there a way we can verify that the firmware is the true issue? I have
Dell R420's
@Dann
OK. That sounds reasonable. For this issue, curtin can (and I think it
makes sense) ignore a BootCurrent value if there is no corresponding
entry; warn in the logs that it's missing, check your firmware, etc...
and proceed if it can.
** Changed in: curtin (Ubuntu)
Importance:
I'm also assuming a firmware bug here, but I need to consult the
specification. If it is a clear firmware bug then I think plan A should
certainly be to pressure the vendor to release a fix.
Either way, I think we're likely to run into users suffering from this
issue for a while. I tend to see
Looking back at your patch:
Index: curtin-20.1-29-g81144052/curtin/util.py
===
--- curtin-20.1-29-g81144052.orig/curtin/util.py
+++ curtin-20.1-29-g81144052/curtin/util.py
@@ -886,6 +886,7 @@ def get_efibootmgr(target=None):
"""
30 matches
Mail list logo
