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

Issue 633787 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Add recovery_subcode to eventlog (if non-zero)?

Project Member Reported by jwer...@chromium.org, Aug 2 2016

Issue description

vboot's recovery reason has a "subcode" stored next to it in NVRAM that is occasionally useful to narrow the problem down further. It's mostly used (and would be very helpful) with TPM problems like the one from http://crosbug.com/p/55764.

We store the recovery reason in the eventlog, but not the subcode. Maybe we should do both (it would just be 11 bytes instead of 10, so who cares). We could even check if the subcode is non-zero and only store it in that case, since eventlog events can be variable in length (at least when looking at the format alone... not sure if mosys would be equipped to handle that).
 
Owner: reinauer@chromium.org
Status: Untriaged (was: Available)
+Stefan for triage.

Comment 2 by gkihumba@google.com, Mar 31 2017

Status: Assigned (was: Untriaged)

Sign in to add a comment