New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 711298 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: 2019-07-09
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Fail to read VPD at boot in verified mode

Project Member Reported by igorcov@chromium.org, Apr 13 2017

Issue description

Chrome Version: 57.0.2984
OS: Chrome OS
Chell Chromebook

What steps will reproduce the problem?
(1) Enroll the device in verified mode
(2)
(3)

What is the expected result?
Success

What happens instead?
Failed to enroll

The enrollment succeeds when the device is in devmode. The reason is there's an error at reading the VPD in verified mode, and the problem is seen in the logs at boot - no need to enroll.

Attached are the logs for both cases: Device is enrolled having devmode enabled, and device is enrolled after verified boot. Also attached the contents of VPD, obtained with:
flashrom -r /tmp/bios.bin -i RO_VPD -i RW_VPD


Interesting places in the logs:
When the device boots in verified mode, the VPD read fails (ui/ui.LATEST):
[WARN] Cannot get eps_base from full BIOS.
[ERROR] getVpdPartitionFromFullBios() failed.loadFile('/tmp/vpd.flashrom.GoHPc1') error.
[WARN] flashromPartialRead() failed, try full read.
[4791:4791:0411/160651.428313:ERROR:app_list_syncable_service.cc(666)] UpdateItem: no sync item: ddb1da55-d478-4243-8642-56d3041f0263
[WARN] Cannot get eps_base from full BIOS.
[ERROR] getVpdPartitionFromFullBios() failed.loadFile('/tmp/vpd.flashrom.tr2Brx') error.

When it boots with devmode enabled, VPD is read successfully:
flashrom v0.9.4  : 0ef11b2 : Jan 17 2017 07:16:38 UTC on Linux 3.18.0-13726-gbe5e2df (x86_64)
flashrom v0.9.4  : 0ef11b2 : Jan 17 2017 07:16:38 UTC on Linux 3.18.0-13726-gbe5e2df (x86_64)
WARNING: SPI Configuration Lockdown activated.
Reading flash... SUCCESS
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.143215 s, 0.0 kB/s
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00670322 s, 0.0 kB/s
0+0 records in
0+0 records out

Also in debug_vboot_noisy.log when boot in verified mode:
WP: status: 0x00
WP: status.srp0: 0
WP: write protect is disabled.
WP: write protect range: spi_send_command called, but SPI is unsupported on this hardware. Please report a bug at flashrom@flashrom.org
RDSR2 failed!
 
debug-logs_20170413-152109.tgz
106 KB Download
debug-logs_20170411-160710.tgz
57.0 KB Download
bios.bin
16.0 MB Download
Labels: Pri-3
NextAction: 2019-07-09
Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.

Sign in to add a comment