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

Issue 682034 link

Starred by 3 users
Status: Duplicate
Merged: issue 682578
Owner:
█ mka@chromium.org
Last visit > 30 days ago
Closed: Feb 2017
Cc:
zalcorn@chromium.org
adlr@chromium.org
snanda@chromium.org
█ rookrishna@chromium.org
sdantul...@chromium.org
dhadd...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Seen Chrome logo animation screen more than a minute

Project Member Reported by abod...@chromium.org, Jan 17 2017 
Chrome Version: 57.0. 2984.0
Chrome OS Version: 9194.0.0
Chrome OS Platform: Lumpy
Network info: wifi

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

Steps To Reproduce:
(1)Perform Auto update to 9194.0.0
(2)Reboot the device after successful update 
(3)observe the boot animation time .

Expected Result:
Chrome logo animation screen time should be less than 2 or 3 seconds.

Actual Result:
Seen Chrome logo animation screen more than a minute.

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 zalcorn@chromium.org, Jan 19 2017

Owner: jkwang@chromium.org
jkwang@ could you PTAL?

Comment 2 by jkwang@google.com, Jan 19 2017 

Reproduced the bug on 9194.0.0 test. 
But the bug is gone on 9199.0.0 test.

I have attached the bootchart. Frecon/boot-animation part looks ok to me.
lumpy_9194.png
681 KB View Download
lumpy_9199.png
542 KB View Download

Comment 3 by abodenha@chromium.org, Jan 19 2017

Cc: zalcorn@chromium.org
Labels: ReleaseBlock-Beta
Status: Assigned (was: Untriaged)

Comment 4 by keta...@chromium.org, Jan 30 2017 

This hasn't been looked at for a week or more. Does this still repro in the latest Dev build?

Comment 5 by keta...@chromium.org, Feb 2 2017 

jkwang@ can you please confirm this is still reproing?

Comment 6 by adlr@chromium.org, Feb 2 2017 

I think in comment 2 jkwang said it's no longer reproducing. Shall we close?

Comment 7 by jkwang@google.com, Feb 2 2017 

Yup, the bug does not reproduce in 9199.0.0. I think we can close the bug for now.

Comment 8 by jkwang@google.com, Feb 2 2017

Status: WontFix (was: Assigned)

Comment 9 by rookrishna@chromium.org, Feb 10 2017

Labels: -M-57 M-58
Status: Assigned (was: WontFix)
Re-opening as this issue is seen  old devices like lumpy and alex

Tested on 58.0.3007.0/9270.0.

Comment 10 by jkwang@google.com, Feb 10 2017 

Here is what I have seen so far.
I was able to reproduce the bug on lumpy on R59-9270.0.0. But it's behaving weird.
Sometimes it takes normal time to boot and some time it takes more than 1 min.
If it takes more than 1 min, I can ssh to it when it hit login screen.
If it takes normal time, when it hits login screen, I have to wait a while to login.
The following build images are all from the same image. I did not re-image the machine, all I did was reboot and reboot.
lumpy_normal.png
657 KB View Download
log-lumpy-normal.tar.gz
810 KB Download
lumpy_slow.png
228 KB View Download
log-lumpy-slow.tar.gz
703 KB Download

Comment 11 by jkwang@google.com, Feb 13 2017 

More: if the boot takes normal time, after login with root, ifconfig also takes very long time.

And: I was able to get one bootchart of 100s. and the log is also attached
lump_slow_100s.png
1.8 MB View Download
log-021317-143207.tar.gz
1.1 MB Download

Comment 12 by adlr@chromium.org, Feb 13 2017

Components: -UI>Shell>OOBE OS>Kernel
Owner: snanda@chromium.org
Sameer, can you take a quick look at the attachments in Comment 11? There seems to be something broken at a low level here and I'm at a loss as to what. At this point it's pretty clearly not the bootanimation's fault.

Comment 13 by snanda@chromium.org, Feb 13 2017

Cc: snanda@chromium.org
Owner: mka@chromium.org
I am suspecting this is the udev related regression we've been seeing.

Comment 14 by mka@chromium.org, Feb 13 2017 

Yes, the problem seems to be the delay of the firmware download from  Issue 682578

Comment 15 by adlr@chromium.org, Feb 13 2017 

Can we dupe this to that?

Comment 16 by mka@chromium.org, Feb 14 2017

Mergedinto: 682578
Status: Duplicate (was: Assigned)
►

Sign in to add a comment