https://bugzilla.suse.com/show_bug.cgi?id=1228863 https://bugzilla.suse.com/show_bug.cgi?id=1228863#c4 Artur Kaufmann <arturkaufmann@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arturkaufmann@gmail.com --- Comment #4 from Artur Kaufmann <arturkaufmann@gmail.com> --- This is my output, after troubleshooting referred to clear TPM and then update-predictions [artur@gregory ~]$ sudo sdbootutil -v update-predictions Garbage after device path end, ignoring. Garbage after device path end, ignoring. /var/lib/pcrlock.d/250-firmware-code-early.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/550-firmware-code-late.pcrlock.d/generated.pcrlock written. Garbage after device path end, ignoring. Garbage after device path end, ignoring. /var/lib/pcrlock.d/250-firmware-config-early.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/550-firmware-config-late.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/600-gpt.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/630-shim-efi-application.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/640-boot-loader-efi-application.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/641-sdboot-loader-conf.pcrlock written. /var/lib/pcrlock.d/650-kernel-efi-application.pcrlock.d/linux-1.pcrlock written. /tmp/sdbootutil.xIRias/cmdline.pcrlock written. /var/lib/pcrlock.d/710-kernel-cmdline-boot-loader.pcrlock.d/cmdline-1.pcrlock written. /tmp/sdbootutil.xIRias/cmdline.pcrlock written. /var/lib/pcrlock.d/710-kernel-cmdline-boot-loader.pcrlock.d/cmdline-2.pcrlock written. /tmp/sdbootutil.xIRias/cmdline.pcrlock written. /var/lib/pcrlock.d/710-kernel-cmdline-boot-loader.pcrlock.d/cmdline-3.pcrlock written. Garbage after device path end, ignoring. Garbage after device path end, ignoring. Couldn't find component '350-action-efi-application' in event log. Couldn't find component '750-enter-initrd' in event log. Didn't find component '800-leave-initrd' in event log, assuming system hasn't reached it yet. Didn't find component '850-sysinit' in event log, assuming system hasn't reached it yet. Didn't find component '900-ready' in event log, assuming system hasn't reached it yet. Skipped 2 components after location '940-' (950-shutdown, 990-final). Unable to recognize 2 components in event log. Event log record 9 (PCR 6, "Raw: Dell Configuration Information 1") not matching any component. Event log record 30 (PCR 14, "Raw: MokList\000") not matching any component. PCR 0 (platform-code) matches event log and fully consists of recognized measurements. Including in set of PCRs. PCR 4 (boot-loader-code) is touched by component we can't find in event log. Removing from set of PCRs. PCR 5 (boot-loader-config) matches event log and fully consists of recognized measurements. Including in set of PCRs. PCR 7 (secure-boot-policy) matches event log and fully consists of recognized measurements. Including in set of PCRs. PCR 9 (kernel-initrd) matches event log and fully consists of recognized measurements. Including in set of PCRs. PCRs dropped from protection mask: 4 (boot-loader-code) PCRs in protection mask: 0 (platform-code), 5 (boot-loader-config), 7 (secure-boot-policy), 9 (kernel-initrd) Predicted future PCRs in 1.503ms. WARNING:esys:src/tss2-esys/api/Esys_StartAuthSession.c:391:Esys_StartAuthSession_Finish() Received TPM Error ERROR:esys:src/tss2-esys/api/Esys_StartAuthSession.c:136:Esys_StartAuthSession() Esys Finish ErrorCode (0x0000018b) Failed to allocate encryption session: State not recoverable Error creating the policy! Please, provide the recovery PIN to register the new policy NVIndex policy created -- You are receiving this mail because: You are on the CC list for the bug.