[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
kern/56735: TPM in -current doesn't appear to manage the Security Device for successful boot
>Synopsis: TPM in -current doesn't appear to manage the Security Device for successful boot
>Arrival-Date: Tue Mar 01 16:25:00 +0000 2022
>Originator: Bob Nestor
>Release: -current, both 9.99.92 and 9.99.93
NetBSD 9.99.93 (GENERIC) #0: Sat Feb 26 15:04:39 UTC 2022
On some systems, the HP 6200 MT being one, when the BIOS is configured to allow the "OS to Manage the Embedded Security Device" (TPM), NetBSD -current will claim/configure the device while booting but then will fail to complete booting. The first indication will be that a boot volume can't be found followed by a kernel crash. Versions of NetBSD that don't configure the TPM, such as NetBSD 9.2, boot successfully regardless of the BIOS setting.
Booting 9.2 shows:
TPM (IFX0102) at acpi0 not configured
Booting 9.99.93 shows:
tpm0 at acpi0 (TPM, IFX0102-1): mem 0xfed40000-0xfed44fff
tpm0: device 0x000b15d1 rev 0x10
tpm0: read 8 bytes, expected 10tpm0: deactivating entropy source
tpm0: ahcisata0 port 1: device present, speed: 3.0Gb/s
tpm0: deactivating entropy source
Attempt to boot a -current kernel on a system like the HP 6200 with the BIOS set to allow the OS to Manage the Embedded Security Device.
As a temporary workaround, disable the BIOS option that allows the OS to Manage the Embedded Security Device.
Main Index |
Thread Index |