I take it that you're using the keyboard and/or touchpad to try to turn the screen back on, right?

The next time you see this, please file a feedback report with Alt+Shift+i immediately after rebooting and logging in, and then mention it on this bug. Thanks!

Just happened again, I clicked alt+shift+i right away and reported it, not
sure what you mean by then mention it on this bug.

Thank you for providing more feedback. Adding requester "derat@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

#3: Thanks. Was the "Send system and app information, and metrics" checkbox unchecked when you submitted the feedback? If so, please submit feedback again and make sure that it's checked. (Otherwise, the logs that I need to look at don't get attached.)

Will leave on next time.

Thank you for providing more feedback. Adding requester "derat@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Thanks, please leave another comment on this bug after you've sent feedback with logs so I can take a look.

Feedback reports:

http://feedback/#/Report/85115513780

...
271 | 2018-02-23 09:29:37 | ACPI Wake | Deep S3
272 | 2018-02-23 12:03:29 | ACPI Enter | S3
273 | 2018-02-23 12:57:55 | EC Event | Lid Open
274 | 2018-02-23 12:57:55 | ACPI Wake | Deep S3
275 | 2018-02-25 22:07:57 | System boot | 2
276 | 2018-02-25 22:07:57 | EC Event | Power Button
277 | 2018-02-25 22:07:57 | Power Button Override
278 | 2018-02-25 22:07:57 | Chrome OS Developer Mode

powerd.PREVIOUS starts mid-log at 0225/155419. Nothing but audio activity starting and stopping from then until the end of the log:

[0225/220742:INFO:activity_logger.cc(20)] Audio activity started
[0225/220742:INFO:activity_logger.cc(20)] Audio activity stopped
[0225/220742:INFO:daemon.cc(525)] Power button down
[0225/220742:INFO:main.cc(218)] Launching "sync"
EOF

---

http://feedback/#/Report/85117802538

...
279 | 2018-02-26 11:12:37 | System boot | 3
280 | 2018-02-26 11:12:37 | EC Event | Power Button
281 | 2018-02-26 11:12:37 | Power Button Override
282 | 2018-02-26 11:12:37 | Chrome OS Developer Mode

powerd.PREVIOUS is more interesting here. It looks like Chrome was hanging (i.e. not acknowledging button presses) at the end of it:

...
[0226/111145:INFO:daemon.cc(525)] Power button down
[0226/111145:INFO:main.cc(218)] Launching "sync"
[0226/111145:INFO:daemon.cc(525)] Power button up
[0226/111147:INFO:daemon.cc(525)] Power button down
[0226/111147:INFO:main.cc(218)] Launching "sync"
[0226/111149:INFO:daemon.cc(562)] Didn't receive power button acknowledgment from Chrome
[0226/111150:INFO:daemon.cc(525)] Power button up
[0226/111152:INFO:daemon.cc(525)] Power button down
[0226/111152:INFO:main.cc(218)] Launching "sync"
[0226/111154:INFO:daemon.cc(562)] Didn't receive power button acknowledgment from Chrome
[0226/111200:INFO:daemon.cc(525)] Power button up
[0226/111202:INFO:daemon.cc(525)] Power button down
[0226/111202:INFO:main.cc(218)] Launching "sync"
[0226/111203:INFO:daemon.cc(525)] Power button up
[0226/111205:INFO:daemon.cc(771)] On AC (USB_PD, 0.000A at 14.9V, max 3.0A at 15.0V) with battery at 100%, 5.551/5.551Ah at 0.193A, full
[0226/111213:INFO:activity_logger.cc(20)] Hovering stopped 20 sec ago
[0226/111217:INFO:daemon.cc(525)] Power button down
[0226/111217:INFO:main.cc(218)] Launching "sync"
[0226/111217:INFO:daemon.cc(525)] Power button up
[0226/111222:INFO:daemon.cc(525)] Power button down
[0226/111222:INFO:main.cc(218)] Launching "sync"
EOF

session_manager agrees:

2018-02-26T11:11:24.145634-05:00 WARNING session_manager[1187]: [WARNING:liveness_checker_impl.cc(64)] Browser hang detected!
...
2018-02-26T11:11:49.148505-05:00 ERR session_manager[1187]: [ERROR:object_proxy.cc(582)] Failed to call method: org.chromium.LibCrosServiceInterface.CheckLiveness: object_path= /org/chromium/Li
bCrosService: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the repl
y, the reply timeout expired, or the network connection was broken.

There are a bunch of Chrome segfaults before then.

I can't find any crashes from your device, though (the client ID in your feedback reports is empty). Do you have crash-reporting disabled?

---

This doesn't seem power-related. Cc-ing Albert in case these symptoms ring any bells.

xiyuan@ possibly related to the hang issue you've been looking at? 

It could. But we only know for sure when seeing the stack somehow.

For the 2nd feedback, chrome seems getting into a crash loop. If that is the cause, it is a different issue.