[Bug 2073634] Re: [SRU] Enable suppression of /EndEntire message
Vlad Gavrila
2073634 at bugs.launchpad.net
Thu Oct 31 04:52:45 UTC 2024
Alex, Lauren,
I build a new image with the updated gadget and the /EndEntire message
is not displayed anymore and I see the BIOS logo throughout OS boot.
But I believe the new automount (which is part of the image) is
interfering with the functionality of the gadget and not able to read
the instrument-uid.assert from the USB during boot (I suspect a race
condition)
Here's the log from the prepare-device hook:
+ mktemp -d
+ MOUNTDIR=/tmp/tmp.4HfwMeYaZI
+ readonly MOUNTDIR
+ test -L /dev/disk/by-id/usb-hp_v165w_070D6C734C572C06-0:0-part1
+ continue
+ test -L /dev/disk/by-id/usb-hp_v165w_070D6C734C572C06-0:0-part1-part1
+ readlink -f /dev/disk/by-id/usb-hp_v165w_070D6C734C572C06-0:0-part1
+ mount -o ro -t vfat /dev/sda1 /tmp/tmp.4HfwMeYaZI
mount: /tmp/tmp.4HfwMeYaZI: /dev/sda1 already mounted on /var/lib/snapd/hostfs/media/root/FAT32.
+ continue
+ /snap/elembio-instrument-gadget/88/bin/uid-extractor -f /tmp/tmp.4HfwMeYaZI/instrument-uid.assert
Error: open /tmp/tmp.4HfwMeYaZI/instrument-uid.assert: no such file or directory
Usage:
uid-extractor [flags]
Flags:
-f, --file string Path to encrypted UID assertion file
-h, --help help for uid-extractor
uid-extractor: open /tmp/tmp.4HfwMeYaZI/instrument-uid.assert: no such file or directory
+ product_serial=
------------------------------------------------------------------------------------------
svc at ubuntu:~$ snap model
brand Element Biosciences (elembio)
model instrument
grade secured
serial - (device not registered yet)
svc at ubuntu:~$ ls /media/root/FAT32/
00000240a1e74b018521 FITSI.csv auto-import.assert instrument-uid.assert svc_concerned-study-5857_auto-import.assert test_instrument-uid
svc at ubuntu:~$ snap logs elembio-automount
2024-10-31T04:13:56Z elembio-automount.daemon[15391]: -> Found device: /dev/disk/by-uuid/32D6-1103
2024-10-31T04:13:56Z elembio-automount.daemon[15391]: -> Successfully mounted device '/dev/disk/by-uuid/32D6-1103' to '/media/root/FAT32'
2024-10-31T04:15:34Z systemd[1]: Stopping Service for snap application elembio-automount.daemon...
2024-10-31T04:15:34Z systemd[1]: snap.elembio-automount.daemon.service: Succeeded.
2024-10-31T04:15:34Z systemd[1]: Stopped Service for snap application elembio-automount.daemon.
2024-10-31T04:16:12Z systemd[1]: Started Service for snap application elembio-automount.daemon.
2024-10-31T04:16:13Z elembio-automount.daemon[1908]: -> Found device: /dev/disk/by-id/usb-hp_v165w_070D6C734C572C06-0:0-part1
2024-10-31T04:16:13Z elembio-automount.daemon[1908]: -> Successfully mounted device '/dev/disk/by-id/usb-hp_v165w_070D6C734C572C06-0:0-part1' to '/media/root/FAT32'
2024-10-31T04:16:13Z elembio-automount.daemon[1934]: -> Found device: /dev/disk/by-id/usb-hp_v165w_070D6C734C572C06-0:0
2024-10-31T04:16:13Z elembio-automount.daemon[1934]: #> Skipping unsupported filesystem type: /dev/disk/by-id/usb-hp_v165w_070D6C734C572C06-0:0: None
svc at ubuntu:~$ snap changes
ID Status Spawn Ready Summary
1 Done today at 04:12 UTC today at 04:13 UTC Initialize system state
2 Done today at 04:13 UTC today at 04:13 UTC Running service command for snap "ubuntu-frame"
3 Done today at 04:13 UTC today at 04:13 UTC Running service command for snap "ubuntu-frame"
4 Error today at 04:13 UTC today at 04:13 UTC Initialize device
5 Error today at 04:16 UTC today at 04:16 UTC Initialize device
svc at ubuntu:~$ snap change 4
Status Spawn Ready Summary
Error today at 04:13 UTC today at 04:13 UTC Run prepare-device hook
Hold today at 04:13 UTC today at 04:13 UTC Generate device key
Hold today at 04:13 UTC today at 04:13 UTC Request device serial
......................................................................
Run prepare-device hook
2024-10-31T04:13:29Z ERROR run hook "prepare-device": exit status 1
svc at ubuntu:~$ snap list
Name Version Rev Tracking Publisher Notes
bare 1.0 5 latest/stable canonical✓ base
core20 20240911 2434 latest/stable canonical✓ base
elembio-automount 1.0 6 latest/stable elembio -
elembio-instrument-gadget 2.0.12 88 latest/edge elembio gadget
elembio-tools 0.5 5 latest/candidate elembio -
elembio-updater a8b66f3+local 102 latest/candidate elembio -
gnome-3-38-2004 0+git.efb213a 143 latest/stable canonical✓ -
gtk-common-themes 0.1-81-g442e511 1535 latest/stable canonical✓ -
iot-kernel 5.4.0-1043.44.1 69 20/stable canonical✓ kernel
mesa-core20 21.2.6 165 latest/stable canonical✓ -
network-manager 1.22.10-27 904 20/stable canonical✓ -
snapd 2.63 21759 latest/stable canonical✓ snapd
ubuntu-frame 99-mir2.13.0 5787 latest/stable canonical✓ -
--
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/2073634
Title:
[SRU] Enable suppression of /EndEntire message
Status in OEM Priority Project:
New
Status in grub2 package in Ubuntu:
Fix Released
Status in grub2 source package in Focal:
Confirmed
Status in grub2 source package in Jammy:
Confirmed
Status in grub2 source package in Noble:
Fix Committed
Status in grub2 source package in Oracular:
Fix Released
Bug description:
[ Impact ]
* Many Ubuntu Core customers require a boot sequence that displays a
custom splash image up until ubuntu-frame loads. Unfortunately, GRUB
interrupts this process, printing two "/EndEntire" messages to the
display.
* Ideally, this should be able to be suppressed via configuration, at
least on devices running Ubuntu Core, as it likely desirable behavior
on Classic systems.
* The message only happens with Ubuntu Core, because Ubuntu Core is
using chainloader of GRUB to load the kernel EFI image.
[ Test Plan ]
* Boot a Ubuntu Core image on an AMD64 device with UEFI support
* During the boot process, check if the console shows "/EndEntire"
and "file path: /ACPI..."
* Test that the re-built GRUB doesn't cause any boot regressions either when
booting from disk or network.
[ Where problems could occur ]
* Removing or suppressing the messages is unlikely to cause any
regression.
* Rebuilding and updating the bootloader always has unforeseen regression
potential, but the appropriate testing should be performed to mitigate
this as much as possible.
[ Other Info ]
* None
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2073634/+subscriptions
More information about the foundations-bugs
mailing list