New issue
Advanced search Search tips

Issue 880433 link

Starred by 1 user

Issue metadata

Status: Closed
Owner: ----
Closed: Nov 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Device powerwashed after successful AU

Project Member Reported by abod...@chromium.org, Sep 4

Issue description

CROS:10895.33.0/69.0.3497.58

What steps will reproduce the problem?
(1)Au to BetaM69-10895.33.0
(2)Reboot device after successful update
(3)

What is the expected result?

What happens instead?

Device powerwashed and went to OOBE screen. 


Please use labels and text to provide additional information.
Reproduced only once on caroline

If this is a regression (i.e., worked before), please consider using the
bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help
us identify the root cause and more rapidly triage the issue.

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

feedback report after reboot.
https://listnr.corp.google.com/product/208/report/85632665357

 
Cc: adlr@chromium.org ahass...@chromium.org
+AU folks 
Can we persistently reproduce this or it is just based on the given feedback? There might be many reasons the device gets powerwashed, like the stateful gets corrupted or something. I just did a cros flash to this specific version and it was fine. 
Not Always reproduced, repro only once.
Status: Closed (was: Untriaged)
Can't repro, please reopen if seen again.

Sign in to add a comment