after some more commentary from the customer, I'm still not convinced
that this isn't related to the hardware itself, HOWEVER, while doing a
bit more deubgging I noticed that the boot_mode_test.py script opens
files but does not properly close them (expecting python to close them
on exit?)
So while this may or may not resolve the hang that was reported when the
secureboot test runs, I can at least fix this a bit so that we properly
close the files after reading them.
** Changed in: plainbox-provider-checkbox
Status: Invalid => Incomplete
** Changed in: plainbox-provider-checkbox
Status: Incomplete => Fix Committed
** Changed in: plainbox-provider-checkbox
Status: Fix Committed => In Progress
** Changed in: plainbox-provider-checkbox
Importance: Undecided => Medium
** Changed in: plainbox-provider-checkbox
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: plainbox-provider-checkbox
Milestone: None => 0.57.0
--
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/1896119
Title:
Catting the SecureBoot efivar in /sys hangs
Status in Provider for Plainbox - Checkbox:
In Progress
Status in linux package in Ubuntu:
Incomplete
Bug description:
During testing, a machine locked up appearing to hang on the secure
boot mode test. Looking at the test logs, both of the things that use
boot_mode_test.py have triggered this issue:
miscellanea/reboot_firmware crashed
miscellanea/secure_boot_mode crashed
as this doesn't do much beyond open up a file in efivars, this is
puzzling behaviour. Need to figure out what would trigger this and
how to work around it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1896119/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
