BTW, I tried on stable, beta, and dev channel, all three of them have the same behavior. And also I've switched between developer mode on/off multiple times and confirmed that this issue ONLY happens when developer mode is enabled.

Can't reproduce on my machine.
Can you file feedback with alt-shift-i when this happen?

> [0115/194306.241631:INFO:daemon.cc(545)] Reading wakeup count from /sys/power/wakeup_count
> [0115/194306.241664:INFO:daemon.cc(549)] Read wakeup count 26237
There is probably something spamming the request to wake up. The wakeup_count normally won't exceed 100.

content of these would be useful too.
/sys/kernel/debug/wakeup_sources
/sys/kernel/debug/pmc_core/last_wake_source

Yes indeed, it does seem like something is spamming the wake up requests.
The issue happens when the screen is off (idling), how do I file feedback with alt-shift-i in this case?

Attached /sys/kernel/debug/wakeup_sources, /sys/kernel/debug/pmc_core/last_wake_source is empty

Deleted: wakeup_sources 2.5 KB

wakeup_sources 2.5 KB View Download

Do you have any updates on this? Could this be a hardware issue? I was leaning towards not because it only happens in developer mode, however the fact that you cannot reproduce it makes me wonder whether I should request for a replacement unit.

The /sys/kernel/debug/wakeup_sources does not have enough info for me to know it for sure.

Also did you have any USB device plugged in? If yes, does the issue still happen after remove all USB device?
The 20K wake count device is deleted. 

To get more log can you run powerd_dbus_suspend, abort it in the middle and do alt-shift-i and mention crbug.com/922307 in the message?

> Could this be a hardware issue?
probably not. If it is HW issue then it should fail in verify mode too.

Feedback sent with crbug.com/922307 mentioned in the message.

No USB devices was ever plugged in, the only accessory used is the official Pixel Slate Keyboard to access the terminal. For some reason an unknown 'deleted' device is spamming wakes.

For the record, I've tested on freshly powerwashed guest mode (so no apps, no settings are migrated), the issue still persists so I'm pretty sure this isn't an user issue.

Thank you for the feedback report. I think I found the cause.

- We tried to enter s0ix but slp_s0_count didn't increase so we bailed out
- powergate status shows usb-otg keeps us from entering s0ix. 
Note that USB-OTG powergate is off on my DVT nocturne.

Benson / Aseda / Todd, is this a known issue?


Relevant log below. The feedback is at https://listnr.corp.google.com/report/85912148875
[  681.288483] PM: noirq suspend of devices complete after 36.632 msecs
[  681.288486] PM: suspend-to-idle
[  686.289410] PC10 residency : 
               Prev : 0xe3d68fb00
               New : 0x101a39c2c0
[  686.289413] ------------[ cut here ]------------
[  686.289425] WARNING: CPU: 0 PID: 0 at ../../../../../tmp/portage/sys-kernel/chromeos-kernel-4_4-4.4.169-r1781/work/chromeos-kernel-4_4-4.4.169/drivers/idle/intel_idle.c:863 intel_idle_freeze_and_check+0x209/0x215
[  686.289426] CPU did not enter SLP S0 for suspend-to-idle.
[  686.289483] Modules linked in: algif_hash algif_skcipher af_alg veth esp6 ah6 xfrm6_mode_tunnel xfrm6_mode_transport xfrm4_mode_tunnel xfrm4_mode_transport nf_nat_tftp nf_conntrack_tftp nf_nat_ftp nf_conntrack_ftp ip6t_REJECT nf_reject_ipv6 ip6t_ipv6header ccm rfcomm cmac uinput snd_soc_kbl_da7219_max98373 snd_soc_da7219 snd_soc_hdac_hdmi snd_soc_skl_ssp_clk snd_soc_dmic dwc3 udc_core snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_sst_match snd_hda_ext_core snd_hda_core snd_seq_dummy snd_seq zram ipu3_imgu snd_seq_device ipu3_cio2 iova videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videobuf2_core dwc3_pci imx355 snd_soc_max98373 at24 sx9310 imx319 acpi_als v4l2_fwnode ak7375 bridge stp llc ipt_MASQUERADE nf_nat_masquerade_ipv4 fuse xt_mark iio_trig_sysfs cros_ec_light_prox
[  686.289502]  cros_ec_sensors_sync cros_ec_sensors_ring cros_ec_sensors cros_ec_sensors_core industrialio_triggered_buffer kfifo_buf industrialio ip6table_filter iwlmvm iwlwifi iwl7000_mac80211 cfg80211 btusb btrtl btbcm btintel hid_google_whiskers hid_google_hammer bluetooth joydev
[  686.289507] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.4.169-15632-g1b3234013807 #1
[  686.289509] Hardware name: Google Nocturne/Nocturne, BIOS Google_Nocturne.10984.78.0 12/21/2018
[  686.289514]  ffffffffa061977c b4d26275892e3cf1 ffffffffa0803d98 ffffffff9ff26e20
[  686.289518]  ffffffffa0803dd0 ffffffff9ff26dd2 b4d26275892e3cf1 ffffffffa0803e60
[  686.289522]  0000000000000082 b4d26275892e3cf1 ffffffffa0803e60 ffffffffa0803e10
[  686.289523] Call Trace:
[  686.289530]  [<ffffffff9ff26e20>] __dump_stack+0x19/0x1b
[  686.289532]  [<ffffffff9ff26dd2>] dump_stack+0x4f/0x84
[  686.289536]  [<ffffffff9fcb685d>] __warn+0xba/0xee
[  686.289539]  [<ffffffff9fcb68f0>] warn_slowpath_fmt+0x5f/0x79
[  686.289543]  [<ffffffff9fced71e>] ? printk+0x62/0x7c
[  686.289547]  [<ffffffff9fd05b41>] ? clockevents_switch_state+0x1b/0x4f
[  686.289552]  [<ffffffff9ff87f58>] intel_idle_freeze_and_check+0x209/0x215
[  686.289557]  [<ffffffffa02052a1>] cpuidle_enter_freeze+0x63/0xc4
[  686.289561]  [<ffffffff9fd6f29b>] cpu_startup_entry+0x1f5/0x296
[  686.289566]  [<ffffffffa03dfd0c>] rest_init+0x83/0x86
[  686.289569]  [<ffffffffa0922ca4>] start_kernel+0x41d/0x48f
[  686.289572]  [<ffffffffa0922d16>] ? start_kernel+0x48f/0x48f
[  686.289576]  [<ffffffffa09225ec>] x86_64_start_reservations+0x30/0x32
[  686.289578]  [<ffffffffa09224ba>] x86_64_start_kernel+0xf0/0xf5
[  686.289580] ---[ end trace e16bc911969b9015 ]---
[  686.289596] PCH IP: 0  - PMC                             	State: On
[  686.289598] PCH IP: 1  - OPI-DMI                         	State: On
[  686.289599] PCH IP: 2  - SPI / eSPI                      	State: On
[  686.289600] PCH IP: 3  - XHCI                            	State: On
[  686.289602] PCH IP: 4  - SPA                             	State: Off
[  686.289603] PCH IP: 5  - SPB                             	State: Off
[  686.289605] PCH IP: 6  - SPC                             	State: Off
[  686.289606] PCH IP: 7  - GBE                             	State: Off
[  686.289607] PCH IP: 8  - SATA                            	State: Off
[  686.289609] PCH IP: 9  - HDA-PGD0                        	State: Off
[  686.289610] PCH IP: 10 - HDA-PGD1                        	State: Off
[  686.289611] PCH IP: 11 - HDA-PGD2                        	State: Off
[  686.289612] PCH IP: 12 - HDA-PGD3                        	State: Off
[  686.289614] PCH IP: 13 - RSVD                            	State: Off
[  686.289615] PCH IP: 14 - LPSS                            	State: Off
[  686.289616] PCH IP: 15 - LPC                             	State: Off
[  686.289618] PCH IP: 16 - SMB                             	State: Off
[  686.289619] PCH IP: 17 - ISH                             	State: Off
[  686.289620] PCH IP: 18 - P2SB                            	State: Off
[  686.289621] PCH IP: 19 - DFX                             	State: Off
[  686.289623] PCH IP: 20 - SCC                             	State: Off
[  686.289624] PCH IP: 21 - RSVD                            	State: Off
[  686.289625] PCH IP: 22 - FUSE                            	State: On
[  686.289627] PCH IP: 23 - CAMERA                          	State: Off
[  686.289628] PCH IP: 24 - RSVD                            	State: Off
[  686.289629] PCH IP: 25 - USB3-OTG                        	State: On
[  686.289631] PCH IP: 26 - EXI                             	State: Off
[  686.289632] PCH IP: 27 - CSE                             	State: Off
[  686.289633] PCH IP: 28 - CSME_KVM                        	State: Off
[  686.289634] PCH IP: 29 - CSME_PMT                        	State: Off
[  686.289636] PCH IP: 30 - CSME_CLINK                      	State: Off
[  686.289637] PCH IP: 31 - CSME_PTIO                       	State: Off
[  686.289638] PCH IP: 32 - CSME_USBR                       	State: Off
[  686.289640] PCH IP: 33 - CSME_SUSRAM                     	State: Off
[  686.289641] PCH IP: 34 - CSME_SMT                        	State: Off
[  686.289642] PCH IP: 35 - RSVD                            	State: Off
[  686.289643] PCH IP: 36 - CSME_SMS2                       	State: Off
[  686.289645] PCH IP: 37 - CSME_SMS1                       	State: Off
[  686.289646] PCH IP: 38 - CSME_RTC                        	State: Off
[  686.289647] PCH IP: 39 - CSME_PSF                        	State: Off
[  686.289874] PM: resume from suspend-to-idle

Did something change in M73 where we enabled the usb gadget controller?

From that feedback report, I don't see anything plugged into the USB ports, therefore the USB_ID and VBUS sense pins shouldn't be asserted.

comment #1 said this happen in all stable, beta, and dev channel.

So probably not M73 specific.

Does anyone have an update on this? I apologize for constantly bumping this issue, but the device is basically unusable in this state. 

I found this post with a similar issue: https://support.google.com/pixelslate/thread/667542?hl=en.
The user resolved the issue with a hardware replacement. But my case is a little more bizarre because it only happens with verify off (which make no sense to me...)

I wonder if some faulty USB hardware kept spamming wake requests, but this doesn't explain why it only happens in developer mode. I really hope this can be resolved because I cannot use my brand new device.

topjohnwu:

I'll try to reproduce it. Please wait.

Thus far unable to reproduce the issue. I have two systems on M73 that are reliably entering S0iX and staying there.