Issue metadata
Sign in to add a comment
|
veyron_(mickey|minnie): Suspend repeatedly fails due to wake events from gpio-keys.11 |
||||||||||||||||||||||||
Issue descriptionSeeing a trend in reports from users that when their Chromebooks go to sleep mode from lid close or idle, they actually shut down instead. When they resume, it's like turning the Chromebook back on after a full shut down. The majority of these reports are tracked here: https://pulse.corp.google.com/#/feedbackneutron?base_params=18g64jkm Of 17 reports on M64 Beta in the past 28 days, 11 were from Veyron_minnie. Also reported on Veyron_speedy, Fizz, Kevin, and Link Sleep Mode causes shutdown - Sample Reports - https://listnr.corp.google.com/report/84853085642 - https://listnr.corp.google.com/report/84937102624 May be related --> Reports about Inability to wake from Sleep: - https://listnr.corp.google.com/report/84955233540 - https://listnr.corp.google.com/report/84969198527 Not sure if this is somehow related to https://crbug.com/803727
,
Jan 25 2018
The device is a volumeup/volumedown, powerbtn. Not sure why we are seeing spurious wakes .
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "gpio-keys.11"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 114 (KEY_VOLUMEDOWN)
Event code 115 (KEY_VOLUMEUP)
Event code 116 (KEY_POWER)
Event type 5 (EV_SW)
Event code 0 (SW_LID)
,
Jan 25 2018
Flashed the latest release to see if this can be reproduced. No luck.
CHROMEOS_RELEASE_APPID={432FF9F1-4D2E-7E74-6F98-32E56E904BFB}
CHROMEOS_BOARD_APPID={432FF9F1-4D2E-7E74-6F98-32E56E904BFB}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
DEVICETYPE=CHROMEBOOK
CHROMEOS_ARC_VERSION=4564826
CHROMEOS_ARC_ANDROID_SDK_VERSION=25
GOOGLE_RELEASE=10176.61.0
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_BUILDER_PATH=veyron_minnie-release/R64-10176.61.0
CHROMEOS_RELEASE_BUILD_NUMBER=10176
CHROMEOS_RELEASE_BRANCH_NUMBER=61
CHROMEOS_RELEASE_CHROME_MILESTONE=64
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=testimage-channel
CHROMEOS_RELEASE_DESCRIPTION=10176.61.0 (Official Build) dev-channel veyron_minnie test
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_BOARD=veyron_minnie
CHROMEOS_RELEASE_VERSION=10176.61.0
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
Might be the button is stuck or the device is rested on the side (resulting in the button press) ?
,
Jan 25 2018
First occurrence I can find in lab (mickey) is here: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/testDetails?testName=power_Resume.SuspendToRam&suite=power_build&daysBack=30&board=veyron_mickey&architecture=&boardFamily=&buildConfig=&reason=&version=&milestone=&dut= failing: 10176.28.0 https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/165606724-chromeos-test/chromeos4-row3-rack11-host3 And its still failing on 10339.0.0 passing: 10032.86.0
,
Jan 25 2018
,
Jan 25 2018
,
Jan 26 2018
Interesting observation.. the issue is not reproducible if there is no user signed in. But reproducible when the user is signed in.
,
Jan 26 2018
Turns out it is the Bluetooth. Veyron uses the gpio-keys to report bluetooth wakeup as well as power-btn wakeup. https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.14/arch/arm/boot/dts/rk3288-veyron.dtsi#42 Verified this by turning the Bluetooth off and the issue goes away. Turning the bluetooth on will cause the suspend to fail again.
,
Jan 26 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by derat@chromium.org
, Jan 25 2018Labels: -Type-Bug -Pri-2 M-65 ReleaseBlock-Stable Pri-1 Type-Bug-Regression
Status: Untriaged (was: Unconfirmed)
Summary: Suspend repeatedly fails due to wake events from gpio-keys.11 (was: Users report that Sleep Mode causes shutdown)