Restart Systemd service after laptop resume

Hi!
After resume my laptop (from suspend, I've no tried hibernation) I need to restart NetworkManager service. How can I do this automaticaly?, I've searched in google and Systemd documentation but I have not a clear idea about how to do it.
thanks

Gazpacho wrote:
lucke wrote:As boast said, you can make pm-utils run "systemctl restart networkmanager.service" after resume for you. https://wiki.archlinux.org/index.php/Pm … _own_hooks
Sorry (to boast too), you are right. I've read the wiki and created a hook, now NM restarts after resume. Thanks!
And now I've discovered that my computer only suspends the first time. Second time nothing happens when I close the tap, execute pm-suspend or the KDE menu option suspend to ram
If you have any idea it is welcome. If not I will mark the thread as solved in a couple of days and search in forums and wiki.
this usually happens when your hook doesn't exit. pm-suspend never finishes because it's waiting for the hook to exit and the second pm-suspend will block until the other pm-suspend is finished. Please post your hook.

Similar Messages

Have to restart VPN service after restarting macmini

Hello,
i am using a mid2011 macmini with Lion Server (10.7.2-Build 11C74) loaded over the Appstore, connected to an Airport Extreme (FW 7.6). I configured the VPN service in the Server settings and forwarded the profile to the clients. VPN connection works just fine.
When i restart the macmini none of the clients are able to connect with the VPN Service. Other services are running without any problems (screensharing, filesharing,...), but i cannot connect with the VPN service through any client.
After i restart the VPN Service (switch off and back on) in the Server App on the macmini it works again.
Is anyone experiencing similar behaviour with the VPN service after a restart of the server? Has anyone suggestions how to get the VPN service working even after a restart without switching it off and on again?
If you need further information please reply, i will hand it in immediately.
FYI:
I did make a complete clean install of the Server, without import of the timemachine backup to ensure the system is "clean".
kind regards
Marko

Hello,
i am using a mid2011 macmini with Lion Server (10.7.2-Build 11C74) loaded over the Appstore, connected to an Airport Extreme (FW 7.6). I configured the VPN service in the Server settings and forwarded the profile to the clients. VPN connection works just fine.
When i restart the macmini none of the clients are able to connect with the VPN Service. Other services are running without any problems (screensharing, filesharing,...), but i cannot connect with the VPN service through any client.
After i restart the VPN Service (switch off and back on) in the Server App on the macmini it works again.
Is anyone experiencing similar behaviour with the VPN service after a restart of the server? Has anyone suggestions how to get the VPN service working even after a restart without switching it off and on again?
If you need further information please reply, i will hand it in immediately.
FYI:
I did make a complete clean install of the Server, without import of the timemachine backup to ensure the system is "clean".
kind regards
Marko

[invalid] Run systemd service after specific device is initialized

Hi.
Is there any way to run systemd service only after specific device is initialized/kernel module is loaded?
The task I'm trying to solve is applying trackpoint speed and sensitivity settings on boot in my X220.
Service code (trackpoint.service) is quite simple
[Unit]
Description=Trackpoint configuration
[Service]
Type=oneshot
EnvironmentFile=/etc/conf.d/trackpoint.conf
ExecStart=/bin/sh -c 'echo ${sensitivity} > /sys/devices/platform/i8042/serio1/serio2/sensitivity'
ExecStart=/bin/sh -c 'echo ${speed} > /sys/devices/platform/i8042/serio1/serio2/speed'
[Install]
WantedBy=graphical.target
The issue is that trackpoint.service gets executed before trackpoint device gets initialized and thus fails.
Jun 14 23:12:10 xi sh[414]: /bin/sh: /sys/devices/platform/i8042/serio1/serio2/sensitivity: No such file or directory
Jun 14 23:12:10 xi systemd[1]: Unit trackpoint.service entered failed state.
Jun 14 23:12:18 xi kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
Jun 14 23:12:18 xi kernel: input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input13
What have I tried already
1. Specified systemd-modules-load in After= and Requires= directives and added psmouse module to /etc/modules-load.d
2. Tried path activation (perhaps, I did it wrong) by creating i8042.path
[Path]
PathExists=/sys/devices/platform/i8042
Unit=trackpoint.service
However, this changed nothing.
I don't know what else should I try.
Please suggest solution for this.
Thanks in advance.
Last edited by eDio (2013-06-15 13:28:36)

Thank you very much.
I've finally managed this to work
$ cat /etc/udev/rules.d/10-trackpoint.rules
SUBSYSTEM=="input", KERNEL=="event13", ACTION=="add", RUN+="/usr/bin/trackpoint_apply"
$ cat /etc/conf.d/trackpoint.conf
speed=255
sensitivity=255
$ cat /usr/bin/trackpoint_apply
#!/usr/bin/env sh
. /etc/conf.d/trackpoint.conf
/usr/bin/echo $speed > /sys/devices/platform/i8042/serio1/serio2/sensitivity
/usr/bin/echo $sensitivity > /sys/devices/platform/i8042/serio1/serio2/speed

Mac Mini Server VPN requires restart of service after each reboot

Mac mini Server (Late 2012)
OS X 10.8.4
After a reboot, when viewing in Server.app, VPN service is turned on, however no connections can be made until the service is turned off then back on again.
VPN service log entry shows "Listening for connections..." but doesn't allow incoming VPN calls until the service is restarted.
Anyone else having similar issues or have suggested solutions?
Thanks much!
Jim

Try this
https://discussions.apple.com/message/22564125#22564125

Restart of Services after changing instanceconfig.xml

Hello together,
is somebody able to explain me which Services/WEBServer I have to resart after I made some changes in the instanceconfig.xml
Regards,
Stefan

Hi Stefan,
You will need to restart the Oracle BI Server service aswell as the BI Presentation Server service.
Rgds
Ed

Is it mandatory to Restart all services after making Business Rule change?

Hi,
I know it may be a easy one but wanted to know is it mandatory to restart all the Planning and Essbase services if we make any changes in the Business rule
in 9.3.1
-KP

No you shouldn't have to restart after rule change.
Cheers
John
http://john-goodwin.blogspot.com/

Error restarting OBIEE services after deploying a RPD.

Hi all,
I have recently performed OBIEE installation and, when a repository is deployed and all services restarted comes an error like this one and BI Server status is down:
Operation Failed: start; OracleInstance: instance1; Component: coreapplication_obis1; msg 0 of 1 processes started.
OBIEE version is 11.1.1.6 and the unique RPD that works is the sample one, any others fail during the restart process.
I have been thinking that maybe it was a logging error but I am not sure due to the last actions I performed, which have been those:
- Create a new user in the Console
- Create a new repository and give the username created before and its password.
Can you help me please?
Regards,
Borja M.

Hi,
Thanks for quick answering, RPD consistency is checked and OK, so that is not the problem. RPD was also renamed and deployed again, throwing OBIEE the same error.
There is something particular related to this problem, any RPD works properly except of the one installed with the OBIEE software. I mean, maybe the error is always the same, or it is a configuration error, but I am not able to fix it.
Regards,
Borja

[SOLVED]Correct way to restart a systemd service on resume from susp?

I have offlineimap setup to run as a daemon. It doesn't correctly resume operations after a resume from suspend to RAM without being restarted. The 'Conflicts=' line in the service file makes sure it is stopped when the machine suspends, but I can't figure out how to get it restarted again. Here is the service file:
[Unit]
Description=Start offlineimap as a daemon
Requires=network.target
Conflicts=suspend.target
After=network.target
[Service]
User=%i
EnvironmentFile=/home/%i/.gnupg/gpg-agent-info
ExecStart=/usr/bin/offlineimap
KillSignal=SIGUSR2
Restart=always
RestartSec=15
[Install]
WantedBy=multi-user.target
I found an email thread here that seemed to imply that I could add sleep.target to 'WantedBy=' and sleep.target to 'After=' to get service to startup again after resume, but that didn't seem to work.
Any ideas? Thanks!
Scott
Last edited by firecat53 (2014-07-01 16:40:20)

tomk wrote:
firecat53 wrote:It doesn't correctly resume operations after a resume from suspend to RAM without being restarted.
Is this just something you have observed on your own system, or is it a known bug?
Something I noticed and figured it was just due to frequently switching networks with VPN on/off again. After a quick search, I discovered the 'socktimeout' option, which I'm testing now to see if that solves the problem. It appears (although I _just_ found this, that it is a known bug. Some have had luck with setting socktimeout, others haven't. I'll post back if I see a difference or not.
Thanks for the nudge
Scott

Restarting a systemd.service with a dependency job failed.

Hello.
Let's say I have foo.service containing that:
[Unit]
Description=Is executed only if bar.service success
Requires=bar.service
After=bar.service
[Service]
Type=simple
TimeoutSec=6
Restart=on-failure
ExecStart=/usr/bin/touch /tmp/test
And i have bar.service containing that:
[Unit]
Description=Test in foo.tld is reachable
[Service]
Type=oneshot
ExecStart=/usr/bin/ping -c1 foo.tld
[Install]
WantedBy=multi-user.target
If the ping fails in bar.service, then I'll get that when I try to start foo.service: « A dependency job for foo.service failed. See 'journalctl -xn' for details. »
How can I make foo.service check every n seconds if its dependency jobs are fullfilled/successfull instead of just failing and stopping like it currently does ?
I'm searching for a "Restart" option that would apply if the dependency check fails. I'm not sure if this is possible.
Thank you in advance for your answers.

Maybe you're looking for RequiresOverrideable? From the man page of systemd.unit
RequiresOverridable=
Similar to Requires=. Dependencies listed in RequiresOverridable= which cannot be fulfilled or fail to start are ignored if the startup was explicitly requested by the user. If the start-up was
pulled in indirectly by some dependency or automatic start-up of units that is not requested by the user, this dependency must be fulfilled and otherwise the transaction fails. Hence, this option
may be used to configure dependencies that are normally honored unless the user explicitly starts up the unit, in which case whether they failed or not is irrelevant.

[solved] How to restart all services with systemd?

I had the habit of restarting all daemons after an upgrade so to make sure the newest libraries, configuration files etc were loaded. I did that with a shell script that restarted the daemons in order which they were listed in rc.conf. With systemd I could do something similar by first getting a list of running services and ordering a 'systemcrl restart <servicename>' for each. But since systemd keeps track of dependencies I wonder if that would be the way to do it. Also I would need to filter out 'one shot' type services that are only needed on bootup.
<edit>restart instead of reload</edit>
<edit>solved it with a little script</edit>
Last edited by rwd (2012-11-27 21:02:02)

I think that's what systemctl snapshot does.
snapshot [NAME]
Create a snapshot. If a snapshot name is specified, the new snapshot will be named after it. If none is specified an automatic snapshot name is generated. In either case, the snapshot name used is printed to STDOUT, unless --quiet is specified.
A snapshot refers to a saved state of the systemd manager. It is implemented itself as a unit that is generated dynamically with this command and has dependencies on all units active at the time. At a later time the user may return to this state by using the isolate command on the snapshot unit.
Snapshots are only useful for saving and restoring which units are running or are stopped, they do not save/restore any other state. Snapshots are dynamic and lost on reboot.
Then, isolate emergency.target or rescue target and switch to the snapshot.

After servicing my laptop recently, I can no longer find the time machine back up disk

I recenty had my macbook pro serviced after the hard drive cable was broken. Upon return, when I attempt to back up to time machine it says backup disk not available and I cannot find any disks to select in time machine preferences. Any idea how to fix this?

aimehunter,
if you had Time Machine running without connecting an external drive directly to your MacBook Pro, then it must have been a wireless connection to an AirPort Time Capsule.
Open the Time Machine pane in System Preferences. Does it show that you have a destination drive selected there? If not, press the Select Disk… button to select your AirPort Time Capsule drive. After that, select Back Up Now from the Time Machine icon in your menu bar to restart your regular Time Machine backups.

Systemd: starting service after graphical target without

Hi there,
I have a service that I want to start after X has been started.
This is my service file:
[Unit]
Description=Run powersaving script depending on AC state
After=graphical.target
[Service]
Type=oneshot
KillMode=none
ExecStart=/usr/bin/powersaving
[Install]
WantedBy=multi-user.target
However, during boot I get the following error message:
~ systemctl status powersaving
● powersaving.service - Run powersaving script depending on AC state
Loaded: loaded (/usr/lib/systemd/system/powersaving.service; enabled)
Active: inactive (dead)
Apr 07 07:16:14 thinkpad systemd[1]: Found ordering cycle on powersaving.service/start
Apr 07 07:16:14 thinkpad systemd[1]: Found dependency on graphical.target/start
Apr 07 07:16:14 thinkpad systemd[1]: Found dependency on multi-user.target/start
Apr 07 07:16:14 thinkpad systemd[1]: Found dependency on powersaving.service/start
Apr 07 07:16:17 thinkpad systemd[1]: Found ordering cycle on powersaving.service/start
Apr 07 07:16:17 thinkpad systemd[1]: Found dependency on graphical.target/start
Apr 07 07:16:17 thinkpad systemd[1]: Found dependency on multi-user.target/start
Apr 07 07:16:17 thinkpad systemd[1]: Found dependency on powersaving.service/start
~ dmesg | grep powersaving
[ 7.492597] systemd[1]: Found dependency on powersaving.service/start
[ 7.492604] systemd[1]: Breaking ordering cycle by deleting job powersaving.service/start
[ 7.492608] systemd[1]: Job powersaving.service/start deleted to break ordering cycle starting with graphical.target/start
I found this thread which suggests to use display-manager.service instead of the graphical target.
However, I start X manually using startx and no display-manager.
So how can I run my service after starting of X without a display-manager?
Thanks!

I don't think your new version will work. Your new version will make your service part of multi-user.target and started after multi-user.target; so you are asking systemd to start your service after itself. In any case such attempts will start the service before startx. startx is a command that you run as an ordinary user, X has the special privilege to get root access (it has the suid bit set) and systemd is not involved in the process. I do not think that you can tell systemd to start a service after a command that you launch by hand; and I don' think it's the purpose of systemd. You are really asking to launch a daemon that needs root access as part of a command that you run as an ordinary user. One of the solution is to use sudo and put sudo /usr/bin/powersaving into ~/.xinitrc after having properly configured sudo.
Last edited by olive (2014-04-07 08:34:32)

After restarting the Services, Foundation service is not starting

Hi All,
Recently, i have applied patch and restarted the services, later found that foundation services is not starting. I have referred the logs and it showing below error.
<Apr 29, 2015 7:45:30 PM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.2.0-79-146777-1.6.0_29-20111005-1808-windows-x86_64 from Oracle Corporation>
<Apr 29, 2015 7:45:31 PM PDT> <Critical> <Security> <BEA-090518> <Could not decrypt the username attribute value of {AES}9e8e9w8ADkG/3Hx33gkE9Ukm29IxHIISKLeLw/FYfxTO0GcnA= from the file C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\security\boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\security\boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException.>
Enter username to boot WebLogic server:
I have logged to Weblogic server and checked, the foundation service is not started.
We dont have the backup of installation folder.
I manually edited the user name and password and started the services, but no luck.
Do any one idea about processBootProperties.cmd, shall i trigger it to get the new boot.properties.
Please suggest.
Thanks

Hi all,
I manually enter the credential for the Web logic server and started the services. It worked out.
I did the same first, but i did some typo error in credential, it killed me for more that 1 hour... ):
Thanks

[SOLVED] Laptop resumes from suspend while lid is still closed

Hi all,
I'm having some weird issue ever since I installed arch on my new laptop (Haswell).
When I put my computer to suspend by closing the lid, all goes well.
But the computer resumes by itself after a while. I have no idea why, WoL is disabled on both ethernet and wifi.
Can someone help figure out what is causing the computer to resume?
For example here is a magic wake up after 1 hour asleep.
Feb 15 00:37:15 jitte systemd[1]: Starting TLP suspend/resume...
Feb 15 00:37:15 jitte tlp[24682]: grep: /sys/devices/platform/dock.?/type: No such file or directory
Feb 15 00:37:15 jitte systemd[1]: Started TLP suspend/resume.
Feb 15 00:37:15 jitte systemd[1]: Starting Sleep.
Feb 15 00:37:15 jitte systemd[1]: Reached target Sleep.
Feb 15 00:37:15 jitte systemd[1]: Starting Suspend...
Feb 15 00:37:15 jitte systemd-sleep[24748]: Suspending system...
Feb 15 00:37:15 jitte kernel: PM: Syncing filesystems ... done.
Feb 15 00:37:15 jitte kernel: PM: Preparing system for mem sleep
Feb 15 00:37:15 jitte kernel: bbswitch: enabling discrete graphics
Feb 15 01:34:26 jitte kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Feb 15 01:34:26 jitte systemd[1]: Time has been changed
Feb 15 01:34:26 jitte kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Feb 15 01:34:26 jitte kernel: PM: Entering mem sleep
Feb 15 01:34:26 jitte kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 15 01:34:26 jitte kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 15 01:34:26 jitte kernel: sd 0:0:0:0: [sda] Stopping disk
Feb 15 01:34:26 jitte kernel: mei_me 0000:00:16.0: suspend
Feb 15 01:34:26 jitte kernel: PM: suspend of devices complete after 220.139 msecs
Feb 15 01:34:26 jitte systemd[607]: Time has been changed
Feb 15 01:34:26 jitte kernel: PM: late suspend of devices complete after 0.115 msecs
Feb 15 01:34:26 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
Feb 15 01:34:26 jitte kernel: PM: noirq suspend of devices complete after 66.764 msecs
Feb 15 01:34:26 jitte kernel: ACPI: Preparing to enter system sleep state S3
Feb 15 01:34:26 jitte kernel: PM: Saving platform NVS memory
Feb 15 01:34:26 jitte kernel: Disabling non-boot CPUs ...
Feb 15 01:34:26 jitte kernel: smpboot: CPU 1 is now offline
Feb 15 01:34:26 jitte kernel: smpboot: CPU 2 is now offline
Feb 15 01:34:26 jitte kernel: smpboot: CPU 3 is now offline
Feb 15 01:34:26 jitte kernel: ACPI: Low-level resume complete
Feb 15 01:34:26 jitte kernel: PM: Restoring platform NVS memory
Feb 15 01:34:26 jitte kernel: Enabling non-boot CPUs ...
Feb 15 01:34:26 jitte kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Feb 15 01:34:26 jitte kernel: Intel pstate controlling: cpu 1
Feb 15 01:34:26 jitte kernel: CPU1 is up
Feb 15 01:34:26 jitte kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Feb 15 01:34:26 jitte kernel: Intel pstate controlling: cpu 2
Feb 15 01:34:26 jitte kernel: CPU2 is up
Feb 15 01:34:26 jitte kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Feb 15 01:34:26 jitte kernel: Intel pstate controlling: cpu 3
Feb 15 01:34:26 jitte kernel: CPU3 is up
Feb 15 01:34:26 jitte kernel: ACPI: Waking up from system sleep state S3
Feb 15 01:34:26 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 15 01:34:26 jitte kernel: PM: noirq resume of devices complete after 130.807 msecs
Feb 15 01:34:26 jitte kernel: PM: early resume of devices complete after 0.108 msecs
Feb 15 01:34:26 jitte kernel: i915 0000:00:02.0: setting latency timer to 64
Feb 15 01:34:26 jitte kernel: mei_me 0000:00:16.0: irq 57 for MSI/MSI-X
Feb 15 01:34:26 jitte kernel: snd_hda_intel 0000:00:03.0: irq 61 for MSI/MSI-X
Feb 15 01:34:26 jitte kernel: ehci-pci 0000:00:1d.0: setting latency timer to 64
Feb 15 01:34:26 jitte kernel: ahci 0000:00:1f.2: setting latency timer to 64
Last edited by jtheoof (2014-03-16 19:15:02)

So here's the update for today: sudo journalctl -amb.
Feb 25 13:39:00 jitte kernel: ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event
Feb 25 13:39:00 jitte kernel: ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event
Feb 25 13:39:00 jitte systemd-logind[276]: Lid closed.
Feb 25 13:39:00 jitte systemd-logind[276]: Suspending...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> sleep requested (sleeping: no enabled: yes)
Feb 25 13:39:00 jitte NetworkManager[273]: <info> sleeping or disabling...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): deactivating device (reason 'sleeping') [37]
Feb 25 13:39:00 jitte dhcpcd[22409]: received SIGTERM from PID 273, stopping
Feb 25 13:39:00 jitte dhcpcd[22409]: wlp2s0: removing interface
Feb 25 13:39:00 jitte dhcpcd[22409]: exited
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 22409
Feb 25 13:39:00 jitte NetworkManager[273]: <info> Removing DNS information from /usr/bin/resolvconf
Feb 25 13:39:00 jitte kernel: wlp2s0: deauthenticating from 00:24:d4:5f:dc:d8 by local choice (reason=3)
Feb 25 13:39:00 jitte kernel: cfg80211: Calling CRDA to update world regulatory domain
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): cleaning up...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): taking down device.
Feb 25 13:39:00 jitte NetworkManager[273]: <info> NetworkManager state is now ASLEEP
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (enp3s0f1): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (enp3s0f1): cleaning up...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (enp3s0f1): taking down device.
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte dbus[278]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Feb 25 13:39:00 jitte systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte dbus[278]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 25 13:39:01 jitte systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 25 13:39:01 jitte gnome-session[1672]: Window manager warning: Log level 16: gsignal.c:2593: instance '0x15b1e20' has no handler with id '468541'
Feb 25 13:39:05 jitte systemd-logind[276]: Delay lock is active but inhibitor timeout is reached.
Feb 25 13:39:05 jitte systemd[1]: Starting Sleep.
Feb 25 13:39:05 jitte systemd[1]: Reached target Sleep.
Feb 25 13:39:05 jitte systemd[1]: Starting Suspend...
Feb 25 13:39:05 jitte systemd-sleep[22893]: Suspending system...
Feb 25 13:39:05 jitte kernel: PM: Syncing filesystems ... done.
Feb 25 13:39:05 jitte kernel: PM: Preparing system for mem sleep
Feb 25 13:39:05 jitte kernel: bbswitch: enabling discrete graphics
Feb 25 17:22:59 jitte kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Feb 25 17:22:59 jitte systemd[1]: Time has been changed
Feb 25 17:22:59 jitte systemd[1666]: Time has been changed
Feb 25 17:22:59 jitte kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Feb 25 17:22:59 jitte kernel: PM: Entering mem sleep
Feb 25 17:22:59 jitte kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 25 17:22:59 jitte kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 25 17:22:59 jitte kernel: sd 0:0:0:0: [sda] Stopping disk
Feb 25 17:22:59 jitte kernel: PM: suspend of devices complete after 1098.028 msecs
Feb 25 17:22:59 jitte kernel: PM: late suspend of devices complete after 0.504 msecs
Feb 25 17:22:59 jitte kernel: pcieport 0000:00:1c.3: System wakeup enabled by ACPI
Feb 25 17:22:59 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
Feb 25 17:22:59 jitte kernel: PM: noirq suspend of devices complete after 66.728 msecs
Feb 25 17:22:59 jitte kernel: ACPI: Preparing to enter system sleep state S3
Feb 25 17:22:59 jitte kernel: PM: Saving platform NVS memory
Feb 25 17:22:59 jitte kernel: Disabling non-boot CPUs ...
Feb 25 17:22:59 jitte kernel: kvm: disabling virtualization on CPU1
Feb 25 17:22:59 jitte kernel: smpboot: CPU 1 is now offline
Feb 25 17:22:59 jitte kernel: kvm: disabling virtualization on CPU2
Feb 25 17:22:59 jitte kernel: smpboot: CPU 2 is now offline
Feb 25 17:22:59 jitte kernel: kvm: disabling virtualization on CPU3
Feb 25 17:22:59 jitte kernel: smpboot: CPU 3 is now offline
Feb 25 17:22:59 jitte kernel: ACPI: Low-level resume complete
Feb 25 17:22:59 jitte kernel: PM: Restoring platform NVS memory
Feb 25 17:22:59 jitte kernel: Enabling non-boot CPUs ...
Feb 25 17:22:59 jitte kernel: x86: Booting SMP configuration:
Feb 25 17:22:59 jitte kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Feb 25 17:22:59 jitte kernel: kvm: enabling virtualization on CPU1
Feb 25 17:22:59 jitte kernel: Intel pstate controlling: cpu 1
Feb 25 17:22:59 jitte kernel: CPU1 is up
Feb 25 17:22:59 jitte kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Feb 25 17:22:59 jitte kernel: kvm: enabling virtualization on CPU2
Feb 25 17:22:59 jitte kernel: Intel pstate controlling: cpu 2
Feb 25 17:22:59 jitte kernel: CPU2 is up
Feb 25 17:22:59 jitte kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Feb 25 17:22:59 jitte kernel: kvm: enabling virtualization on CPU3
Feb 25 17:22:59 jitte kernel: Intel pstate controlling: cpu 3
Feb 25 17:22:59 jitte kernel: CPU3 is up
Feb 25 17:22:59 jitte kernel: ACPI: Waking up from system sleep state S3
Feb 25 17:22:59 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 25 17:22:59 jitte kernel: PM: noirq resume of devices complete after 132.766 msecs
Feb 25 17:22:59 jitte systemd[1666]: Service bluetooth.target is not needed anymore. Stopping.
Feb 25 17:22:59 jitte systemd[1]: Service bluetooth.target is not needed anymore. Stopping.
Feb 25 17:22:59 jitte systemd[1666]: Stopping Bluetooth.
Feb 25 17:22:59 jitte systemd[1666]: Stopped target Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Stopping Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Stopped target Bluetooth.
Feb 25 17:22:59 jitte systemd[1666]: Starting Bluetooth.
Feb 25 17:22:59 jitte systemd[1666]: Reached target Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Starting Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Reached target Bluetooth.
Feb 25 17:22:59 jitte kernel: PM: early resume of devices complete after 0.347 msecs
Feb 25 17:22:59 jitte kernel: hpet1: lost 2539 rtc interrupts
Feb 25 17:22:59 jitte kernel: mei_me 0000:00:16.0: irq 58 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: usb usb1: root hub lost power or was reset
Feb 25 17:22:59 jitte kernel: usb usb2: root hub lost power or was reset
Feb 25 17:22:59 jitte kernel: snd_hda_intel 0000:00:03.0: irq 61 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: irq 62 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: snd_hda_intel 0000:00:1b.0: irq 63 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: pcieport 0000:00:1c.3: System wakeup disabled by ACPI
Feb 25 17:22:59 jitte kernel: dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -19
Feb 25 17:22:59 jitte kernel: PM: Device 00:07 failed to resume: error -19
Feb 25 17:22:59 jitte kernel: usb 3-1: reset high-speed USB device number 2 using ehci-pci
Feb 25 17:22:59 jitte kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd ef/10:09:00:00:00:b0 (SET FEATURES) succeeded
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 25 17:22:59 jitte kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd ef/10:09:00:00:00:b0 (SET FEATURES) succeeded
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 25 17:22:59 jitte kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
Feb 25 17:22:59 jitte kernel: ata1.00: configured for UDMA/133
Feb 25 17:22:59 jitte kernel: sd 0:0:0:0: [sda] Starting disk
Feb 25 17:22:59 jitte kernel: usb 1-5: reset high-speed USB device number 2 using xhci_hcd
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af174f00
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af174f40
Feb 25 17:22:59 jitte kernel: usb 1-6: reset full-speed USB device number 3 using xhci_hcd
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af143780
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af1437c0
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af143800
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802320b0900
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802320b0940
Feb 25 17:22:59 jitte kernel: usb 1-7: reset full-speed USB device number 5 using xhci_hcd
Feb 25 17:22:59 jitte kernel: [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88022dc25300
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88022dc25340
Feb 25 17:22:59 jitte kernel: usb 1-7: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes
Feb 25 17:22:59 jitte kernel: PM: resume of devices complete after 1355.352 msecs
Feb 25 17:22:59 jitte kernel: PM: Finishing wakeup.
Feb 25 17:22:59 jitte kernel: Restarting tasks ...
Feb 25 17:22:59 jitte kernel: iwlwifi 0000:02:00.0: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: rtsx_pci 0000:03:00.0: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: r8169 0000:03:00.1: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: pci 0000:04:00.0: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: done.
Feb 25 17:22:59 jitte kernel: video LNXVIDEO:00: Restoring backlight state
Feb 25 17:22:59 jitte kernel: video LNXVIDEO:01: Restoring backlight state
Feb 25 17:22:59 jitte kernel: bbswitch: disabling discrete graphics
Feb 25 17:22:59 jitte kernel: ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
Feb 25 17:22:59 jitte kernel: Bluetooth: hci0: read Intel version: 370710018002030d00
Feb 25 17:22:59 jitte kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Feb 25 17:22:59 jitte kernel: Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
Feb 25 17:22:59 jitte bluetoothd[272]: Failed to set mode: Blocked through rfkill (0x12)
Feb 25 17:22:59 jitte systemd-sleep[22893]: System resumed.
Feb 25 17:22:59 jitte systemd[1]: Started Suspend.
Feb 25 17:22:59 jitte systemd[1]: Requested transaction contradicts existing jobs: File exists
Feb 25 17:22:59 jitte systemd[1]: Service sleep.target is not needed anymore. Stopping.
Feb 25 17:22:59 jitte systemd[1]: Stopping Sleep.
Feb 25 17:22:59 jitte systemd[1]: Stopped target Sleep.
Feb 25 17:22:59 jitte systemd[1]: Reached target Suspend.
Feb 25 17:22:59 jitte systemd-logind[276]: Operation finished.
Feb 25 17:22:59 jitte NetworkManager[273]: <info> wake requested (sleeping: yes enabled: yes)
Feb 25 17:22:59 jitte NetworkManager[273]: <info> waking up and re-enabling...
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): bringing up device.
Feb 25 17:22:59 jitte kernel: iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
Feb 25 17:22:59 jitte kernel: iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
Feb 25 17:22:59 jitte kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): preparing device.
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): deactivating device (reason 'managed') [2]
Feb 25 17:22:59 jitte NetworkManager[273]: <info> NetworkManager state is now DISCONNECTED
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): bringing up device.
Feb 25 17:22:59 jitte kernel: r8169 0000:03:00.1 enp3s0f1: link down
Feb 25 17:22:59 jitte kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0f1: link is not ready
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): preparing device.
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): deactivating device (reason 'managed') [2]
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0) supports 5 scan SSIDs
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0): supplicant interface state: starting -> ready
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Feb 25 17:23:00 jitte NetworkManager[273]: <warn> Trying to remove a non-existant call id.
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0): supplicant interface state: ready -> disconnected
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0) supports 5 scan SSIDs
Feb 25 17:23:02 jitte kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
Feb 25 17:23:02 jitte kernel: atkbd serio0: Use 'setkeycodes e00d <keycode>' to make it known.
What's really odd is that the laptop woke up at the exact same time as yesterday. What could be causing that?
I'm using gnome-shell v3.10.3-1, linux-mainline v3.14rc3-1.

Powersave not restarting network properly after suspend

My laptop uses ethernet hardware supported by the sky2 module, which must be unloaded before suspend. Network has to be restarted after the module is reloaded or ethernet stays kaput. So, I edited my /etc/powersave/sleep like this:
## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "nvsound acx100 acx_pci hsfmodem prism54 bcm4400 emu10k1 forcedeth ipw2100 ipw2200 natsemi psmouse rt2400 ehci_hcd ohci_hcd uhci_hcd ehci-hcd usb-ohci usb-uhci snd_ens1370 snd_ens1371 en1370 en1371 via_agp via_rhine i8042 intel_mch_agp rt2500 button speedstep_smi ndiswrapper"
## ServiceRestart: "network,alsa,netfs"
# These modules will be unloaded before entering suspend to disk
# See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="prism54 sky2 ath_pci"
## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "nvsound acx100 acx_pci hsfmodem prism54 bcm4400 emu10k1 forcedeth ipw2100 ipw2200 natsemi psmouse rt2400 ehci_hcd ohci_hcd uhci_hcd ehci-hcd usb-ohci usb-uhci snd_ens1370 snd_ens1371 en1370 en1371 via_agp via_rhine i8042 intel_mch_agp rt2500 button speedstep_smi ndiswrapper"
## ServiceRestart: "network,alsa,netfs"
# These modules will be unloaded before entering the corresponding
# sleep state. See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="prism54 sky2 ath_pci"
## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "nvsound acx100 acx_pci hsfmodem prism54 bcm4400 emu10k1 forcedeth ipw2100 ipw2200 natsemi psmouse rt2400 ehci_hcd ohci_hcd uhci_hcd ehci-hcd usb-ohci usb-uhci snd_ens1370 snd_ens1371 en1370 en1371 via_agp via_rhine i8042 intel_mch_agp rt2500 button speedstep_smi ndiswrapper"
## ServiceRestart: "network,alsa,netfs"
# These modules will be unloaded before entering the corresponding
# sleep state. See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_STANDBY="prism54 sky2 ath_pci"
## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: string
## Default: "slmodemd irda"
# All services that have to be stopped before entering a sleep mode
# and restarted after the machine resumes.
# If you notice problems of some services that may be related to
# suspend/standby, restarting the service may solve the problem.
# The names to enter here are simply the filenames of the init scripts
# in /etc/init.d. The services are stopped in the order entered here.
# They are restarted after resume in the reverse order.
# Entering "NONE" disables restarting of services ("" means default).
SUSPEND2DISK_RESTART_SERVICES="network"
SUSPEND2RAM_RESTART_SERVICES="network"
STANDBY_RESTART_SERVICES="network"
Problem is, powersaved doesn't restart the network like it ought to. The log gives me this:
suspend2ram initiated: 2007-06-05 07:05:46 PM
Debug info follows here, please include in your bug reports. Thanks.
Loaded modules:
Module Size Used by
sky2 37896 0
rtc_sysfs 3840 0
rtc_proc 3844 0
snd_seq_oss 29056 0
snd_seq_midi_event 6528 1 snd_seq_oss
snd_seq 46800 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 6796 2 snd_seq_oss,snd_seq
joydev 8384 0
usbhid 36256 0
hid 24448 1 usbhid
ff_memless 5256 1 usbhid
snd_pcm_oss 38816 0
rtc_dev 6792 0
snd_mixer_oss 14336 1 snd_pcm_oss
pcmcia 31404 0
rtc_cmos 7188 0
i2c_i801 7952 0
i2c_core 17664 1 i2c_i801
rtc_core 7684 4 rtc_sysfs,rtc_proc,rtc_dev,rtc_cmos
rtc_lib 3456 2 rtc_sysfs,rtc_core
tifm_7xx1 6912 0
tifm_core 6784 1 tifm_7xx1
ath_pci 88224 0
wlan 188868 1 ath_pci
pcspkr 2944 0
psmouse 35080 0
serio_raw 5636 0
ath_hal 190032 1 ath_pci
snd_hda_intel 254104 1
snd_pcm 68484 2 snd_pcm_oss,snd_hda_intel
snd_timer 19076 2 snd_seq,snd_pcm
snd 44388 10 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer
soundcore 6496 1 snd
yenta_socket 23180 1
rsrc_nonstatic 11136 1 yenta_socket
pcmcia_core 32920 3 pcmcia,yenta_socket,rsrc_nonstatic
sg 26780 0
snd_page_alloc 7816 2 snd_hda_intel,snd_pcm
ehci_hcd 31116 0
uhci_hcd 22032 0
tsdev 6464 0
evdev 8192 6
thermal 11656 0
processor 24788 1 thermal
fan 3972 0
button 6288 0
battery 8580 0
ac 4100 0
i915 21376 2
drm 70548 3 i915
intel_agp 21404 1
agpgart 27608 3 drm,intel_agp
usbcore 111752 4 usbhid,ehci_hcd,uhci_hcd
ext3 118536 2
jbd 54952 1 ext3
mbcache 6916 1 ext3
sr_mod 14372 0
cdrom 34080 1 sr_mod
sd_mod 17668 3
ata_generic 5636 0
ata_piix 11780 2
libata 102164 2 ata_generic,ata_piix
Memory info:
total used free shared buffers cached
Mem: 506356 370360 135996 0 7444 87180
-/+ buffers/cache: 275736 230620
Swap: 0 0 0
/proc/cmdline: root=/dev/sda1 ro idle=halt acpi_sleep=s3_mode
========we are going to sleep, preparing.========
== checking runlevel ==
no shutdown/reboot in progress, good.
== Unmounting FAT/NTFS filesystems: ==
none found in /etc/mtab
== FAT/NTFS filesystems unmounted ==
Stopping services: ('network' configured)
none running.
ejecting PCMCIA cards...
Unloading modules: ('prism54 sky2' configured)
checking prism54
checking sky2
# trying to unload: sky2
unloaded: sky2
prepare_sleep finished for suspend2ram
/usr/sbin/s2ram not found, falling back to echo.
==== finished, return code 0 ====
========we are back from suspend, cleaning up.========
== restore_after_sleep: restart and reload everything ==
Resuming:
switched back to console: ' 7'
Reloading modules:
sky2
inserting PCMCIA cards...
Restarting services:
Remounting filesystems:
not necessary.
======================================
restore_after_suspend_to_ram: finished
Apparently network is considered already accounted for, but it isn't. I have to restart the script manually. What's up with this?

Umm... OP? Log doesn't say that network fails, but appears to indicate that powersaved does not try to restart it. I'll give it a shot but it looks completely irrelevant.
Edit: Well I'll be damned, it worked. Just a second, I'm going to do a bit more messing around...
Edit again: Hmm, strange, works without the 5-second wait now. Damned if I know what was up with that.
Last edited by Gullible Jones (2007-06-06 01:35:48)

Restart Systemd service after laptop resume

Similar Messages

Maybe you are looking for