Tim Wawrzynczak has uploaded this change for review.
mb/google/brya: Temporarily disable recovery MRC cache
There is a bug yet to be root-caused that, when a board is booted for
the first time with recovery MRC cache enabled, coreboot will fail to
lock the recovery MRC hash space in the TPM and will reboot, whereas it
should instead boot to recovery (which will create the space in the TPM)
and any subsequent boots will be fine. However, this first boot then
turns into a boot-loop until the user manually enters recovery mode.
Until this bug is fixed, disable the recovery MRC cache.
BUG=b:181678769
Change-Id: Ia2189066e9a089293edada6403c7defe60f3aa33
Signed-off-by: Tim Wawrzynczak <twawrzynczak@chromium.org>
---
M src/mainboard/google/brya/Kconfig
1 file changed, 0 insertions(+), 1 deletion(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/62/51262/1
diff --git a/src/mainboard/google/brya/Kconfig b/src/mainboard/google/brya/Kconfig
index b3006cb..e35559a 100644
--- a/src/mainboard/google/brya/Kconfig
+++ b/src/mainboard/google/brya/Kconfig
@@ -29,7 +29,6 @@
config CHROMEOS
select EC_GOOGLE_CHROMEEC_SWITCHES
select GBB_FLAG_DISABLE_EC_SOFTWARE_SYNC
- select HAS_RECOVERY_MRC_CACHE
select VBOOT_LID_SWITCH
config DEVICETREE
To view, visit change 51262. To unsubscribe, or for help writing mail filters, visit settings.