You are not logged in.

#1 2013-09-18 16:32:06

axelectrik
Member
Registered: 2012-01-25
Posts: 122

System ON after Suspension

Most of the times when I try to suspend my system, everything tuns off (audio off/mouse & keyboard off/screen off) BUT the system fans are still working as if the system was still turned on.
Besides mouse and keyboard are not responding, wich doesn't allow me to turn the system on again, the reset button in case doen't work, leaving as only option to power off the system by keeping pressed the power button in case.

This is the output of journalctl (wich shows absolutely nothing):

sep 18 04:33:48 wonderland gnome-session[459]: [120B blob data]
sep 18 04:33:49 wonderland gnome-session[459]: [120B blob data]
sep 18 04:33:50 wonderland gnome-session[459]: [120B blob data]
sep 18 04:33:51 wonderland gnome-session[459]: [120B blob data]
sep 18 04:33:52 wonderland gnome-session[459]: [120B blob data]
sep 18 04:33:52 wonderland gnome-session[459]: [120B blob data]
sep 18 04:33:53 wonderland gnome-session[459]: [120B blob data]
sep 18 04:33:54 wonderland gnome-session[459]: [120B blob data]
sep 18 04:33:55 wonderland gnome-session[459]: [120B blob data]
sep 18 04:33:56 wonderland gnome-session[459]: [120B blob data]
sep 18 04:33:57 wonderland gnome-session[459]: [120B blob data]
sep 18 04:33:58 wonderland gnome-session[459]: [120B blob data]
sep 18 04:33:58 wonderland gnome-session[459]: [120B blob data]
sep 18 04:33:59 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:00 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:01 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:02 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:03 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:03 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:04 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:05 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:06 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:07 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:08 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:09 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:09 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:10 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:11 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:12 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:12 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:12 wonderland gnome-session[459]: (symbol) No such key name 'shit'. Ignoring it.
sep 18 04:34:13 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:14 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:15 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:15 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:16 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:17 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:18 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:20 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:20 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:20 wonderland gnome-session[459]: JS ERROR: !!!   WARNING: file '/usr/share/gnome-shell/extensions/alternate-tab@gnome-shell-extensions.g
sep 18 04:34:21 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:21 wonderland gnome-session[459]: [207B blob data]
sep 18 04:34:21 wonderland gnome-session[459]: [207B blob data]
sep 18 04:34:21 wonderland gnome-session[459]: [126B blob data]
sep 18 04:34:21 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:21 wonderland gnome-session[459]: [207B blob data]
sep 18 04:34:21 wonderland gnome-session[459]: [173B blob data]
sep 18 04:34:21 wonderland gnome-session[459]: [158B blob data]
sep 18 04:34:21 wonderland gnome-session[459]: [126B blob data]
sep 18 04:34:21 wonderland gnome-session[459]: [126B blob data]
sep 18 04:34:21 wonderland gnome-session[459]: [126B blob data]
sep 18 04:34:21 wonderland gnome-session[459]: [173B blob data]
sep 18 04:34:21 wonderland gnome-session[459]: [120B blob data]
sep 18 04:34:21 wonderland gnome-session[459]: (nm-applet:900): Gtk-WARNING **: Theme directory preferences/48 of theme Numix has no size field
sep 18 04:34:21 wonderland gnome-session[459]: [128B blob data]
-- Reboot --
sep 18 10:48:52 wonderland /etc/gdm/Xsession[386]: /etc/gdm/Xsession: Beginning session setup...
sep 18 10:48:52 wonderland /etc/gdm/Xsession[386]: localuser:axelectrik being added to access control list
sep 18 10:48:53 wonderland /etc/gdm/Xsession[386]: /etc/gdm/Xsession: ssh-agent not found!
sep 18 10:48:53 wonderland /etc/gdm/Xsession[386]: /etc/gdm/Xsession: Setup done, will execute: gnome-session

I really don't have an idea of how to fix this! As I said this happens most of the times, but rarely it suspends normally.
Please hel sad this is really annoying!

Offline

#2 2013-09-19 10:08:58

orschiro
Member
Registered: 2009-06-04
Posts: 2,136
Website

Re: System ON after Suspension

Do you use systemd or pm-utils for suspending?

Offline

#3 2013-09-19 22:09:25

axelectrik
Member
Registered: 2012-01-25
Posts: 122

Re: System ON after Suspension

I think is pm-utils the default by gnome.
This also happens when using kshutdown wich I assume also uses pm-utils but I'm not sure, there is no information about it.
In both cases as I said, this happens almost always but some other times it suspends normally

Offline

#4 2013-09-20 06:39:46

orschiro
Member
Registered: 2009-06-04
Posts: 2,136
Website

Re: System ON after Suspension

What happens if you use `$ systemctl suspend`?

Offline

#5 2013-09-20 07:25:50

axelectrik
Member
Registered: 2012-01-25
Posts: 122

Re: System ON after Suspension

Practically the same, it works a little bit better, in this case most of the times it suspends and few times it stays on.
This could mean a hardware problem, but I've reconfigured my BIOS  to optimized defaults, besides this has only been happening since a few months ago.

Offline

#6 2013-09-20 11:07:58

fabertawe
Member
From: Lloegr
Registered: 2009-11-24
Posts: 257

Re: System ON after Suspension

Well I'm sure this is of no help wink but ever since moving to systemd, suspend has been working 10% of the times I've tried, if that. It used to work 100% reliably with consolekit.

I've tried pm-utils and this worked once then the second time my system completely froze so not even sysrq worked. The log was exactly the same as that of the first successful suspension. This caused a resync of my array, which took hours, so I no longer attempt suspending.


i7 4790K 4.4GHz, ASRock Z97 Extreme6, 16GB 2400MHz, GTX 970, Arch x86_64

Offline

#7 2013-09-20 12:35:44

Evilandi666
Member
Registered: 2010-10-28
Posts: 105

Re: System ON after Suspension

Got the same error on KDE while using pm-utils. Happens since last update, could be 3.11.1 kernel or the last systemd update.
It worked 100% before the update, but now 90% suspend failes as described above. hmm
Maybe a kernel bug? A systemd bug?

Last edited by Evilandi666 (2013-09-20 12:38:14)

Offline

#8 2013-09-20 23:41:57

Evilandi666
Member
Registered: 2010-10-28
Posts: 105

Re: System ON after Suspension

Temporary downgrade to lts 3.10.12 fixes it.
Hopefully 3.11.2 will fix this.

Offline

#9 2013-09-22 19:23:02

axelectrik
Member
Registered: 2012-01-25
Posts: 122

Re: System ON after Suspension

I haven't trie downgrading, but probably it could be a KDE problem??
I tried to set te command on kshutdown with gnome upower method:

dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend

and since that I have no problems (only 3 days in a row) with kshutdown.
In case this happens again, I'll try to downgrade.

Offline

#10 2013-09-23 18:57:44

b9anders
Member
Registered: 2007-11-07
Posts: 681

Re: System ON after Suspension

I have a similar problem. Still testing but so far, making sure to turn OFF "never prevent an action on lid close" under Advanced Settings in PowerDevil seems to be helping it.

Offline

#11 2013-09-24 11:57:08

Evilandi666
Member
Registered: 2010-10-28
Posts: 105

Re: System ON after Suspension

Evilandi666 wrote:

Temporary downgrade to lts 3.10.12 fixes it.
Hopefully 3.11.2 will fix this.

I got it working now with 3.11.1; I was using "echo -n mem >/sys/power/state" for quite some time, this does not work anymore OR does now trigger Systemd's suspend. (I am using pm-suspend).
Changed those lines to "/usr/sbin/pm-suspend" and it works fine again.

And I had to make logind ignore all button presses for acpid to work again.

Edit: It just does not work 100%..there is a bug somewhere.
Edit2: After trying some more things, it seems that it does not have anything to do with using Systemd's suspend or pm-suspend. Or Using KDE or Gnome or acpid as trigger.
With pm-suspend it works sometimes, with systemd's suspend it never works. Tested on two different machines.
Downgraded (again) to 3.10.x (lts kernel): pm-suspend works, systemd's suspend works...
Solution (hopefully): Wait for 3.11.2.

Last edited by Evilandi666 (2013-09-24 12:51:01)

Offline

#12 2013-09-27 23:10:22

Evilandi666
Member
Registered: 2010-10-28
Posts: 105

Re: System ON after Suspension

3.11.2 did not fix it. sad

Offline

#13 2013-09-28 06:25:29

Morn
Member
Registered: 2012-09-02
Posts: 330

Re: System ON after Suspension

I am getting the exact same suspend issue whenever I leave my USB DVB-C adapter plugged in when suspending. But if I unplug the adapter prior to actually suspending the system, I still get the problem! So if the adapter has been connected at all during the system's uptime, incomplete suspend with running fans will occur every single time. So maybe USB is the cause of this problem somehow?

Offline

#14 2013-09-29 05:57:59

axelectrik
Member
Registered: 2012-01-25
Posts: 122

Re: System ON after Suspension

I can't be completly sure, BUT I think this problem happened more often whenever I had plugged in an USB.
I can't confirm it but it could be an USB issue.

Offline

#15 2013-10-10 19:59:53

Evilandi666
Member
Registered: 2010-10-28
Posts: 105

Re: System ON after Suspension

Just wanted to point out that this one is still around with 3.11.4.

Offline

Board footer

Powered by FluxBB