Sabin does not boot up and is stuck on chromeos screen. |
|||
Issue descriptionChrome OS Version: <From about:version: Platform 9111.0.0> Chrome OS Platform: <Sabin/Kefka> Network info: <WiFi> Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1) Install test image (Kefka) Note: Sabin uses kefka image. Expected Result: Device should boot up as expected and show OOBE screen. Actual Result: Sabin does not boot up and is stuck on chromeos screen. 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? Device cannot be used for testing. Note: VT2 terminal is accessible. Please provide any additional information below. Attach a screen shot or log if possible. Logs Attached.
,
Jan 10 2017
Who is the right owner for this?
,
Jan 10 2017
Can you attach/link the logs? Does "stuck on chromeos screen" mean chrome splash screen is present? Can you take a photo/video? Is first boot successful, if recovery build is installed?
,
Jan 10 2017
Not able to reproduce this issue on 9169.0.0 Recovery build.
,
Jan 11 2017
+aashutoshk, need logs to determine who should own this.
,
Jan 11 2017
Looks like the issue is only for test image. Also, cannot toggle between VT2 and normal screen.
CHROMEOS_RELEASE_APPID={2EDF7C6D-6586-D292-0B61-4A33B62E3BF6}
CHROMEOS_BOARD_APPID={2EDF7C6D-6586-D292-0B61-4A33B62E3BF6}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
DEVICETYPE=CHROMEBOOK
CHROMEOS_ARC_VERSION=3594654
CHROMEOS_RELEASE_BUILDER_PATH=kefka-release/R57-9111.0.0
GOOGLE_RELEASE=9111.0.0
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_BOARD=kefka
CHROMEOS_RELEASE_BUILD_NUMBER=9111
CHROMEOS_RELEASE_BRANCH_NUMBER=0
CHROMEOS_RELEASE_CHROME_MILESTONE=57
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=testimage-channel
CHROMEOS_RELEASE_DESCRIPTION=9111.0.0 (Official Build) dev-channel kefka test
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_VERSION=9111.0.0
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
I will check if this issue persist on ToT.
|
|||
►
Sign in to add a comment |
|||
Comment 1 by aashuto...@chromium.org
, Jan 10 2017