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

Issue 803666 link

Starred by 2 users
Status: Assigned
Owner:
█ rspangler@chromium.org
Last visit > 30 days ago
Cc:
adurbin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

vboot: Try the other RW slot if software sync fails

Project Member Reported by dnojiri@chromium.org, Jan 18 2018 
When AP in slot A fails to update EC, it should reboot to slot B to let it update EC. Currently, AP gives up and requests recovery.

Comment 1 by rspangler@chromium.org, Jan 19 2018

Status: Available (was: Untriaged)
More generally:

If we are trying a new AP-RW firmware, and that firmware fails, we should set tries=0 and reboot back to the previous firmware rather than requesting recovery.  This will be a better user experience when we push firmware updates.

We should make sure the failure reason is logged so that we can track *why* the new firmware fails.

Comment 2 by benhenry@chromium.org, Aug 1

Status: Assigned (was: Available)
►

Sign in to add a comment