On Tue, Nov 29, 2016 at 07:24:32AM -0000, Ivan Hu wrote:
> This issue is caused by the Dell machines have already embedded the
> MokSBStatesRT variable with EFI_VARIABLE_NON_VOLATILE attribute, and the
> new shim-signed 1.21.4 include the patch which will mirror the
> MokSBStatesRT when MokSBState exists, see the
> https://github.com/rhinstaller/shim/commit/8f1bd605d05077a76502de5510cc937c4f4c62dd,
> and it causes the setvariable MokSBStatesRT failed because it has
> already existed with different attribute.
Are the machines that have this variable pre-set in production, or are these
dev systems? Does this issue block the boot or does it "just" generate an
ugly error message? From your perspective, should this block release of
this SRU, which has been delayed several times and will require another
round trip to Microsoft for signing to get this new patch included?
The current version of shim is known to have failures correctly booting to
e.g. fwupdate.efi (bug #1581299). The pending SRU fixes this.
On Tue, Nov 29, 2016 at 07:24:32AM -0000, Ivan Hu wrote: NON_VOLATILE attribute, and the /github. com/rhinstaller /shim/commit/ 8f1bd605d05077a 76502de5510cc93 7c4f4c62dd,
> This issue is caused by the Dell machines have already embedded the
> MokSBStatesRT variable with EFI_VARIABLE_
> new shim-signed 1.21.4 include the patch which will mirror the
> MokSBStatesRT when MokSBState exists, see the
> https:/
> and it causes the setvariable MokSBStatesRT failed because it has
> already existed with different attribute.
Are the machines that have this variable pre-set in production, or are these
dev systems? Does this issue block the boot or does it "just" generate an
ugly error message? From your perspective, should this block release of
this SRU, which has been delayed several times and will require another
round trip to Microsoft for signing to get this new patch included?
The current version of shim is known to have failures correctly booting to
e.g. fwupdate.efi (bug #1581299). The pending SRU fixes this.