Issue metadata
Sign in to add a comment
|
minnie: Suspend repeatedly fails due to wake events from gpio-keys.11 |
||||||||||||||||||||||||
Issue descriptionGoogle Chrome 64.0.3282.144 (Official Build) (32-bit) Revision 0 Platform 10176.68.0 (Official Build) stable-channel veyron_minnie What steps will reproduce the problem? (1) Leave the device idle for few minutes. (2) Device should go to suspend mode (3) Try to wake the device by clicking on touchpad or keyboard What is the expected result? Display should turn on. What happens instead? Nothing happens. Display remains off. On closing the lid and opening it again, device reboots. This issue is similar to the repro steps of crbug.com/773421 on chell device
,
Feb 6 2018
,
Feb 6 2018
I don't know what minnie's eventlog usually looks like, but this seems pretty weird: ... 160 | 2018-02-03 17:12:38 | System boot | 0 161 | 2018-02-03 17:12:38 | Chrome OS Developer Mode 162 | 2018-02-03 17:13:10 | System boot | 0 163 | 2018-02-03 17:13:10 | Chrome OS Developer Mode 164 | 2018-02-05 17:20:22 | Sleep 165 | 2018-02-05 17:20:23 | Wake 166 | 2018-02-05 17:20:23 | Sleep 167 | 2018-02-05 17:20:24 | Sleep 168 | 2018-02-05 17:20:24 | Wake 169 | 2018-02-05 17:20:24 | Wake 170 | 2018-02-05 17:20:25 | Sleep 171 | 2018-02-05 17:20:25 | Wake 172 | 2018-02-05 17:20:26 | Sleep 173 | 2018-02-05 17:20:27 | Wake 174 | 2018-02-05 17:20:27 | Sleep 175 | 2018-02-05 17:20:28 | Wake 176 | 2018-02-05 17:20:28 | Wake 177 | 2018-02-05 17:20:29 | Sleep 178 | 2018-02-05 17:20:29 | Sleep 179 | 2018-02-05 17:20:30 | Wake 180 | 2018-02-05 17:20:30 | Wake 181 | 2018-02-05 17:20:30 | Sleep 182 | 2018-02-05 17:20:31 | Sleep 183 | 2018-02-05 17:20:31 | Wake 184 | 2018-02-05 17:20:32 | Wake 185 | 2018-02-03 17:24:06 | System boot | 0 186 | 2018-02-03 17:24:06 | Chrome OS Developer Mode Here's the end of the second-to-last powerd log: [0205/172028:INFO:daemon.cc(599)] Read wakeup count 47 \... [0205/172029:INFO:main.cc(244)] Running "/usr/bin/powerd_setuid_helper --action=suspend --suspend_wakeup_count_valid --suspend_wakeup_count=47" ... [0205/172029:INFO:daemon.cc(687)] powerd_suspend returned 2 ... [0205/172029:WARNING:suspender.cc(544)] Suspend attempt #8 canceled due to wake event ... [0205/172029:INFO:daemon.cc(599)] Read wakeup count 48 ... [0205/172030:INFO:main.cc(244)] Running "/usr/bin/powerd_setuid_helper --action=suspend --suspend_wakeup_count_valid --suspend_wakeup_count=48" ... [0205/172030:INFO:daemon.cc(687)] powerd_suspend returned 3 ... [0205/172030:WARNING:suspender.cc(544)] Suspend attempt #9 canceled due to wake event ... [0205/172030:INFO:daemon.cc(599)] Read wakeup count 49 ... [0205/172031:INFO:main.cc(244)] Running "/usr/bin/powerd_setuid_helper --action=suspend --suspend_wakeup_count_valid --suspend_wakeup_count=49" ... [0205/172031:INFO:daemon.cc(687)] powerd_suspend returned 2 ... [0205/172031:WARNING:suspender.cc(544)] Suspend attempt #10 canceled due to wake event ... [0205/172031:INFO:daemon.cc(599)] Read wakeup count 50 ... [0205/172031:INFO:main.cc(244)] Running "/usr/bin/powerd_setuid_helper --action=suspend --suspend_wakeup_count_valid --suspend_wakeup_count=50" ... [0205/172032:INFO:daemon.cc(687)] powerd_suspend returned 3 ... [0205/172032:ERROR:suspender.cc(572)] Unsuccessfully attempted to suspend 11 times; shutting down [0205/172032:INFO:daemon.cc(1564)] Postponing shutdown for lockfile(s): /run/lock/flashrom_powerd.lock ... [0205/172037:INFO:daemon.cc(1590)] Shutting down, reason: suspend-failed ... And from messages: 2018-02-05T17:20:24.009865-08:00 INFO kernel: [ 430.640264] last active wakeup source: gpio-keys.11 So I think this is issue 800998 . |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sdantul...@chromium.org
, Feb 6 2018