Kernel crash when resuming samus in docked mode |
||||||
Issue descriptionVersion: 55.0.2883.42 beta 8872.44.0 (Official Build) beta-channel samus OS: Chrome What steps will reproduce the problem? (1) Connect an external display, keyboard, power, & mouse. (2) Close the laptop to enter docked mode. (3) Lock the screen (4) Leave the device over night (5) Touch the keyboard or move mouse to wake What is the expected result? Chrome OS's really-superfantabulastic instant wake time. What happens instead? Nothing. Mouse and keyboard do nothing. Need to open the device and wait for a really long time (10+s maybe longer. Seems longer than a normal boot.) before getting back to a lock screen. Please use labels and text to provide additional information.
,
Nov 18 2016
Will do. Tends to take overnight to happen. I'll grab a report post-turkey-day. Thanks.
,
Nov 19 2016
Oh, just read a bit more carefully. The title says "... seems to shut down", but the "What happens instead?" section says "... before getting back to a lock screen." Are you getting the lock screen (i.e. system didn't shut down) or the login screen?
,
Nov 22 2016
,
Nov 28 2016
https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=user:abodenha@google.com&lReport=17845083817 Just happened again. I paid closer attention this time: 0: Be using a samus in docked mode with multiprofile 1: lock device. 2: Got to lunch. 3: Come back Mouse wont wake device Keyboard wont wake device Opening lid wont wake device Hitting power button wakes. Lock screen comes up. Device crashes and returns to start screen. Sign in and see "chrome didn't shut down correctly" Crash id is crash/ab3fd12300000000 which looks like a kernel hang.
,
Nov 29 2016
Over to Sameer for triage. Lid-open not waking seems bizarre.
,
Nov 29 2016
,
Nov 19
Closing due to lack of activity. Please reopen if still relevant. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by derat@chromium.org
, Nov 18 2016Owner: derat@chromium.org