Suspend doesn't work when laptop is below 5%

SuperZanti · 2015-05-25 20:55:58

I"m having a very strange issue where when I suspend my laptop and the battery is below 5% it wakes back up immediately. It then promptly goes back to suspend, wakes up immediately, and infinitely continues this cycle until the battery is dead or I plug in the charger. Another weird thing is that after this happens (and again only when the battery is below 5% meaning 0,1,2,3 or 4 percent), is that the fan speeds up and becomes really loud. It stays this way. If I plug in my charger it stays the same, if I do a 'sudo reboot' it also stays the same. I have to completely power off the machine and turn it back on to get the fan back to normal.

This doesn't happen if the battery is over 5%. Only if it's under.

I don't have upower, pm-utils, or even laptop-mode-tools. I use acpi to check if my laptop lid is closed to suspend, and I manage mostly everything with udev events using a modified version of ftw (for the watts).

This is the output of cat /proc/acpi/wakeup

cat /proc/acpi/wakeup
Device	S-state	  Status   Sysfs node
P0P1	  S4	*disabled
PEG0	  S4	*disabled  pci:0000:00:01.0
PEG1	  S4	*disabled
PEG2	  S4	*disabled
PEG3	  S4	*disabled
USB1	  S3	*disabled
USB2	  S3	*disabled
USB3	  S3	*disabled
USB4	  S3	*disabled
EHC2	  S3	*disabled  pci:0000:00:1a.0
USB5	  S3	*disabled
USB6	  S3	*disabled
USB7	  S3	*disabled
HDEF	  S4	*disabled  pci:0000:00:1b.0
RP01	  S4	*disabled  pci:0000:00:1c.0
RP03	  S4	*disabled
RP04	  S4	*disabled
RP05	  S4	*disabled
RP06	  S4	*disabled
RP07	  S4	*disabled
RP08	  S4	*disabled
RP02	  S4	*disabled  pci:0000:00:1c.1
WLAN	  S3	*disabled  pci:0000:03:00.0
EHC1	  S3	*disabled  pci:0000:00:1d.0
XHC1	  S3	*disabled  pci:0000:00:14.0
XHC	  S3	*disabled
SLPB	  S4	*disabled  platform:PNP0C0E:00

So everything is disabled to my knowledge. However it seems this may have changed in newer revisions of the linux kernel?

Here is my journalctl around the time the event occured:

-- Reboot --
May 25 14:34:59 Chell systemd[418]: Unit type .busname is not supported on this system.
May 25 14:34:59 Chell systemd[418]: Reached target Paths.
May 25 14:34:59 Chell systemd[418]: Starting Paths.
May 25 14:34:59 Chell systemd[418]: Reached target Timers.
May 25 14:34:59 Chell systemd[418]: Starting Timers.
May 25 14:34:59 Chell systemd[418]: Reached target Sockets.
May 25 14:34:59 Chell systemd[418]: Starting Sockets.
May 25 14:34:59 Chell systemd[418]: Reached target Basic System.
May 25 14:34:59 Chell systemd[418]: Starting Basic System.
May 25 14:34:59 Chell systemd[418]: Reached target Default.
May 25 14:34:59 Chell systemd[418]: Startup finished in 10ms.
May 25 14:34:59 Chell systemd[418]: Starting Default.
May 25 14:35:00 Chell org.a11y.Bus[501]: Activating service name='org.a11y.atspi.Registry'
May 25 14:35:00 Chell org.a11y.Bus[501]: Successfully activated service 'org.a11y.atspi.Registry'
May 25 14:35:00 Chell org.a11y.atspi.Registry[568]: SpiRegistry daemon is running with well-known name - o
May 25 14:42:26 Chell systemd[418]: Time has been changed
May 25 14:45:44 Chell systemd[418]: Time has been changed
May 25 14:58:51 Chell systemd[418]: Time has been changed
May 25 14:59:27 Chell systemd[418]: Time has been changed
May 25 15:07:09 Chell systemd[418]: Time has been changed
May 25 15:09:32 Chell systemd[418]: Time has been changed
May 25 15:14:13 Chell systemd[418]: Time has been changed
May 25 15:17:57 Chell systemd[418]: Time has been changed
May 25 15:18:11 Chell systemd[418]: Time has been changed
May 25 15:28:24 Chell systemd[418]: Time has been changed
May 25 15:30:53 Chell systemd[418]: Time has been changed
May 25 15:32:05 Chell systemd[418]: Time has been changed
May 25 15:32:35 Chell systemd[418]: Time has been changed
May 25 15:32:58 Chell systemd[418]: Time has been changed
May 25 15:33:14 Chell systemd[418]: Time has been changed
May 25 15:33:30 Chell systemd[418]: Time has been changed

and finally dmesg:

May 25 15:37:41 Chell systemd[418]: Stopping Timers.
May 25 15:37:41 Chell systemd[418]: Stopped target Sockets.
May 25 15:37:41 Chell systemd[418]: Stopping Sockets.
May 25 15:37:41 Chell systemd[418]: Stopped target Paths.
May 25 15:37:41 Chell systemd[418]: Stopping Paths.
May 25 15:37:41 Chell systemd[418]: Received SIGRTMIN+24 from PID 7567 (kill).
May 25 15:37:41 Chell systemd[421]: pam_unix(systemd-user:session): session closed for user seth
May 25 15:37:53 Chell systemd[416]: Unit type .busname is not supported on this system.
May 25 15:37:53 Chell systemd[416]: Reached target Timers.
May 25 15:37:53 Chell systemd[416]: Starting Timers.
May 25 15:37:53 Chell systemd[416]: Reached target Paths.
May 25 15:37:53 Chell systemd[416]: Starting Paths.
May 25 15:37:53 Chell systemd[416]: Reached target Sockets.
May 25 15:37:53 Chell systemd[416]: Starting Sockets.
May 25 15:37:53 Chell systemd[416]: Reached target Basic System.
May 25 15:37:53 Chell systemd[416]: Starting Basic System.
May 25 15:37:53 Chell systemd[416]: Reached target Default.
May 25 15:37:53 Chell systemd[416]: Startup finished in 5ms.
May 25 15:37:53 Chell systemd[416]: Starting Default.
May 25 15:37:54 Chell org.a11y.Bus[503]: Activating service name='org.a11y.atspi.Registry'
May 25 15:37:54 Chell org.a11y.Bus[503]: Successfully activated service 'org.a11y.atspi.Registry'
May 25 15:37:54 Chell org.a11y.atspi.Registry[569]: SpiRegistry daemon is running with well-known name - o
May 25 15:37:55 Chell systemd[416]: Reached target Shutdown.
May 25 15:37:55 Chell systemd[416]: Starting Shutdown.
May 25 15:37:55 Chell systemd[416]: Starting Exit the Session...
May 25 15:37:55 Chell systemd[416]: Stopped target Default.
May 25 15:37:55 Chell systemd[416]: Stopping Default.
May 25 15:37:55 Chell systemd[416]: Stopped target Basic System.
May 25 15:37:55 Chell systemd[416]: Stopping Basic System.
May 25 15:37:55 Chell systemd[416]: Stopped target Timers.
May 25 15:37:55 Chell systemd[416]: Stopping Timers.
May 25 15:37:55 Chell systemd[416]: Stopped target Paths.
May 25 15:37:55 Chell org.freedesktop.Notifications[503]: XIO:  fatal IO error 11 (Resource temporarily un
May 25 15:37:55 Chell org.freedesktop.Notifications[503]: after 688 requests (688 known processed) with 0 
May 25 15:37:55 Chell org.a11y.Bus[503]: g_dbus_connection_real_closed: Remote peer vanished with error: U
May 25 15:37:55 Chell org.a11y.atspi.Registry[569]: g_dbus_connection_real_closed: Remote peer vanished wi
May 25 15:37:55 Chell systemd[416]: Stopping Paths.
May 25 15:37:55 Chell systemd[416]: Stopped target Sockets.
May 25 15:37:55 Chell systemd[416]: Stopping Sockets.
May 25 15:37:55 Chell systemd[416]: Received SIGRTMIN+24 from PID 601 (kill).
May 25 15:37:55 Chell systemd[418]: pam_unix(systemd-user:session): session closed for user seth
May 25 15:38:08 Chell systemd[434]: Unit type .busname is not supported on this system.
May 25 15:38:08 Chell systemd[434]: Reached target Sockets.
May 25 15:38:08 Chell systemd[434]: Starting Sockets.
May 25 15:38:08 Chell systemd[434]: Reached target Paths.
May 25 15:38:08 Chell systemd[434]: Starting Paths.
May 25 15:38:08 Chell systemd[434]: Reached target Timers.
May 25 15:38:08 Chell systemd[434]: Starting Timers.
May 25 15:38:08 Chell systemd[434]: Reached target Basic System.
May 25 15:38:08 Chell systemd[434]: Starting Basic System.
May 25 15:38:08 Chell systemd[434]: Reached target Default.
May 25 15:38:08 Chell systemd[434]: Startup finished in 5ms.
May 25 15:38:08 Chell systemd[434]: Starting Default.
May 25 15:38:09 Chell org.a11y.Bus[510]: Activating service name='org.a11y.atspi.Registry'
May 25 15:38:09 Chell org.a11y.Bus[510]: Successfully activated service 'org.a11y.atspi.Registry'
May 25 15:38:09 Chell org.a11y.atspi.Registry[563]: SpiRegistry daemon is running with well-known name - o
May 25 15:41:58 Chell systemd[434]: Time has been changed
May 25 15:50:12 Chell systemd[434]: Time has been changed

I also have no suspend events in /etc/acpi/handler.sh

Last edited by SuperZanti (2015-05-25 22:16:47)

SuperZanti · 2015-05-25 22:36:17

update:

I tried completely disabling acpi events by running

sudo systemctl stop acpid

However, the problem still persists. I also just double checked all my bios settings and there is no option that I see that would fix this.

Last edited by SuperZanti (2015-05-25 23:05:24)

SuperZanti · 2015-05-26 07:57:46

I still haven't figured out anything and I've tried just about everything I know how to do in linux. If anyone even simply has any suggestions on how I could maybe get some leads that would be great.

Stebalien · 2015-05-26 11:47:01

Check your BIOS. Your laptop may have some automatic "wake and hibernate" feature that triggers when the battery drops below 5%. Unfortunately, your BIOS probably expects you to be running the OS your laptop came with along with any associated vendor specific drivers.

SuperZanti · 2015-05-26 14:07:22

Unfortunately, I've already checked the bios. I couldn't find anything related to waking up. Plus, I feel like if it was a bios thing then it wouldn't enter an infinite loop (it would just wake up once and not suspend again).

This is a complete walkthrough of my bios:
https://www.youtube.com/watch?v=qEpoBfVPKHo

I have an Asus zenbook prime ux32vda.

Last edited by SuperZanti (2015-05-26 16:46:18)

ANOKNUSA · 2015-05-27 04:14:29

If you battery is dropping below 5% charge it's better to power off the machine rather than letting the charge trickle down closer to zero while in suspend. Even letting it get to 5% is undesirable.

SuperZanti · 2015-05-27 04:39:14

I am aware. The reason I want it fixed is because I have no hibernate. Sometimes I'm not paying attention and I want to computer to suspend before I simply lose all my data. Then I can plug it in and continue working.

I know letting it get below 5% is undesirable, but it's still something I would rather have fixed than broken.

Arch Linux

#1 2015-05-25 20:55:58

Suspend doesn't work when laptop is below 5%

#2 2015-05-25 22:36:17

Re: Suspend doesn't work when laptop is below 5%

#3 2015-05-26 07:57:46

Re: Suspend doesn't work when laptop is below 5%

#4 2015-05-26 11:47:01

Re: Suspend doesn't work when laptop is below 5%

#5 2015-05-26 14:07:22

Re: Suspend doesn't work when laptop is below 5%

#6 2015-05-27 04:14:29

Re: Suspend doesn't work when laptop is below 5%

#7 2015-05-27 04:39:14

Re: Suspend doesn't work when laptop is below 5%

Board footer