Same identical problem happening to me. Several members in the Chromebooks community on Google+ are having the same identical issue on their Acer 15 models including both the owner and moderator of the community. Several reports on reddit with exact same issue on their Acer 15 models. "Triple BOOT TIME" from a cold start.

I've reshared the issue above here:

http://bit.ly/ChromebooksCommunity

Hopefully we can get this fixed pronto!

I sent feedback April 9 from this Gmail address. Another TC has the same issue on his Acer 15.

A video for extra proof :) https://photos.app.goo.gl/Z5akHhkTzIoUJFoh1

#CBC-RS/TC-watchlist

Feedback from comment #2 is at https://listnr.corp.google.com/product/208/report/85292669791?dateRange=All

From the video, for some reason there's a large delay before the splash-screen even appears.

I had this issue back on Dev 65 when the Play Store became available. It was so bad that I switched back to Beta and attributed it to either the Dev channel or the Play Store.

Was on Beta 65 without the black screen delay before the splash-screen.

Did not have the delay on Stable 65.0.3325.184 (Official Build) (64-bit)

It's back on 65.0.3325.209 (Official Build) (64-bit). 

Play Store is not enabled.
Bluetooth is disabled.
No chrome://flags set.

	
Revision	0
Platform	10323.67.0 (Official Build) stable-channel auron_yuna
Firmware Version	Google_Auron_yuna.6301.59.116
ARC	4691291
JavaScript	V8 6.5.254.43
Flash	29.0.0.113 /opt/google/chrome/pepper/libpepflashplayer.so
User Agent	Mozilla/5.0 (X11; CrOS x86_64 10323.67.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.209 Safari/537.36

My Acer 15 Chromebook started taking longer and longer to turn on.  Within a few days my chromebook will no longer turn on at all.  I've tried everything and no luck. My sister who has the same exact chromebook called me and said that she cannot turn on her computer either.  This all happened on the same day.  Coincidence??  

I bought a new Acer 15 Chromebook CB5-571 a few weeks ago and it booted up very quickly the first few days, but after rebooting in response to a message about an update, I'm experiencing the same delay that everyone else has already described here.  It must be caused by this update. 

gwendal@ I'm not sure who is triaging the OS>Firmware component. We need to get someone looking at this - a lot of people are reporting this problem

We have approx 100 Acer C910 Chromebooks in our school all exhibiting this behavior as soon as they update to 65.0.3325.209. I have tried to build a recovery drive but the utility puts on the previous version that does not have this issue. I assumed the utility would put on 209 and that by doing a fresh install on the devices it might fix whatever the auto update did. Can't test that because I can't install 209 with the utility. But I can confirm this issue on the Acer C910.

Not sure OS->Firmware is the right component, firmware has not changed in ~1 year on this device and firmware boot time in the feedback report is ~700ms as expected:

1101:jumping to kernel                                 706,641 (1,166)

That said, I don't see a long delay in the kernel boot log either, although it could be delayed before it starts logging...

Are these systems updating from R64 to this build or are they coming from an earlier R65 build?

@dlaurie the system updated from an earlier build. They where on 65.0.3325.184 (Platform version: 10323.62.0/1) before and didn't show that issue on the earlier build. The issue occurs right after the update to 65.0.3325.209, Platform 10323.67.0 (Official Build) stable-channel auron_yuna
Firmware
Google_Auron_yuna.6301.59.116
Kanal
Derzeit auf Stabil
ARC-Version
4691291

Hey all,

Just confirming that we're still seeing community reports about this issue on the M66 stable build.

- https://productforums.google.com/forum/#!topic/chromebook-central/gqmwB2A0Lt0

Thanks!

+josafat for help routing 

It is not storage related and affect more machines than Acer.

We are having the issues most noticeably on the Acer C720.  Prior to finding this bug thread we went through and tested different SSD and motherboard, running the proprietary manufacturer shim & updating to the latest each step to no avail.  

ignore #15, I thought it could be b/76202029.
Reviewing the video, it happens between coreboot and kernel handover.

#2, #3, 
- I assume the problem happens at every reboot from power off. Is that correct?
- can we take another report, to compare timing and drive health.

coreboot setup the drive without delay, so it is not an issue of the SSD slow boot up/bring up. 

Next step will be put the device in dev mode and retrieve the bootup timing sequence with the old and new image. Step 4 of 
https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/a-brief-perf-how-to will indicate which job is prevent the graphics from starting.

Today I received Chrome OS 66 on my Acer CB 15 yuna. With this update the boot-up-delay seems to be fixed. Tried several reboots without an issue. 

Same for me, since the update boot-up time has lost the delay.

There was boot time regression in Yuna on previous M65 and earlier M66 units (issue 822330). Problem got resolved in later M66 builds.

+krk to confirm 

Updated to 66.0.3359.137 this morning and the slow boot seems to be resolved. Thanks!

https://screenshot.googleplex.com/R5eifUA2Xik shows a massive improvement in 68 (ToT) If there is a known CL that contributed to this improvement, it may be worth cherrypicking it back into 67 atleast?

Does this owner need to be reassigned (if "Last visit >30 days ago" is accurate)?

I have an Acer 720 - Chrome oS 66.0.3359.137. I have 15-16 seconds of black screen on startup and then another 7 to log in screen..So I don't belive it is fixed

Following up from my comment in #23 I do see a big improvement in Yuna's boot time in M68. There may be a case for cherrypicking the changes back into earlier branches. Reassigning to josafat@ to take a call.

I have an Acer C-720 and still have the slow (14 seconds) boot. I am updated to 66.0.3359.137.

Issue is fixed on the Acer 15, auron_yuna.


Google Chrome	66.0.3359.137 (Official Build) (64-bit)
Revision	0
Platform	10452.74.0 (Official Build) stable-channel auron_yuna
Firmware Version	Google_Auron_yuna.6301.59.116
ARC	4734322
JavaScript	V8 6.6.346.24
Flash	29.0.0.140 /opt/google/chrome/pepper/libpepflashplayer.so
User Agent	Mozilla/5.0 (X11; CrOS x86_64 10452.74.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.137 Safari/537.36

re c#27 do we see same improvements in M67?

This issue now seems to be affecting the ASUS Flip C100P and the CTL NL6 after both updated to version 66.0.3359.137 

Two different machines with different hardware and firmware but both are now exhibiting a lengthy black screen before reaching the first splash screen for sign-in. Followed by a delay opening the browser window once you have signed in.

I am seeing similar issues on the latest builds for Asus C302A.

#32, #31: can you collect a feedback report (add bug id in subject) with the latest build?

Have submitted a feedback report. Issue still present on C100P after updating to 66.0.3359.158
Unresponsive black screen after signing-in may actually be worse (lasting a minimum of 15 seconds) with ver. xxxx.158 

(Bulk Edit) Adding the new conops Chrome OS hotlist to all open issues with the "#CBC-RS/TC-watchlist" tag, our former tracking tag.

Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.

<UI triage> Bug owners, please add the appropriate component to your bug. Thanks!

I'm still seeing this on my 2013 Pixel.

Please restore my faith in Google and tell me that Google isn't simply going to leave their $1000+ Flagship Chromebook in this broken state.  I hope you'll agree that shouldn't be acceptable by anyone's standards.

I should note that I did get an unexpected post-EOL update on the 2013 Pixel but the 15 second boot delay remains.  This basically TRIPLES the normal boot time! Fast boot is one of the marquee features of a Chromebook is it not?

Currently running.
Version 69.0.3497.120 (Official Build) (64-bit)

This issue remains on Acer C720 and C740 models on Version 70.0.3538.110 (Official)

HP Chromebook 11 G5 EE and Dell Chromebook 13-7310 are unaffected on the same Chrome OS version.

HP hits the white background chrome logo screen in ~5 seconds
Dell hits the white background chrome logo screen in ~4 seconds

Acer C720/C740 now take 15-20 seconds to get to the white background chrome logo screen. Ironically these Acer devices have a sticker on them that says "7 seconds fast bootup".

Any traction on this issue?  Because these devices take 3x as long to start up many teachers in our school district are reporting them as broken and taking them out of service.

This bug seems to be a mix of update issues since last year on several devices.

Seems like many users report this issue has been fixed on M66 or later builds.

If you're still experiencing this issue on the latest build (M70 or later), can you submit a feedback report using Alt-Shift-I and add bug id in your description? And then post here that you've submitted a feedback report?

I'd like to close this bug and open a new one that's more targeted to recent build issues.

Bug report submitted for Acer C740.  I put "bug issue 831549" in the description as well as a link to this thread.

trumbull,

Thanks for the attention to this issue.

My 2013 Pixel Chromebook is stuck at EOL Version 69.0.3497.120 (Official Build) (64-bit) unless this gets fixed.  How would you like me to handle reporting that?

Scott

I had already opened issue 891679 for the 2013 Pixel and this problem.

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.