New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 689654 link

Starred by 2 users
Status: WontFix
Owner:
dbasehore@chromium.org
Closed: Mar 2017
Cc:
snanda@chromium.org
diand...@chromium.org
█ sha...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

kevin sometimes fails to resume after suspending

Project Member Reported by derat@chromium.org, Feb 7 2017 
Chrome Version: 56.0.2924.87
OS Version: 9000.82.0

My PVT3 kevin device failed to resume after suspending.

I closed the lid at 10:24:29, and powerd ran powerd_suspend at 10:24:31. When I opened the lid around 12:05, the LED on the right side was blue but the screen stayed black. The system powered off after I held the power button for eight seconds, and it booted when I opened the lid again a few minutes later. Chrome displayed a message that it had crashed when I logged in.

I don't see any clues in /var/log/messages:

2017-02-07T10:24:29.490889-08:00 INFO session_manager[1398]: [INFO:session_manager_impl.cc(577)] LockScreen() method called.
2017-02-07T10:24:30.639864-08:00 INFO session_manager[1398]: [INFO:session_manager_impl.cc(581)] HandleLockScreenShown() method called.
2017-02-07T10:24:30.640330-08:00 INFO session_manager[1398]: [INFO:session_manager_impl.cc(577)] LockScreen() method called.
2017-02-07T10:24:31.552690-08:00 NOTICE powerd_suspend[6433]: Going to suspend-to-RAM state: args=--suspend_duration=-1 --nosuspend_to_idle --wakeup_count=106
2017-02-07T10:24:31.756199-08:00 NOTICE powerd_suspend[6485]: Explicit sync
2017-02-07T10:24:32.416372-08:00 NOTICE powerd_suspend[6489]: Finalizing suspend
2017-02-07T10:24:32.423210-08:00 INFO kernel: [  809.844324] PM: suspend entry 2017-02-07 18:24:32.422456376 UTC
2017-02-07T12:12:22.254505-08:00 INFO kernel: imklog 5.8.11, log source = /proc/kmsg started.
2017-02-07T12:12:22.254627-08:00 INFO rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="653" x-info="http://www.rsyslog.com"] start

I filed a feedback report at http://feedback/#/Report/52867022246. (The description there is a bit off; I must've forgotten that I just suspended instead of shutting down earlier.)

I think I've seen this a few times with the same device.

Comment 1 by tbroch@chromium.org, Mar 2 2017

Cc: dbasehore@chromium.org diand...@chromium.org
Agreed I can't surface anything that looks suspect before suspend and only see these on subsequent reboot:

2017-02-07T12:12:26.290617-08:00 WARNING crash_reporter[2385]: Last shutdown was not clean
2017-02-07T12:12:26.290653-08:00 INFO crash_reporter[2385]: Unclean shutdown occurred while suspended. Not counting toward unclean shutdown statistic.

+Doug, Derek for further triage

Comment 2 by tbroch@chromium.org, Mar 2 2017

Cc: -dbasehore@chromium.org
Owner: dbasehore@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by diand...@chromium.org, Mar 3 2017

Status: WontFix (was: Assigned)
Going to be really hard without ramoops.  The ideal reboot steps are in <https://sites.google.com/a/google.com/test-chrome-os-operations/chrome?pli=1>, but in the very least restarting with Alt-TopRowKeyboardVolup-R is the right way to reboot while preserving logs.  If you file feedback after such a reboot it will have the console-ramoops and will be actionable.

That being said 9000.82.0 (or specifically BIOS 8785.144.0) had a major problem with suspend resume on some boards.  See <https://b.corp.google.com/issues/35647800> for some details.  This has since been fixed.


Hard to say whether to close it as Duplicate of the other bug or as WontFix (not enough info to really confirm), but it doesn't terribly matter.
►

Sign in to add a comment