Another Chromebook Central thread
https://productforums.google.com/forum/#!topic/chromebook-central/dQHPOS_OaSI

Same issue for me on 67.0.3396.99, with Toshiba 2 (2014 version) - it now wont wake properly with a blank screen on resume. Only fix is to force it off and reboot. :-(

Feedback reports with logs

Users reporting that their Chromebooks turn off or shutdown when they close the lid (even when settings are set to sleep)
M67 - https://listnr.corp.google.com/report/85526613328
M67 - https://listnr.corp.google.com/report/85518898493
M67 - https://listnr.corp.google.com/report/85518330216
M67 - https://listnr.corp.google.com/report/85517166488

M68 Beta - https://listnr.corp.google.com/report/85515330482

Additional reports from users that they cannot wake their computer from sleep and just see a black screen:
M67 - https://listnr.corp.google.com/report/85525410571
M67 - https://listnr.corp.google.com/report/85522241345
M67 - https://listnr.corp.google.com/report/85522088221
M67 - https://listnr.corp.google.com/report/85519227344
M67 - https://listnr.corp.google.com/report/85518704087
M67 - https://listnr.corp.google.com/report/85516577953
M67 - https://listnr.corp.google.com/report/85513029130
M67 - https://listnr.corp.google.com/report/85512477199

M68 Beta - https://listnr.corp.google.com/report/85520225730

This report says that the audio of video starts playing when they open their Chromebook's lid but the screen stays black:
M67 - https://listnr.corp.google.com/report/85513290682

If the issue is reproducible for you, please do the following:

1. Note the time when the system shuts down unexpectedly.
2. After the system reboots, sign in and immediately file a feedback report with Alt+Shift+i. Make sure that the "Send system and app information, and metrics" checkbox is checked, and in the text field at the top, mention the time when the issue occurred and this bug ID (859358).
3. Leave a comment here mentioning that you filed a feedback report. Include the email address from which you sent the report if it isn't the same one that you're using to comment here.

From clicking through the feedback reports linked in #4 and #5, it sounds like different issues are being discussed.

Danny or Katherine, is this something that you've seen?

Re:  comment 6. I've asked users this as well in the CBC topic. I believe in V67 you can also send feedback from the sign in screen.

Hi everyone (again),

Could you please try these steps when your chromebook doesn't wake up from sleep?

1. Press the these 3 keys together. alt-volume up-x key combination 3 times within a 10 second period.  Wait about 5 seconds. If the system reboots, file feedback report. If not, go to the step below.

2. hit alt-volup-r key combo once. If the system reboots, file feedback report. 
 If not, go to the step below.

3. hit power+refresh key combo once. The system will reboot here. File feedback report.

In the feedback, please post which step worked.  If steps 1 or 2 are successful there may be additional detail in the feedback report to help identify the root cause.

Sent feedback at 11:21 AM ET with bug number in first line. Email used was this one.

willlandrieu: Thanks! I've filed issue 860305 with details from your report. Please feel free to star it for updates.

Also filed issue 860307 based on a feedback report about a leon device crashing while suspending.

I sent feedback with "crbug 860561" as the first line; not sure what was going through my head at that moment. 

The report should be from a Peppy on R67-10575.58.0 from this address.

#12: Thanks, filed issue 861641 based on that report.

Add a Dell Wolf to the list of affected models; mine started failing to resume July 18th, though it has been on the latest stable v67 since it was released late June.  Always powers up correctly on lid open if shut down though.  Will submit a feedback report tonight.

Possibly related, Adblock Plus updated to 3.2 on July 17, not sure if some get new versions earlier.

Just sent feedback after the bug happened. I used Alt+Volup+X once which got it to show a picture again.

The report has 'crbug 859358' in the first line and is from this email.

I'm on M70 with the Dell Wolf model. No issues here, possibly related to Canary. Could definitely be something else too, of course. 

Google Chrome	70.0.3498.0 (Official Build) canary (64-bit)
Revision	47e231210ca1a01b1b5d60231207d505cb7ff0af-refs/branch-heads/3498@{#1}
Platform	10897.0.0 (Official Build) canary-channel wolf
Firmware Version	Google_Wolf.4389.24.62

For failure in #12-#13,

It does resume properly but appears there's a userspace crash at 14:52:50 followed by the user directed crash (Alt + VolUp + X) at 14:53:10.  Note, storage seems amiss upon resume and a similar log signature and repro (black screen) mentioned here: crbug.com/661656

+Gwendal for insights on storage failure.


2018-07-21 14:52:46.426 5 powerd_suspend[3911]:  Resume finished
...
2018-07-21 14:52:50.552 4 kernel  :  [  560.829932] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
2018-07-21 14:52:50.682 3 979:979 : storage_monitor_chromeos.cc(215): NOTREACHED() hit.
2018-07-21 14:52:50.682 3 979:979 : 
2018-07-21 14:52:50.682 3 979:979 : Crash dump received by crash_reporter
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.201345:WARNING:diagnostics_writer.cc(211)] [FAIL] 009 PathUserData (Path contents too large (2168828392) for: /home/chronos)
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.208988:WARNING:diagnostics_writer.cc(211)] Finished 18 tests.
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209068:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Install type
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209100:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Chrome version test
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209131:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: User data path
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209162:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Local state path
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209192:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: App dictionaries directory path
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209243:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Resources path
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209276:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Available disk space
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209307:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: User preferences integrity
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209337:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Local state integrity
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209367:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Bookmark file
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209397:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Web Data database
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209427:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Cookie database
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209457:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Favicons database
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209502:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: History database
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209531:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Top Sites database
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209559:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Database tracker database
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209587:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: NSS certificate database
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209615:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: NSS Key database
2018-07-21 14:52:50.682 3 979:979 : [0721/145311.209636:WARNING:diagnostics_writer.cc(211)] Finished All Recovery operations.
2018-07-21 14:52:58.000 6 activity_logger.cc(20):  Video activity stopped; last reported 20 sec ago
2018-07-21 14:53:10.000 6 suspend_delay_controller.cc(121):  Unregistering suspend delay 58261506 (chrome) due to D-Bus client :1.9 going away
2018-07-21 14:53:10.000 6 suspend_delay_controller.cc(121):  Unregistering dark suspend delay 58294274 (chrome) due to D-Bus client :1.9 going away
2018-07-21 14:53:10.200 6 kernel  :  [  580.510426] sysrq: SysRq : Cros dump and crash
2018-07-21 14:53:10.200 6 kernel  :  [  580.510498] sysrq_x_cros_signal_process: signal 6 chrome pid 979 tgid 979
2018-07-21 14:53:10.415 4 crash_reporter[4059]:  Received crash notification for chrome[979] user 1000 (called directly)

report sent with 'crbug 859358' in dscription

#20: Thanks, I've filed  issue 868097  based on your feedback report -- feel free to star it or provide more details there.

I had the same issue: https://bugs.chromium.org/p/chromium/issues/detail?id=867733

Happened again after updating to 68.0.3440.87 beta on swanky. Report is from this email.
 

Forgot to mention, this may be another CBC post. I have requested it be unlocked/ un-dupped so that I could get more info from the OP.

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

Sent feedback from this email with "crbug 859358 in the first line."

#25: Thanks, added them to issue 860305. Please use that bug for further discussion of swanky.

Bug appears 100% solved in 68.0.3440.87 on Toshiba CB30-102.
* login in, start browser session, close lid, wait 2 sec, open lid
* screen wakes up, login prompt, browser session still active. 

Works for me. Great work, thanks guys!

Another Chromebook Central thread
https://productforums.google.com/forum/#!topic/chromebook-central/aJOG5pJ43q0;context-place=forum/chromebook-central

See a bunch of errors in UI_LOG that seem consistent with other reports of black screen.

[1290:1290:0621/235126.276789:ERROR:input_method_manager_impl.cc(1080)] IMEEngine for "jkghodnilhceideoidjikpgommlajknk" is not registered
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
[1290:1290:0621/235126.524874:ERROR:geolocation_handler.cc(146)] Failed to get Geolocation data: 0
[1445:1454:0621/235126.529242:ERROR:drm_gpu_display_manager.cc(210)] There is no display with ID 2785062953156608
[1445:1454:0621/235126.650271:ERROR:drm_gpu_display_manager.cc(210)] There is no display with ID 2785062953156608
[1445:1454:0621/235126.686187:ERROR:drm_gpu_display_manager.cc(210)] There is no display with ID 2785062953156608
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
[1290:1290:0621/235449.286080:ERROR:input_method_manager_impl.cc(1080)] IMEEngine for "jkghodnilhceideoidjikpgommlajknk" is not registered
[1290:1419:0621/235449.499324:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1290:1419:0621/235449.499554:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1290:1419:0621/235449.499877:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1290:1419:0621/235449.500179:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1290:1419:0621/235449.500463:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1290:1419:0621/235449.500772:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1290:1419:0621/235449.505448:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1290:1419:0621/235449.506088:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1290:1419:0621/235451.074333:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1290:1419:0621/235451.074573:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1290:1419:0621/235451.077074:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1290:1419:0621/235451.093863:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1290:1419:0621/235451.094920:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1290:1419:0621/235451.097620:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /opt/google/chrome/chrome_renderer.service
[1:14:0621/235455.623826:ERROR:adm_helpers.cc(73)] Failed to query stereo recording.
[1:15:0621/235520.792860:ERROR:adm_helpers.cc(73)] Failed to query stereo recording.
[1290:1290:0621/235542.643547:ERROR:object_proxy.cc(616)] Failed to call method: org.chromium.ArcOemCrypto.BootstrapMojoConnection: object_path= /org/chromium/ArcOemCrypto: org.freedesktop.DBus.Error.Failed: arc-oemcrypto/dev_mode:OEMCrypto disabled in dev mode
[1290:1290:0621/235553.258608:ERROR:object_proxy.cc(616)] Failed to call method: org.chromium.ArcOemCrypto.BootstrapMojoConnection: object_path= /org/chromium/ArcOemCrypto: org.freedesktop.DBus.Error.Failed: arc-oemcrypto/dev_mode:OEMCrypto disabled in dev mode
[1290:1290:0621/235558.807390:ERROR:object_proxy.cc(616)] Failed to call method: org.chromium.ArcOemCrypto.BootstrapMojoConnection: object_path= /org/chromium/ArcOemCrypto: org.freedesktop.DBus.Error.Failed: arc-oemcrypto/dev_mode:OEMCrypto disabled in dev mode
[1290:1290:0621/235615.624432:ERROR:textfield.cc(1754)] Not implemented reached in virtual bool views<IPv6: 2>Textfiel<IPv6: 3>ShouldDoLearning()
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
[1445:1445:0621/235919.244083:ERROR:gles2_cmd_decoder.cc(18008)] [.DisplayCompositor-0x18d317216a00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[1445:1445:0621/235919.244529:ERROR:gles2_cmd_decoder.cc(18008)] [.DisplayCompositor-0x18d317216a00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[1445:1445:0621/235919.244711:ERROR:gles2_cmd_decoder.cc(10115)] [.DisplayCompositor-0x18d317216a00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1445:1445:0621/235919.244901:ERROR:gles2_cmd_decoder.cc(10115)] [.DisplayCompositor-0x18d317216a00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1445:1445:0621/235919.260263:ERROR:gles2_cmd_decoder.cc(10115)] [.DisplayCompositor-0x18d317216a00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1445:1445:0621/235919.260792:ERROR:gles2_cmd_decoder.cc(10115)] [.DisplayCompositor-0x18d317216a00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1445:1445:0621/235919.384398:ERROR:gles2_cmd_decoder.cc(10115)] [.DisplayCompositor-0x18d317216a00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1445:1445:0621/235919.385100:ERROR:gles2_cmd_decoder.cc(10115)] [.DisplayCompositor-0x18d317216a00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1445:1445:0622/004919.332039:ERROR:gles2_cmd_decoder.cc(18008)] [.DisplayCompositor-0x18d317216a00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[1445:1445:0622/004919.332200:ERROR:gles2_cmd_decoder.cc(18008)] [.DisplayCompositor-0x18d317216a00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[1445:1445:0622/004919.332298:ERROR:gles2_cmd_decoder.cc(10115)] [.DisplayCompositor-0x18d317216a00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1445:1445:0622/004919.332390:ERROR:gles2_cmd_decoder.cc(10115)] [.DisplayCompositor-0x18d317216a00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1445:1445:0622/004921.094293:ERROR:gles2_cmd_decoder.cc(18008)] [.DisplayCompositor-0x18d317216a00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[1445:1445:0622/004921.094686:ERROR:gles2_cmd_decoder.cc(18008)] [.DisplayCompositor-0x18d317216a00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[1445:1445:0622/004921.094927:ERROR:gles2_cmd_decoder.cc(10115)] [.DisplayCompositor-0x18d317216a00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1445:1445:0622/004921.095242:ERROR:gles2_cmd_decoder.cc(10115)] [.DisplayCompositor-0x18d317216a00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1445:1445:0622/004921.236383:ERROR:gles2_cmd_decoder.cc(10115)] [.DisplayCompositor-0x18d317216a00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1445:1445:0622/004921.236583:ERROR:gles2_cmd_decoder.cc(10115)] [.DisplayCompositor-0x18d317216a00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1445:1445:0622/011021.680567:ERROR:gles2_cmd_decoder.cc(18008)] [.DisplayCompositor-0x18d317216a00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[1445:1445:0622/012705.562117:ERROR:gles2_cmd_decoder.cc(18008)] [.DisplayCompositor-0x18d317216a00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name

Another user report
https://productforums.google.com/forum/#!topic/chromebook-central/reXj-57zj5E

I got 2 new Lenovo 500e Chromebooks.
And one of them is showing this behavior..

The powerd log shows this entry:
[1201/052641:INFO:state_controller.cc(1078)] Ready to perform lid-closed action (suspend)
[1201/052641:INFO:suspender.cc(377)] Starting request 93454337
[1201/052641:INFO:daemon.cc(544)] Reading wakeup count from /sys/power/wakeup_count
[1201/052641:INFO:daemon.cc(548)] Read wakeup count 3
[1201/052641:INFO:internal_backlight_controller.cc(734)] Setting brightness to 0 (0%) over 0 ms
[1201/052642:INFO:suspend_delay_controller.cc(137)] Announcing suspend request 93454337 with 4 pending delay(s) and 0 outstanding delay(s) from previous request
[1201/052642:INFO:suspend_delay_controller.cc(86)] Got notification that delay 93454340 (btdispatch) is ready for suspend request 93454337 from :1.40
[1201/052642:INFO:suspend_delay_controller.cc(86)] Got notification that delay 93454338 (shill) is ready for suspend request 93454337 from :1.4
[1201/052642:INFO:suspend_delay_controller.cc(86)] Got notification that delay 93454337 (trunksd) is ready for suspend request 93454337 from :1.6
[1201/052642:INFO:daemon.cc(1077)] Chrome is using normal display mode
[1201/052642:INFO:suspend_delay_controller.cc(86)] Got notification that delay 93454339 (chrome) is ready for suspend request 93454337 from :1.18
[1201/052642:INFO:suspend_delay_controller.cc(223)] Notifying observers that suspend is ready
[1201/052642:INFO:suspender.cc(457)] Starting suspend
[1201/052642:INFO:main.cc(266)] Running "/usr/bin/powerd_setuid_helper --action=suspend  --suspend_wakeup_count_valid --suspend_wakeup_count=3 --suspend_to_idle"

But once that is run, it will not be able to resume.
Thats from powerd.PREVIOUS

Google Chrome	70.0.3538.76 (Official Build) (64-bit)
Revision	22757df8a5ddfacf2eaf57b85f4ea54c14b8f87a-refs/branch-heads/3538@{#1031}
Platform	11021.56.0 (Official Build) stable-channel coral-unibuild (astronaut babymega babytiger blacktip blacktip360 blacktiplte blue bruce coral epaulette lava nasher nasher360 porbeagle rabbid robo robo360 santa whitetip)
Firmware Version	Google_Coral.10068.71.0
Customization ID	ROBO360
ARC	5081697
JavaScript	V8 7.0.276.31
Flash	31.0.0.122 /opt/google/chrome/pepper/libpepflashplayer.so
User Agent	Mozilla/5.0 (X11; CrOS x86_64 11021.56.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.76 Safari/537.36

Debug log created via:  chrome://net-internals "Chrome OS", Store logs

Deleted: debug-logs_20181201-010502.tgz 971 KB

debug-logs_20181201-010502.tgz 971 KB Download

And now attaching debug logs from the one Lenovo 500e that works..
Perhaps one can look thru to see the differences..

Here is what I would think would be in the bad ones powerd..
From the worng one:
[1201/002659:INFO:main.cc(266)] Running "/usr/bin/powerd_setuid_helper --action=suspend  --suspend_wakeup_count_valid --suspend_wakeup_count=17 --suspend_to_idle"
[1201/002712:INFO:daemon.cc(636)] powerd_suspend returned 0
[1201/002712:INFO:suspender.cc(416)] Finishing request 81002503 successfully after 13s
[1201/002712:INFO:internal_backlight_controller.cc(734)] Setting brightness to 19200 (100%) over 0 ms
[1201/002712:INFO:daemon.cc(464)] Lid opened
[1201/002712:INFO:input_device_controller.cc(286)] Configuring devices for mode "laptop"
[1201/002712:INFO:input_device_controller.cc(217)] Un-inhibiting /sys/devices/pci0000:00/0000:00:16.3/i2c_designware.3/i2c-9/i2c-ELAN0001:00/input/input8
[1201/002712:INFO:input_device_controller.cc(217)] Un-inhibiting /sys/devices/pci0000:00/0000:00:17.0/i2c_designware.4/i2c-10/i2c-ELAN0000:00/input/input7
[1201/002712:INFO:input_device_controller.cc(217)] Un-inhibiting /sys/devices/pci0000:00/0000:00:17.1/i2c_designware.5/i2c-11/i2c-WCOM50C1:00/0018:2D1F:003F.0001/input/input5
[1201/002712:INFO:input_device_controller.cc(205)] Disabling wakeup for /sys/devices/pci0000:00/0000:00:16.3/i2c_designware.3/i2c-9/i2c-ELAN0001:00/input/input8 through /sys/devices/pci0000:00/0000:00:16.3/i2c_designware.3/i2c-9/i2c-ELAN0001:00
[1201/002712:INFO:input_device_controller.cc(205)] Disabling wakeup for /sys/devices/pci0000:00/0000:00:17.0/i2c_designware.4/i2c-10/i2c-ELAN0000:00/input/input7 through /sys/devices/pci0000:00/0000:00:17.0/i2c_designware.4/i2c-10/i2c-ELAN0000:00



vendor               | coreboot
version              | Google_Coral.10068.71.0
release_date         | 07/04/2018
size                 | 16384 KB
ro bios version      | Google_Coral.10068.34.0
Boot switch status:
  Recovery button: released
  Developer mode:  not enabled
  RO firmware:     protected
Boot reason (0): normal
Boot firmware: B
Active EC code: RW
Raw log:
arch                   = x86                            # Platform architecture

Deleted: debug-logs_20181201-011131.tgz 813 KB

debug-logs_20181201-011131.tgz 813 KB Download

#31: I don't see anything conclusive there, unfortunately. The messages file just shows the system suspending and then booting instead of resuming:

...
2018-12-01T05:26:42.631730+00:00 NOTICE powerd_suspend[9520]: Going to suspend-to-RAM state: args=--suspend_duration=-1 --suspend_to_idle --wakeup_count=3
2018-12-01T05:26:42.764394+00:00 NOTICE powerd_suspend[9572]: Suspending console since S0ix can fail if console not suspended
2018-12-01T05:26:42.774995+00:00 NOTICE powerd_suspend[9576]: Disabling Bluetooth HCI mode change event before suspend
2018-12-01T05:26:42.892065+00:00 NOTICE powerd_suspend[9581]: Available order 3 pages: 11784
2018-12-01T05:26:42.908757+00:00 NOTICE powerd_suspend[9584]: Finalizing suspend
2018-12-01T05:26:42.916201+00:00 INFO kernel: [ 1231.503183] PM: suspend entry 2018-12-01 05:26:42.915114695 UTC
2018-12-01T00:29:07.241880-05:00 INFO kernel: [    0.000000] Initializing cgroup subsys cpuset
2018-12-01T00:29:07.241990-05:00 INFO kernel: [    0.000000] Initializing cgroup subsys cpu
2018-12-01T00:29:07.241993-05:00 INFO kernel: [    0.000000] Initializing cgroup subsys cpuacct
2018-12-01T00:29:07.241994-05:00 NOTICE kernel: [    0.000000] Linux version 4.4.153-15155-g656ec00c3ce2 (chrome-bot@swarm-cros-558) ...

(The system clock timestamps are all over the place, too.)

Thanks derat,

It is a strange issue and only occurs for the one device from a sleep state.

How to produce issue:
Direct Result of the Lenovo 500e going into a "sleep" state Via:

1a. Closing the lid, with the "go to sleep state, when lid is closed" turned on.
1b. Log in, Keyboard combo: "Search" + "Shift" + "L" = go to sleep.
1c. Log in, sit idle for chromebook to go to sleep state. (Eventually side poweron button LED goes off.) ~ 6-10min.

How to boot back up: (Otherwise the power led just blink's slowly. Or not blink at all)

From here the only way to start this 500e back up is either a combo of:
1. "ESC" + "Refresh" + "Power button" for 2 seconds to boot to recovery mode.
2. From Recovery mode: "Refresh" + "Power for ~2 seconds to "Hard Reset"

Upon boot you are greeted with the "Restore pages?, chrome didn't shut down correctly."

Other info:
Shutdown: (Shutdown/Close Lid/Open lid works.)
1. start up from cold power off with power button.
2. shutdown via the "shutdown" button/logo on the login screen.
3. Close Lid.
4. Wait a few seconds.
5. Open Lid.
6. Device powers on and were good.

I will probably end up returning this one as the 2 are for my kiddos and, I can see the complaints from mom already happening :(

I'm see this behavior again on M71 beta, although alt+volup+x does not fix the issue. No crashes in chrome:crashes yet, I will let you know if I find anything