Public bug reported:
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.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "kern.log starting from a cold boot just before commanded
suspend"
https://bugs.launchpad.net/bugs/1576571/+attachment/4651152/+files/kern.log
--
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:
New
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.
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
