Unexpected reboot after logging out when in dock mode.
Reported by
kamil.ch...@displaylink.com,
Mar 24 2017
|
|||
Issue descriptionChrome Version: 58.0.3029.31 dev-channel Chrome OS Version: 58.0.3029.31 dev-channel Chrome OS Platform: 9334.18.0 dev-channel chell Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1) Connect UDL2 with monitor attached and mouse to Chromebook. (2) Close lid. (3) Log out user. Expected Result: Log in screen should be shown to the user. Actual Result: Monitor is blank. After opening lid machine restart. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) sometimes - 75% What is the impact to the user, and is there a workaround? If so, what is it? No workaround. Please provide any additional information below. Attach a screen shot or log if possible. Console ramoops file under /dev/pstore is not created. Issue is also affecting UDL3 devices. Issue is also reproducible on stable channel 57.0.2987.123. Issue is also reproducible on asuka chromebook. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Jun 1 2017
If we can get logs, whatever happened at the end of messages, or the eventlog.txt might have some indication of what went wrong. about://net-internals has a Chrome OS section with a store debug logs button, which should put a tar file in your downloads folder, this should contain just about everything we can get off the device for analysis.
,
Jun 1 2017
Able to repro with UDL3 monitor & Chell device with version 60.0.3112.10/9592.3.0 dev-channel Observations: 1. Once log out from UDL3 monitor, log in screen displays for a second and goes blank. 2. Opened chromebook lid and see the device rebooting 3. Collected logs after reboot (not sure how much info it has) Logs here: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/704908/
,
Jun 2 2017
We are panicing: ... 250 | 2017-06-01 16:36:16 | System Reset 251 | 2017-06-01 16:36:16 | Chrome OS Developer Mode 252 | 2017-06-01 16:36:50 | Kernel Event | Oops 253 | 2017-06-01 16:36:50 | Kernel Event | Panic 254 | 2017-06-01 16:36:52 | System boot | 235 255 | 2017-06-01 16:36:52 | System Reset 256 | 2017-06-01 16:36:52 | Log area cleared | 1027 257 | 2017-06-01 16:36:52 | Chrome OS Developer Mode 258 | 2017-06-01 16:37:29 | Kernel Event | Oops 259 | 2017-06-01 16:37:29 | Kernel Event | Panic 260 | 2017-06-01 16:37:31 | System boot | 236 261 | 2017-06-01 16:37:31 | System Reset 262 | 2017-06-01 16:37:31 | Chrome OS Developer Mode 263 | 2017-06-01 16:41:10 | Kernel Event | Clean Shutdown 264 | 2017-06-01 16:41:11 | ACPI Enter | S5 265 | 2017-06-01 16:41:26 | System boot | 237 ... Unfortunately messages does not contain anything regarding the panic, so we probably need the /dev/pstore/ramoops. Prasanthi, is there any chance in your repro that you happened to have a /dev/pstore entry? If that is not getting generated this may be a bit trickier, e.g. enabling UART and using a servo to try to grab the kernel panic messages. |
|||
►
Sign in to add a comment |
|||
Comment 1 by bhthompson@google.com
, Jun 1 2017Components: OS>Kernel>Graphics