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

Issue 829015 link

Starred by 4 users
Status: WontFix
Owner: ----
Closed: Aug 29
Cc:
matthewjoseph@chromium.org
sdantul...@chromium.org
mkarkada@chromium.org
dchan@chromium.org
ahass...@chromium.org
dhadd...@chromium.org
█ vbendeb@chromium.org
█ tgillella@chromium.org
adurbin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

[Sand] Unable to turn ON device after AU from M66 to M65

Project Member Reported by abod...@chromium.org, Apr 4 2018 
AU from  M66(10452.42.0) beta to M65(10323.67.0) Stable

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Perform AU from  M66(10452.42.0) beta to M65(10323.67.0) Stable
(2) Reboot after successful update.
(3)

Expected Result:
Should reboot the device.

Actual Result:
After reboot failed to turn On device.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always.
What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

Comment 1 by matthewjoseph@chromium.org, Apr 4 2018

Cc: matthewjoseph@chromium.org

Comment 2 by abod...@chromium.org, Apr 4 2018

Cc: tgillella@chromium.org

Comment 3 by abod...@chromium.org, Apr 4 2018

Cc: dchan@chromium.org
M65 FW : Google_Sand.9042.140.0
M66 FW : Google_Sand.9042.178.0

Comment 4 by bhthompson@google.com, Apr 4 2018

Cc: vbendeb@chromium.org
I don't see any Sand specific changes, any chance this is related to https://chromium-review.googlesource.com/#/c/chromiumos/overlays/chromiumos-overlay/+/979294/ ?

https://crosland.corp.google.com/log/10323.62.0..10323.67.0

Comment 5 by abod...@chromium.org, Apr 4 2018 

No issue AU from M65-10323.62.0 to M65-10323.67.0 but if you AU M66(beta) to M65(stable) then will see this issue.

Comment 6 by vbendeb@chromium.org, Apr 4 2018 

The patch in #4 is not at all likely to be at fault, what it was causing was failure to update Cr50 during post-install.

When looking at #1: what does "After reboot failed to turn On device" - did the device fall into recovery or did it show no signs of life at all, black screen and all?

How do you recover the device after this failure to see if the problem is reproducible?

Comment 7 by abod...@chromium.org, Apr 4 2018 

Power LED is ON but No display after reboot.

Comment 8 by vbendeb@chromium.org, Apr 4 2018 

how do you recover from this state?

Comment 9 by tgillella@google.com, Apr 4 2018 

To recover the device we need to flash firmware(bios) with servo.

Comment 10 by vbendeb@chromium.org, Apr 4 2018 

can I get a device in that failed state to investigate?

Comment 11 by bhthompson@google.com, Apr 21 2018 

Is this still reproducible?

Comment 12 by bhthompson@google.com, Aug 29

Status: WontFix (was: Untriaged)
►

Sign in to add a comment