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

Issue 643072 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Recovery is unsuccessful with 55.0.2844.0/8760.0.0 via USB

Project Member Reported by sc00335...@techmahindra.com, Sep 1 2016

Issue description

Version: 55.0.2844.0
Platform: 8760.0.0 dev channel paine,falco
OS: Chrome

What steps will reproduce the problem?
1.Try to recover the build 55.0.2844.0/8760.0.0 via USB (Esc+reload+power)

Expected: Should be able to recover the build.

Actual: Unable to recover the build and error message "Unexpected error has occurred" is seen.

This is a regression issue as recovery is successful with 55.0.2842.0/8751.0.0 dev-channel Paine
 
Cc: songsuk@chromium.org tienchang@chromium.org
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on CrOS device (Paine) Version: 55.0.2844.0/8760.0.0 dev. 

Note: Able to install the same build on Jerry device.
Cc: pucchakayala@chromium.org
Issue is reproduced on Peppy 55.0.2844.0/8760.0.0 as well.
Issue is seen with Peppy,Paine,Falco,Wolf,Parrot of 55.0.2844.0/8760.0.0 and
Works fine in Peach_pit,Jerry,Daisy with same build number.
Cc: ka...@chromium.org
Repro'd on Peppy
recovery.log
102 KB View Download
AU to this build is fine 
Cc: bhthompson@chromium.org
Cc: sha...@chromium.org dhend...@chromium.org
+flashrom experts

Looks like it failed in the firmware update...
"
Starting firmware updater (/tmp/install-mount-point/usr/sbin/chromeos-firmwareupdate --mode=recovery)
Command: /tmp/install-mount-point/usr/sbin/chromeos-firmwareupdate --mode=recovery
Starting Google_Peppy firmware updater v4 (recovery)...
 - Updater package: [Google_Peppy.4389.93.0 / EC:peppy_v1.5.132-c77d95f]
 - Current system:  [RO:Google_Peppy.4389.78.0 , ACT:Google_Peppy.4389.78.0 / EC:peppy_v1.5.113-2d79820]
 - Write protection: Hardware: ON, Software: Main=ON EC=ON
mode_recovery: update main/RW:A,B,SHARED
 * invoke: flashrom -p host  -r _current/bios.bin
 * invoke: flashrom -p host --fast-verify -w bios.bin -i RW_SECTION_A
 Execution failed (1): flashrom -p host --fast-verify -w bios.bin -i RW_SECTION_A
 Messages:


FREG0: WARNING: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
FREG2: WARNING: Management Engine region (0x00001000-0x001fffff) is locked.
Please send a verbose log to flashrom@flashrom.org if this board is not listed on
http://flashrom.org/Supported_hardware#Supported_mainboards yet.
Writes have been disabled. You can enforce write support with the
ich_spi_force programmer option, but it will most likely harm your hardware!
If you force flashrom you will get no support if something breaks.
FAILED
flashrom v0.9.4  : ff55cf6 : Aug 31 2016 18:13:14 UTC on Linux 3.8.11 (x86_64)flashrom v0.9.4  : ff55cf6 : Aug 31 2016 18:13:14 UTC on Linux 3.8.11 (x86_64)Write/erase is not working yet on your programmer in its current configuration.
Aborting.
ERROR: Execution FAILED.
ERROR: Execution failed: ./updater4.sh (error code = 1)
"

Since peppy is rather old and unchanged, perhaps something changed recently in Flashrom?
Yes, there was a bad CL that went in as part of a larger effort to merge patches from upstream. The revert landed in 8770.0.0: https://chromium-review.googlesource.com/#/c/380935/

Should be fixed now.
Owner: dhend...@chromium.org
Status: Fixed (was: Untriaged)
Ok let us assume this is fixed, we just need to verify.

Comment 11 by son...@google.com, Sep 22 2016

Status: Verified (was: Fixed)
Verified on build 8826.0.0

Sign in to add a comment