Version 53.0.2785.103 beta (64-bit)
Platform 8530.81.0 (Official Build) beta-channel samus
ARC Version 3251841
Firmware Google_Samus.6300.174.0


Still happening. When booting from cold it always just shows a blank white screen. I have to push refresh+power to hard reset. Then I get the normal white screen with Chrome logo. 

Any attached USB or SD devices? Are these devices in dev mode?

Nope none at all sir, zero. Just running official beta channel enabled in settings. Cold boot, power on, and blank white screen. 

Version 53.0.2785.103 beta (64-bit)
Platform 8530.81.0 (Official Build) beta-channel samus
ARC Version 3251841
Firmware Google_Samus.6300.174.0

If it was just one device I'd think it was a hardware issue, but two of them is far more troubling...

Have you filed a feedback report (alt+shift+i) ? There might be something in the logs that would help us track it down...

Done, but I'll do it again. Anytime more helpful than another?

As soon as possible after the issue happens.

What email address did you use for the report? I don't see it.

We have a user reporting this as well, device is in Kiosk mode and is enrolled in device management.  Access to submit a feedback report is very limited.  I can provide the directory ID, etc. if that will help.

User reports that the device is 'stuck' at a white screen.  Device is offline in admin console.

Google Chrome Version	53.0.2785.103
Platform Version	8530.81.0 (Official Build) beta-channel panther
Firmware Version	Google_Panther.4920.24.26

https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=white%20screen&lReport=13359959193 is a feedback report describing the same symptoms. Not sure if it's the same one shyepgay235@ filed.

warx@ I know you investigated hang issues with debug mode, could you take a look at this one too.

+snanda for thoughts.

From comment 1, I saw 'always' so I assume it is consistently happening. None of my devices can reproduce this issue. abodenha@, can I borrow your samus or if that is not available, I can check panther on crosdistros.

You're welcome to grab my samus. It's not failing for me either. I'm hoping there's something useful in the feedback reports.

Hmm, I see a bunch of suspend resumes and then one full boot.  Could the issue be at resume and not boot?

Please try the following sequence of keystrokes and see if they allow the system to come up:
- press alt-volup-x keys up to three times within a 5 second period
- if the above doesn't work, press alt-volup-r once

If the system becomes functional at this point please file feedback report (alt-shift-i) and ping this bug.




192 | 2016-09-15 14:26:47 | ACPI Wake | S5
193 | 2016-09-15 14:26:47 | Wake Source | Power Button | 0
194 | 2016-09-15 14:58:32 | ACPI Enter | S3
195 | 2016-09-15 15:08:34 | ACPI Wake | S3
196 | 2016-09-15 15:08:34 | Wake Source | GPIO | 27
197 | 2016-09-15 15:08:34 | EC Event | Lid Open
198 | 2016-09-15 15:13:16 | ACPI Enter | S3
199 | 2016-09-15 15:17:41 | ACPI Wake | S3
200 | 2016-09-15 15:17:41 | Wake Source | GPIO | 27
201 | 2016-09-15 15:17:41 | EC Event | Lid Open
202 | 2016-09-15 15:46:59 | ACPI Enter | S3
203 | 2016-09-16 00:37:16 | ACPI Wake | S3
204 | 2016-09-16 00:37:16 | Wake Source | GPIO | 27
205 | 2016-09-16 00:37:16 | EC Event | Lid Open
206 | 2016-09-16 00:37:27 | System boot | 147
207 | 2016-09-16 00:37:27 | SUS Power Fail
208 | 2016-09-16 00:37:27 | System Reset
209 | 2016-09-16 00:37:27 | ACPI Wake | S5
210 | 2016-09-16 00:37:27 | Wake Source | Power Button | 0

I have filed numerous reports through Alt+Shift+I after every time it has
happened as recent as today.

Version 53.0.2785.129 beta (64-bit)
Platform 8530.90.0 (Official Build) beta-channel samus
ARC Version 3284968
Firmware Google_Samus.6300.174.0

I got a minnie which could repro the bug. re comment 12: I tried the keystrokes. It didn't bring the system back.

This actually happened while Chrome OS was rebooting to update to:
Version 54.0.2840.51 beta (64-bit)
Platform 8743.57.0 (Official Build) beta-channel samus
ARC Version 3327608
Firmware Google_Samus.6300.174.0

re comment 15, my minnie device may hang on white screen with chrome logo sometimes during dev. So it maybe different from the reporter's bug.

this happens to me with my Chromebook Pixel 2015 nearly at every boot. This
even happens when there is an update to Chrome OS applied, and it says
restart to update. There is no logo whatsoever. It just goes from a black
screen to a completely blank white screen and absolutely nothing happens 1
minute 2 minutes or 5 minutes later. The only way to use your Chromebook is
to refresh and power button.

95% of the time I open my i7 16GB Pixel 2015, this is what I am greeted with. Picture was taken just 3 minutes ago.
No amount of waiting does anything, just frozen. I have to push the refresh+power button every time. Going on 2+ months now...
Currently on:
Version 55.0.2883.35 beta (64-bit)
Platform 8872.35.0 (Official Build) beta-channel samus
ARC Version 3426244
Firmware Google_Samus.6300.174.0

Deleted: IMG_20161107_193034.jpg 2.9 MB

	IMG_20161107_193034.jpg 2.9 MB View Download

I can no longer power down my Chromebook. When I click the software power button to power down, it goes to this same white screen. So I cannot power on or off my $1,000+ Chromebook without there being some kind of issue. Does me having to push the refresh button+power cause any harm to my Chromebook? I mean I need to do that 10 times a day. 

Version 55.0.2883.54 beta (64-bit)
Platform 8872.54.0 (Official Build) beta-channel samus
ARC Version 3500695
Firmware Google_Samus.6300.174.0 

Still happening for me

What's super weird is that I can even push the software power button to shut down the Chromebook and it will do the same thing, fade to a blank white screen and hang indefinitely. I have to push power+refresh to hard reset, just to power off my Chromebook Pixel. 

Back to this issue. from the logs in comment 9, I didn't see anything wrong in powerd logs.

For the elogs in comment 12, I do see several "System boot -> SUS Power Fail -> System Reset". But I don't know how they are triggered.

Daniel, do you have an idea on this?

It's not clear from the comments whether the problem is that:

a) the system is hanging at boot before frecon displays the logo, or

b) the system is failing to shut down and getting stuck after fading to white (and then remaining in this state even after the lid is closed and opened).

I think that b) is more likely, since I think that a) would mean that frecon *is* managing to clear the screen to white but not managing to draw the logo, which would be weird.

If that's indeed the case, I'd check file:///var/log/messages after hard-resetting to see if it has any information about why the system didn't shut down previously.

Maybe it's also possible that the firmware could be clearing the screen to white, but I don't know if that happens outside of dev mode.

I would be personally happy to give you whatever details you need. I have
exhibited both A and B as you explain. The initial issue I noticed was upon
boot I would be greeted with a blank white screen that goes nowhere. It
indefinitely stays a white screen and does not boot up. Then I also noticed
after that same update that often when I click the software power down
button the same thing would happen in reverse it would close everything and
go to a white screen but never power down. It would just stay at that blank
white screen, the same thing I see when I power on indefinitely.

I have seen the newest feedback report: https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=640458&lReport=17173416493

So this report is (b) case, and report in #9 is (a) case.

Both of them have "SUS Power Fail and System Reset" which is not shown in my test device's eventlog (veyron_minnie, which doesn't have this bug). So we probably just need to find out why "SUS Power Fail and System Reset" are triggered.

Btw, I have seen many "Valid eCryptfs headers not found in file header region or xattr region" in (b) case, which might indicate not clean shutdown.

I think it's not uncommon for "SUS Power Fail" to be logged when the system boots normally; see e.g.  http://crbug.com/652110#c19 . I'm not sure that it's related to this.

ok thanks. And the long span timestamp may also indicate this is not the root cause.

Just keeping you apprised, it just happened from a cold boot.
Version 55.0.2883.87 beta (64-bit)
Platform 8872.70.0 (Official Build) beta-channel samus
ARC Version 3554338
Firmware Google_Samus.6300.174.0

Adding more people to see if they have theories about how we could end up stuck at a solid white screen during boot.

Coming back to comment #8 
> We have a user reporting this as well, device is in Kiosk mode and is enrolled in device management.
[...]
> User reports that the device is 'stuck' at a white screen.  Device is offline in admin console

What kiosk-app is he using ?
if he is using the very simple 'Kiosk' application simply fetching URL (aka  https://chrome.google.com/webstore/detail/kiosk/afhcomalholahplbjhnmahkoekoijban)
The white screen is the typical behavior when it has an invalid URL / no URL / cannot fetch it.
In this mode, Ctrl+A will ask for the 'admin' password set in the kiosk
(ctrl+alt+S quickly startup will go back to the regular chromeOS mode)

For me I am not in Kiosk mode at all. I know one reporter is, but for me I
am just using a Pixel 2015 with nothing more than beta channel.

Can someone who has the problem please attach a video of the device booting up (all the way from off state)?

I will do that next time it happens. But that's the thing. From a cold boot
the screen turned onto a blank white screen and it's there for all
eternity. I don't think of it it will help because it just goes from cold
boot to blank white screen. Nothing else happens.

SO I have forgotten to take a video any of the 5 times it has happened in the past day. Do you really want a video of just a cold boot screen closed to a white screen? 

Also, this happens when you turn it off. Less often but it happens. I commented previously on this. And it just happened again. I click the software power button in the lower right hand corner, and everything closes and goes to a white screen. Normally it would then power off, but it hangs just the same way only in reverse as when it powers on. 

Yeah a video would help, because it would likely tell me if it's a sw or a hw problem. I suspect the latter, but have no evidence.