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

Issue 689675 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 689792



Sign in to add a comment

[Gnawty/Swanky] unable to recover

Project Member Reported by ka...@chromium.org, Feb 7 2017

Issue description

Build 9000.82.0 / 56.0.2924.87

Recovering the Gnawty device, an error is issued and after communicating to  FW testing team, it seems Gnawty misses the FW version it is supposed to be with.


 

Comment 1 by ka...@chromium.org, Feb 7 2017

Cc: helenzhang@chromium.org rjahagir@chromium.org gkihumba@chromium.org pgangishetty@chromium.org dchan@chromium.org vsu...@chromium.org sontis@chromium.org twreid@chromium.org
Components: Test OS>Firmware

Comment 3 by dchan@google.com, Feb 7 2017

Cc: vwang@chromium.org
This is due to older firmware were installed on device with new RAM.

The gnawty with new RAM must have 9000.83.0 with Google_Gnawty.5216.239.109 firmware.  

We will no go 9000.82.0 FSI on gnawty and retry next week with > 9000.83.0
Just talked with Vincent. He'll wait for next stable au for FSI, with fw changes.
Labels: -ReleaseBlock-Stable
Labels: -ReleaseBlock-FSI ReleaseBlock-Stable
Components: -Test Internals>Installer
Labels: Proj-swanky Proj-gnawty
Summary: [Gnawty/Swanky] unable to recover (was: [FSI] Gnawty unable to recover)
Swanky got the same recovery error in 9202.25.0/57.0.2987.48. recovery log:

https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/689675/
Blocking: 689792

Comment 9 by ka...@chromium.org, Feb 16 2017

Status: Fixed (was: Untriaged)
Performed recovery install on Gnawty. Had to fix the device that failed last time by updating FW version from test image first. 

Doing same for Swanky now. Will verify once done.
Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-56; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-56 label, otherwise remove Merge-TBD label. Thanks.
Status: Verified (was: Fixed)
And recovery works on swanky after #9 action. 

Comment 12 by ka...@chromium.org, Feb 16 2017

To clarify - the fixed version is 9000.87.0 / 56.0.2924.101.

Project Member

Comment 13 by sheriffbot@chromium.org, Mar 31 2017

Labels: -Merge-TBD

Sign in to add a comment