Update for the following overnight suspend: worked correctly with a suspend of around 8 hours.
No significant changes in hardware configuration or kernel options (added "initcall_debug"). I did install 'uswsusp' to support hibernation in addition to S3 suspend and modified '/etc/initramfs-tools/conf.d/resume' to be "RESUME=/dev/mapper/cryptsetup1" as well as converting the partition used for swap to LUKS (with key-file and passphrase) - it had the original base-installer's plain dm_crypt configuration. Hibernation works correctly. Hopefully this was issue was a one-off event. I'll continue monitoring and update this bug report as appropriate. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1576571 Title: S3 suspend resume cycle every 30 minutes Status in linux package in Ubuntu: Confirmed Bug description: 16.04 amd64 on an Asus T300 CHI. I commanded the PC to S3 suspend around 21:30 last evening. Returned to the PC around 08:00 this morning and discovered the PC wouldn't resume from suspend and had fully discharged its battery. After a cold boot restart I investigated the logs and noticed that overnight the PC appears to have been in a cycle of suspend/resume every 30 minutes until around 06:49 when it wrote a hibernation image, suspended, woke, and ran out of power. Due to the timestamps in kern.log not being accurate (some resume messages are timestamped with the suspend time until the system clock is corrected) its proving hard to understand the precise sequence of events, and even whether the PC truly did go into S3 suspend. The battery was fully charged before the PC was commanded to suspend and when running idle should last ~6 hours or more. I wondered about some ACPI interrupts waking it up but it has very few devices that might do that. It has a single USB3 port and no device was connected. It only has an iwlwifi PCI network device (no wired Ethernet). ethtool indicates there is no WoL for the WiFi adapter. It only has a Bluetooth connected keyboard so there is no possibility of a keyboard wakeup. It has a touchscreen digitizer but nothing entered the room during the night an there are no secret stray cats, or mice! It does have IIO sensors for ambient light and accelerometer but there is currently no software accessing them although the kernel drivers are loaded. $ grep -Ea 'PM: (Prepar|Finish)' kern.log Apr 28 21:36:54 T300CHI kernel: [82469.274147] PM: Preparing system for sleep (mem) Apr 28 21:36:54 T300CHI kernel: [82471.096890] PM: Finishing wakeup. Apr 28 21:37:31 T300CHI kernel: [82507.808915] PM: Preparing system for sleep (mem) Apr 28 21:37:35 T300CHI kernel: [82509.203304] PM: Finishing wakeup. Apr 28 22:07:45 T300CHI kernel: [84319.706320] PM: Preparing system for sleep (mem) Apr 28 22:07:49 T300CHI kernel: [84321.104263] PM: Finishing wakeup. Apr 28 22:38:01 T300CHI kernel: [86131.634214] PM: Preparing system for sleep (mem) Apr 28 22:38:04 T300CHI kernel: [86133.021188] PM: Finishing wakeup. Apr 28 23:08:19 T300CHI kernel: [87943.507350] PM: Preparing system for sleep (mem) Apr 28 23:08:19 T300CHI kernel: [87944.923894] PM: Finishing wakeup. Apr 28 23:38:34 T300CHI kernel: [89755.366961] PM: Preparing system for sleep (mem) Apr 28 23:38:34 T300CHI kernel: [89756.786890] PM: Finishing wakeup. Apr 29 00:08:48 T300CHI kernel: [91567.020044] PM: Preparing system for sleep (mem) Apr 29 00:08:48 T300CHI kernel: [91568.436456] PM: Finishing wakeup. Apr 29 00:38:59 T300CHI kernel: [93378.844871] PM: Preparing system for sleep (mem) Apr 29 00:39:03 T300CHI kernel: [93380.256574] PM: Finishing wakeup. Apr 29 01:09:13 T300CHI kernel: [95190.641618] PM: Preparing system for sleep (mem) Apr 29 01:09:17 T300CHI kernel: [95192.030272] PM: Finishing wakeup. Apr 29 01:39:28 T300CHI kernel: [97002.442841] PM: Preparing system for sleep (mem) Apr 29 01:39:32 T300CHI kernel: [97003.826499] PM: Finishing wakeup. Apr 29 02:09:42 T300CHI kernel: [98814.281002] PM: Preparing system for sleep (mem) Apr 29 02:09:46 T300CHI kernel: [98815.670863] PM: Finishing wakeup. Apr 29 02:40:01 T300CHI kernel: [100626.106115] PM: Preparing system for sleep (mem) Apr 29 02:40:01 T300CHI kernel: [100627.499669] PM: Finishing wakeup. Apr 29 03:10:11 T300CHI kernel: [102437.773451] PM: Preparing system for sleep (mem) Apr 29 03:10:15 T300CHI kernel: [102439.159921] PM: Finishing wakeup. Apr 29 03:40:30 T300CHI kernel: [104249.563211] PM: Preparing system for sleep (mem) Apr 29 03:40:30 T300CHI kernel: [104250.977264] PM: Finishing wakeup. Apr 29 04:10:44 T300CHI kernel: [106061.409233] PM: Preparing system for sleep (mem) Apr 29 04:10:44 T300CHI kernel: [106062.798963] PM: Finishing wakeup. Apr 29 04:40:59 T300CHI kernel: [107873.214783] PM: Preparing system for sleep (mem) Apr 29 04:40:59 T300CHI kernel: [107874.612422] PM: Finishing wakeup. Apr 29 05:11:09 T300CHI kernel: [109684.937138] PM: Preparing system for sleep (mem) Apr 29 05:11:13 T300CHI kernel: [109686.330386] PM: Finishing wakeup. Apr 29 05:41:28 T300CHI kernel: [111496.747318] PM: Preparing system for sleep (mem) Apr 29 05:41:28 T300CHI kernel: [111498.140735] PM: Finishing wakeup. Apr 29 06:11:29 T300CHI kernel: [113298.690266] PM: Preparing system for sleep (mem) Apr 29 06:11:33 T300CHI kernel: [113300.102234] PM: Finishing wakeup. Apr 29 06:41:34 T300CHI kernel: [115101.410436] PM: Preparing system for sleep (mem) Apr 29 06:41:38 T300CHI kernel: [115102.820245] PM: Finishing wakeup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
