At this point, this is not a problem I can fix. It's very much tied to
their hardware, and to the kernel on that hardware. This is the only
instance of this I have ever seen, anywhere, over literally thousands of
test runs, and it is very easily reproduced manually by simply catting
the efi variable for SecureBoot, so it exists outside the test suite.
I've added a kernel task, if there's any fix to be had here, it would
have to occur there.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: plainbox-provider-checkbox
Status: New => Invalid
--
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:
Invalid
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
