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

Issue 638181 link

Starred by 2 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: Blank OS recovery screen

Project Member Reported by sandeepk...@techmahindra.com, Aug 16 2016

Issue description

Version: 54.0.2826.0/8710.0.0 (Official Build) dev-channel Peppy, Daisy
OS: Chrome
What steps will reproduce the problem?
(1) Try to recover the OS via USB>> hit Ctrl+ reload + power button and observe

Expected: Recovery screen should be seen
Actual: 1. Instead blank page is seen and after some time the recovery is successful (As per regular installing process)
2. Able to work on the build as well

This is a Regression issue as able to see the recovery screen in 54.0.2826.0/8709.0.0 (Official Build) dev-channel Peppy, Daisy
 
Cc: songsuk@chromium.org krishna...@chromium.org
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on 54.0.2826.0/8710.0.0 dev-channel Peppy. Observed black screen flickering while recovering the OS.

Comment 2 by ajha@chromium.org, Aug 16 2016

This worked fine on 54.0.2826.0/8709.0.0_Dev_Peppy and Daisy.
Reproduce the issue on Chrome 54.0.2826.0/8711.0.0 - Daisy
Cc: ka...@chromium.org sontis@chromium.org

Comment 5 by shrawan@google.com, Aug 16 2016

Cc: shrawan@chromium.org
Able to reproduce on Peppy and Daisy. 


Tested with Build: 54.0.2826.0/8710.0.0
Observation:
1) Black screen started as soon as the recovery process started.
2) waited more than 30 minutes still nothing came back on screen. Screen was still Blank.
3) removed the USB stick and saw the dev screen. From this time onward blank screen was not seen. 
4) able to log-on and work properly. Checked the chrome version and installation was successful.





Attaching recovery logs for Peppy.
recovery.log
596 KB View Download

Comment 6 by ka...@chromium.org, Aug 16 2016

Cc: dchan@chromium.org
Components: OS>Firmware
Labels: ReleaseBlock-Stable
Summary: Regression: Blank OS recovery screen (was: Regression: Blank page is seen on OS recovery via USB)
Cc: sha...@chromium.org dhend...@chromium.org
Labels: -ReleaseBlock-Dev -ReleaseBlock-Stable ReleaseBlock-Beta
Owner: souvikghosh@google.com
Status: Assigned (was: Untriaged)
Seems related to https://chromium-review.googlesource.com/#/c/368480/

souvikghosh/dhendrix, can you evaluate?
Is there a possibility to get into this issue via AU?
Cc: dbehr@chromium.org
A quick look at the log shows many of these messages:
[    5.774827] DEBUG: tsm_vte: new vte object
[    5.823043] DEBUG: tsm_screen: new screen

That message comes from frecon, which also had a change land: https://chromium-review.googlesource.com/#/c/365563/

The part where flashrom is called seemed to succeed:
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.93.0 , ACT:Google_Peppy.4389.93.0 / EC:peppy_v1.5.132-c77d95f]
 - Write protection: Hardware: ON, Software: Main=off EC=off
mode_recovery: update RO+RW
 * invoke: flashrom -p host --fast-verify -w bios.bin
mode_recovery: update ec/RO+RW
 * invoke: flashrom -p ec --fast-verify -w ec.bin
mode_recovery: EC may be restored or updated in next boot.
Firmware update (recovery) completed.
Finished after 27 seconds.
Firmware update completed.
Rep#8
AU works fine. No issues seen after successful update on daisy. 

Cc: souvikghosh@google.com
Owner: ----
Status: Available (was: Assigned)
Issue is seen on installing 54.0.2830.0/8713.0.0 dev channel Parrot, Paine, Gnawty (Blank OS recovery screen is seen)
Owner: dbehr@chromium.org
Is this still happening?

Dominik, any comment/evaluation as per c#9?

Comment 14 Deleted

Comment 15 by ka...@chromium.org, Sep 12 2016

Now  issue 646039  is observed - messages missing from recovery screen.

Comment 16 by dchan@google.com, Sep 12 2016

can this be mark as fixed/verified ?

Comment 17 by ka...@chromium.org, Sep 12 2016

Status: Verified (was: Available)
Yes, this seems to be fixed.

Sign in to add a comment