New issue
Advanced search Search tips

Issue 675045 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

ToT samus coreboot fails to talk to TPM

Project Member Reported by rspangler@chromium.org, Dec 16 2016

Issue description

TPM: Startup
src/drivers/pc80/tpm/tpm.c:514 unexpected TPM status 0xff
src/drivers/pc80/tpm/tpm.c:702 failed sending data to TPM
TPM: command 0x99 send/receive failed: 0x10000001
setup_tpm():442: Antirollback: 10000001 returned by tlcl_startup()
Phase 1
VB2:vb2_fail() Need recovery, reason: 0x2b / 0x2
FMAP: area GBB found @ 611000 (454656 bytes)
VB2:vb2_check_recovery() Recovery reason from previous boot: 0x2b / 0x2
VB2:vb2_check_recovery() We have a recovery request: 0x2b / 0x0
Clearing TPM owner
tpm_clear_and_reenable():224: TPM: Clear and re-enable
TPM: Force clear
src/drivers/pc80/tpm/tpm.c:514 unexpected TPM status 0xff
src/drivers/pc80/tpm/tpm.c:702 failed sending data to TPM
TPM: command 0x5d send/receive failed: 0x10000001
tpm_clear_and_reenable():225: Antirollback: 10000001 returned by tlcl_force_clear()
Recovery requested (1009000e)
Saving nvdata
src/drivers/pc80/tpm/tpm.c:514 unexpected TPM status 0xff
src/drivers/pc80/tpm/tpm.c:702 failed sending data to TPM
TPM: command 0x14 send/receive failed: 0x10000001

The samus firmware branch appears to work fine.  As did ToT, up until sometime in the last month or so.

 

Sign in to add a comment