[Solved] Systemd suspend fails everytime
Hi,
I've been using Arch Linux on my laptop for a while now and suddenly my laptop would not go into suspend anymore.
My laptop is Asus UX32VD.
Here's the whole journalctl between suspend starting and suspend failing.
I also get this at bootup:
[drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up
some while ago the iSSD in my laptop failed but it was later that the computer stopped suspending.
Does anyone see the problem?
Thanks.
Edit: When I try to mount the iSSD partitions I get the same error messages that begin with "ata2.00" so those errors seem to be connected to the iSSD drive. Now, I can't disable the drive in bios, is it possible to make arch linux ignore it all together?
Edit2: Arch Linux is installed on sda (ata1) and the bad drive is sdb (ata2)
Edit3: The broken ssd was the culprit. When I write 1 to /sys/block/sdb/device/delete the laptop suspends correctly.
So I made the following systemd service:
[Unit]
Description=Disable my fault ssd drive at suspend
[Service]
Type=OneShot
ExecStart=/bin/sh -c 'echo 1 > /sys/block/sdb/device/delete'
[Install]
WantedBy=sleep.target
Changing status to solved
Last edited by granra (2014-04-18 23:01:57)
Rexilion wrote:What is stopping you from taking it out?
It's soldered to the motherboard.
Similar Messages
-
[SOLVED] systemd --user: "Failed to open private bus connection:"
EDIT: The solution was to set DBUS_SESSION_BUS_ADDRESS, as suggested by gtmanfred in irc. By putting the following before executing systemd --user, the error vanished:
export DBUS_SESSION_BUS_ADDRESS=/run/user/$(id -u)/dbus/user_bus_socket
===================
Original problem:
Everything on my box appears to be working ok, but I'm getting this error consistently in tty1 and at the top of journalctl (as user) whenever I start systemd --user:
systemd[3975]: Failed to open private bus connection: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
I roughly have my system setup per this wiki section https://wiki.archlinux.org/index.php/Sy … ur_Session. I start systemd --user via a small script in my .bash_profile. Here are my relevant dbus{.service,socket} files, from the package user-session-units mentioned in the wiki: (Edit: xorg is started through xorg-launch-helper, also from that wiki page) Edit2: I'm not using autologin. I noticed that under the autologin section of that page, DBUS_SESSION_BUS_ADDRESS is set to some path. In my setup that isn't set anywhere, so I may try to copy that later but I don't have time to play with it right now. Will post back later.
=====/usr/lib/systemd/user/dbus.service=====
[Unit]
Description=D-Bus System Message Bus
Requires=dbus.socket
[Service]
ExecStart=/usr/bin/dbus-daemon --session --address=systemd: --nofork --systemd-activation
ExecReload=/usr/bin/dbus-send --print-reply --session --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig
=====/usr/lib/systemd/user/dbus.socket=====
[Unit]
Description=D-Bus System Message Bus Socket
[Socket]
ListenStream=%t/dbus/user_bus_socket
And the output of sudo systemctl status dbus:
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Tue 2013-02-05 14:50:30 EST; 22min ago
Main PID: 369 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
└─369 /usr/bin/dbus-daemon --system --address=systemd: --no...
Feb 05 14:50:30 sellers-laptop systemd[1]: Starting D-Bus System Message Bus...
Feb 05 14:50:30 sellers-laptop systemd[1]: Started D-Bus System Message Bus.
Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 05 14:51:18 sellers-laptop dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 05 14:51:18 sellers-laptop dbus[369]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
I'm not sure what the error even means or how to go about debugging it. Any suggestions would be appreciated.
Last edited by Feynman (2013-02-05 22:07:23)NVM...didn't notice it was already solved.
Last edited by the sad clown (2013-02-05 22:33:10) -
[SOLVED] systemd boot fails - Removable on fstab
Just converted to the dark (systemd) side.
Very straight forward, simple and easy enough.
I have one problem with boot process.
I have three usb devices that i use frequently, below is my fstab
# Removable Media
UUID=6e4bc1aa-3414-48b9-9598-5eedfaadbe2b /media/FreeAgent1 ext4 defaults,user 0 0
UUID=14219291-0703-45b6-95db-976c5b7c3b7b /media/FreeAgent2 ext4 defaults,user 0 0
UUID=0590bbe0-d098-4f81-a9c7-c72654aa54a5 /media/Sandisk ext4 defaults,user 0 0
USB devices at the moment arent on the pc.
With init process, everything was fine.
Boot process gave me prompt.
With systemd, my archlinux box doesnt boot (at all)
http://ebalaskas.gr/img/systemd_removeable.png
Reading https://bbs.archlinux.org/viewtopic.php?id=146982 & http://lists.freedesktop.org/archives/s … 06292.html
i get the feeling that perhaps is a bug.
But i am not sure.
The emergency mode (^D) doesnt work either - keyboard seemed dead.
Used old transitional init=/bin/sh to comment out the removable devices from my fstab
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by ebal (2012-08-24 06:43:52)ebal wrote:
Nothing is needed to be done to fstab file !
it shouldnt
it mustnt
with the heck i must edit my fstab cause systemd doesnt have a proper function to timeout when there are devices that are not present at boot time !!!
That dont even make sense.
Thank you all for your answers but PLZ ... try to focus on the actual problem that systemd is failing to boot and not to fstab !
btw from my first post i 've already mentioned that i commented out these entries just to boot with systemd.
what is the problem with using nofail or noauto,x-systemd.automount? systemd does the right thing here, it tries to mount the device on boot and waits for it - it's just that the timeout is very long (afaik 90 seconds).
the only reason this worked with initscripts is that afaik initscripts just tries to mount the device and won't wait for it if it isn't there, but instead just fails immediately. While this worked, it was still the wrong approach. You should have added noauto or nofail in the first place. -
[SOLVED] systemd : services failing to start on boot
I have removed sysvinit completely as per the systemd wiki pages.
I don't usually re-boot very often so I'm not sure exactly when the problem started.
I only noticed this problem about 4 or 5 days ago.
But now whenever I reboot my machine 2 services fail consistently.
adsl.service
colord.service
They both start flawlessly once I can log in at a console.
I'm using kde and in the last couple of days, while trying to fix my problem, the kdm service has failed to start a couple of times too - saying there is no X server.
Before switching to systemd I never had any of these problems using the old rc.conf method. My DAEMONS array had the adsl service start after the network service.
I need some help and advice to find out what is causing the problem and how to fix it.
Last edited by bhrgunatha (2012-10-25 05:44:22)Thanks. That seems plausible. So I've been snooping at the journal.
journalctl -ab
Oct 25 17:06:13 starch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
Oct 25 17:06:14 starch systemd[1]: Started Recreate Volatile Files and Directories.
Oct 25 17:06:14 starch systemd[1]: Starting System Initialization.
Oct 25 17:06:14 starch systemd[1]: Reached target System Initialization.
Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printing Service Sockets.
Oct 25 17:06:14 starch systemd[1]: Listening on CUPS Printing Service Sockets.
Oct 25 17:06:14 starch systemd[1]: Starting Console System Startup Logging...
Oct 25 17:06:14 starch systemd[1]: Starting Restore Sound Card State...
Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printer Service Spool.
Oct 25 17:06:14 starch systemd[1]: Started CUPS Printer Service Spool.
Oct 25 17:06:14 starch systemd[1]: Starting D-Bus System Message Bus Socket.
Oct 25 17:06:16 starch ntpd[381]: ntpd [email protected] Tue Aug 21 15:06:24 UTC 2012 (1)
Oct 25 17:06:16 starch ntpd[413]: proto: precision = 0.156 usec
Oct 25 17:06:17 starch ntpd[413]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct 25 17:06:17 starch ntpd[413]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Oct 25 17:06:18 starch ntpd[413]: Listen and drop on 1 v6wildcard :: UDP 123
Oct 25 17:06:18 starch ntpd[413]: Listen normally on 2 lo 127.0.0.1 UDP 123
Oct 25 17:06:18 starch ntpd[413]: Listen normally on 3 lo ::1 UDP 123
Oct 25 17:06:18 starch ntpd[413]: peers refreshed
Oct 25 17:06:18 starch ntpd[413]: Listening on routing socket on fd #20 for interface updates
Oct 25 17:06:18 starch dbus[384]: [system] Activating systemd to hand-off: service name='org.freedesktop.ColorManager' unit='colord.service'
Oct 25 17:06:18 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.systemd1'
Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct 25 17:07:03 starch dbus[384]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
Oct 25 17:07:03 starch systemd[1]: Starting Manage, Install and Generate Color Profiles...
Oct 25 17:07:03 starch systemd[1]: Started Manage, Install and Generate Color Profiles.
Oct 25 17:07:03 starch systemd[1]: colord.service: main process exited, code=killed, status=6
Oct 25 17:07:03 starch systemd[1]: Unit colord.service entered failed state.
Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 25 17:07:04 starch kernel: PPP generic driver version 2.4.2
Oct 25 17:07:04 starch cupsd[380]: Unknown directive DefaultAuthType on line 26.
Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link up
Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 25 17:07:04 starch pppoe-start[382]: TIMED OUT
Oct 25 17:07:04 starch kernel: NET: Registered protocol family 24
Oct 25 17:07:04 starch pppoe-start[382]: /usr/sbin/pppoe-start: line 193: 394 Terminated $CONNECT "$@" > /dev/null 2>&1
That seems to confirm your theory.
eth0 link is not up when attempting to start colord and adsl
So the $64,000 question:
How do I defer them until eth0 is ready?
Or how can I force the eth0 link to be up before colord or adsl try to use it?
Last edited by bhrgunatha (2012-10-25 01:33:36) -
[SOLVED] systemd-modules-load fails
.. because it cannot find gspca. My log:
journalctl -xn
-- Logs begin at Thu 2013-08-22 11:43:18 CEST, end at Mon 2014-06-23 14:26:30 CEST. --
Jun 23 14:25:21 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop7" has new interfaces: ("org.
Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop2" has new interfaces: ("org.
Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop1" has new interfaces: ("org.
Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop0" has new interfaces: ("org.
Jun 23 14:26:19 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop0" lost interfaces: ("org.fre
Jun 23 14:26:30 jiggs systemd[1]: Starting Load Kernel Modules...
-- Subject: Unit systemd-modules-load.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-modules-load.service has begun starting up.
Jun 23 14:26:30 jiggs systemd-modules-load[3138]: Failed to find module 'gspca'
Jun 23 14:26:30 jiggs systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Jun 23 14:26:30 jiggs systemd[1]: Failed to start Load Kernel Modules.
-- Subject: Unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-modules-load.service has failed.
-- The result is failed.
Jun 23 14:26:30 jiggs systemd[1]: Unit systemd-modules-load.service entered failed state.
But I have lots of gspca's:
# ls /lib/modules/`uname -r`/kernel/drivers/media/usb/gspca
gl860 gspca_kinect.ko gspca_ov534.ko gspca_sonixj.ko gspca_sq905c.ko gspca_topro.ko
gspca_benq.ko gspca_konica.ko gspca_pac207.ko gspca_spca1528.ko gspca_sq905.ko gspca_tv8532.ko
gspca_conex.ko gspca_main.ko gspca_pac7302.ko gspca_spca500.ko gspca_sq930x.ko gspca_vc032x.ko
gspca_cpia1.ko gspca_mars.ko gspca_pac7311.ko gspca_spca501.ko gspca_stk014.ko gspca_vicam.ko
gspca_etoms.ko gspca_mr97310a.ko gspca_se401.ko gspca_spca505.ko gspca_stk1135.ko gspca_xirlink_cit.ko
gspca_finepix.ko gspca_nw80x.ko gspca_sn9c2028.ko gspca_spca506.ko gspca_stv0680.ko gspca_zc3xx.ko
gspca_jeilinj.ko gspca_ov519.ko gspca_sn9c20x.ko gspca_spca508.ko gspca_sunplus.ko m5602
gspca_jl2005bcd.ko gspca_ov534_9.ko gspca_sonixb.ko gspca_spca561.ko gspca_t613.ko stv06xx
The only difference I have with respect to a standard installation is that I downloaded an older version of the backport drivers, and in doing so I surely re-installed gspca.
So my questions are: where is systemd-module-load searching for gspca? How can I persuade it to search in the right directory? And in any case, why is it searching for it in the wrong place to start with?. Just in case,
# uname -a
Linux jiggs 3.15.1-1-ARCH #1 SMP PREEMPT Tue Jun 17 09:32:20 CEST 2014 x86_64 GNU/Linux
Last edited by MariusMatutiae (2014-06-26 09:10:22)Problem solved, thanks to both of you guys. For some resason, I had a webcam.conf file in /etc/modules-load.d containing the single line *gspca*, which is not a module: both modprobe and insmod fail, because the correct module name is one of those listed in /lib/modules/`uname -r`/kernel/drivers/media/usb/gspca. They are called gspca_benq.ko gspca_konica.ko and so on. I simply deleted the file since I do not need it.
As for backport drivers: this site, http://drvbp1.linux-foundation.org/~mcg … backports/ has the most recent versions of Linux drivers, backported so that older kernels can install them (I understand this is not a concern for fellow Archers). Whenever I need to upgrade (mostly on Debian) or downgrade (a few times on Arch, because an older version of a driver is free of a newly minted bug) I download these drivers, compile them and install them from source. -
Systemd.timesyncd fails on boot [Solved]
Upgraded systemd to 217-1 and now each boot sees timesyncd fail:
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled)
Active: failed (Result: start-limit) since Fri 2014-10-31 10:25:59 NZDT; 5min ago
Docs: man:systemd-timesyncd.service(8)
Process: 303 ExecStart=/usr/lib/systemd/systemd-timesyncd (code=exited, status=1/FAILURE)
Main PID: 303 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
Oct 31 10:25:59 Shiv systemd[1]: Failed to start Network Time Synchronization.
Oct 31 10:25:59 Shiv systemd[1]: Unit systemd-timesyncd.service entered failed state.
Oct 31 10:25:59 Shiv systemd[1]: systemd-timesyncd.service failed.
Oct 31 10:25:59 Shiv systemd[1]: start request repeated too quickly for systemd-timesyncd.service
Oct 31 10:25:59 Shiv systemd[1]: Failed to start Network Time Synchronization.
Oct 31 10:25:59 Shiv systemd[1]: Unit systemd-timesyncd.service entered failed state.
Oct 31 10:25:59 Shiv systemd[1]: systemd-timesyncd.service failed.
Once I log in, I am able to restart the service without any complaint.
Anyone else seeing this?
# edit: perhaps related to this fixed(?) bug: http://lists.freedesktop.org/archives/s … 03199.htmltl;dr answer:
# sed -i 's/ remote-fs.target$//' /usr/lib/systemd/system/systemd-journal-flush.service
Long answer:
In systemd 217 a few changes were made with regard to ordering of early boot units, resulting in certain setups which used to work with systemd 216 to make problems with systemd 217. The fix above was also applied in systemd upstream by this commit:
commit 919699ec301ea507edce4a619141ed22e789ac0d
Author: Lennart Poettering <[email protected]>
Date: Fri Oct 31 16:22:36 2014 +0100
units: don't order journal flushing afte remote-fs.target
Instead, only depend on the actual file systems we need.
This should solve dep loops on setups where remote-fs.target is moved
into late boot.
For example, in my case, connman.service explicitly requests to be ordered before remote-fs.target, leading to all kinds of fun:
systemd[1]: Found ordering cycle on basic.target/start
systemd[1]: Found dependency on sysinit.target/start
systemd[1]: Found dependency on systemd-tmpfiles-setup.service/start
systemd[1]: Found dependency on systemd-journal-flush.service/start
systemd[1]: Found dependency on remote-fs.target/start
systemd[1]: Found dependency on connman.service/start
systemd[1]: Found dependency on basic.target/start
systemd[1]: Breaking ordering cycle by deleting job systemd-tmpfiles-setup.service/start
systemd-timesyncd[201]: Failed to allocate manager: No such file or directory
systemd[1]: systemd-timesyncd.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start Network Time Synchronization.
systemd[1]: Unit systemd-timesyncd.service entered failed state.
systemd[1]: systemd-timesyncd.service failed.
Explanation:
systemd-journal-flush.service wants to be ordered after remote-fs.target whereas connman.service wants to be ordered before remote-fs.target. Additionally, connman.service requires basic.target. (This is implicit behavior for units which don't declare "DefaultDependencies=no".) This is why basic.target ends up getting pulled in so early in the first place.
Furthermore, systemd-timesyncd.service relies on properly initialized runtime directories in order to work, so it wants to be ordered after systemd-tmpfiles-setup.service.
In order to be able to start basic.target, systemd breaks the ordering cycle by taking systemd-tmpfiles-setup.service out of the transaction, thereby preventing systemd-timesyncd.service from starting up correctly.
Last edited by csn (2014-11-01 22:18:37) -
[SOLVED] systemd: Failed to open private dbus connection
Below is a snapshot from journalctl -b:
systemd[1]: Starting user-1000.slice.
systemd[1]: Created slice user-1000.slice.
systemd[1]: Starting User Manager for 1000...
systemd[1]: Starting Session 1 of user me.
systemd[1]: Started Session 1 of user me.
systemd-logind[195]: New session 1 of user me.
systemd[261]: pam_unix(systemd-user:session): session opened for user me by (uid=0)
systemd[261]: Failed to open private dbus connection: Failed to connect to socet /run/usr/1000/dbususer_bus_socket: No such file or directory
systemd[261]: Mounted /sys/kernel/config.
systemd[261]: Stopped target Bluetooth.
systemd[261]: Stopped target Sound Card.
systemd[261] Starting Default.
systemd[261]: Reached target Default.
systemd[261]: Startup finished in 135ms.
systemd[1]: Started User Manager for 1000.
login[199]: LOGIN ON tty1 BY me
It's a fresh Arch Linux install and I didn't even had a time yet to tinker with systemd so it's unlikely that I've messed things up. I suspect that it might be the cause of the following problem:
$ systemctl status --user
Failed to issue method call: Process /bin/false exited with status 1
For reference, systemd version:
$ systemctl --version
systemd 207
+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
Any ideas how can I solve the private dbus connection problem?
Last edited by vox23 (2013-09-25 17:02:22)65kid wrote:do you actually experience any problems?
I thought that it might be related to:
$ systemctl status --user
Failed to issue method call: Process /bin/false exited with status 1
however when I followed wiki and created:
$cat /etc/systemd/system/[email protected]/environment.conf
[Service]
Environment=DISPLAY=:0
Environment=XDG_RUNTIME_DIR=/run/user/%I
Environment=SHELL=%s
then /bin/false error went away. I still have some problems with systemd managing my user session but unrelated to the above. Marking as solved. -
[SOLVED] Network Manager systemd unit fails after update
EDIT: Reinstalling libnm-glib resolved this issue
After updating to the latest version of NetworkManager (networkmanager-0.9.8.10-3), the systemd unit fails to start. It works fine after downgrading back to the previous version though (networkmanager-0.9.8.10-1). I'm not sure if this is a bug or an error on my end; since the previous package works I've just dowgraded for the time being. For the update that doesn't work, here is the output of "systemctl status" and the systemd journal:
>>sudo systemctl daemon-reload
>> sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: failed (Result: exit-code) since Wed 2014-06-11 15:28:25 EDT; 10s ago
Process: 24073 ExecStart=/usr/bin/NetworkManager --no-daemon (code=exited, status=127)
Main PID: 24073 (code=exited, status=127)
Jun 11 15:28:25 kyle systemd[1]: NetworkManager.service: main process exited, code=exited, status=127/n/a
Jun 11 15:28:25 kyle systemd[1]: Failed to start Network Manager.
Jun 11 15:28:25 kyle systemd[1]: Unit NetworkManager.service entered failed state.
>> journalctl -xn
-- Logs begin at Tue 2014-06-10 12:47:19 EDT, end at Wed 2014-06-11 15:28:36 EDT. --
Jun 11 15:28:25 kyle sudo[24070]: pam_unix(sudo:session): session opened for user root by kyle(uid=0)
Jun 11 15:28:25 kyle systemd[1]: Starting Network Manager...
-- Subject: Unit NetworkManager.service has begun with start-up
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit NetworkManager.service has begun starting up.
Jun 11 15:28:25 kyle systemd[1]: NetworkManager.service: main process exited, code=exited, status=127/n/a
Jun 11 15:28:25 kyle systemd[1]: Failed to start Network Manager.
-- Subject: Unit NetworkManager.service has failed
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit NetworkManager.service has failed.
-- The result is failed.
Jun 11 15:28:25 kyle systemd[1]: Unit NetworkManager.service entered failed state.
Jun 11 15:28:25 kyle sudo[24070]: pam_unix(sudo:session): session closed for user root
Jun 11 15:28:28 kyle dbus[489]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out
Jun 11 15:28:36 kyle sudo[24075]: kyle : TTY=pts/2 ; PWD=/var/cache/pacman/pkg ; USER=root ; COMMAND=/usr/bin/systemctl status NetworkManager
Jun 11 15:28:36 kyle sudo[24075]: pam_unix(sudo:session): session opened for user root by kyle(uid=0)
Jun 11 15:28:36 kyle sudo[24075]: pam_unix(sudo:session): session closed for user root
Last edited by T0k3n (2014-07-03 15:18:01)Check the changes:
https://projects.archlinux.org/svntogit … e192881dc5
https://projects.archlinux.org/svntogit … ee906b6c44
When posting configs, code or command output, please use [ code ] tags, not [ quote ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and - in case of longer listings - more convenient to scroll through. -
[SOLVED][systemd 210] systemd-backlight@.service gets loaded and fails
Hello,
I just updated to 210 and rebooted as soon as possible as advised. The first thing I noticed is the red [Failed] message during startup. After looking at systemctl I noticed that systemd-backlight@backlight:eeepc-wmi.service fails. There are 3 things wrong with this 1) I don't have a backlight this is on a desktop 2) It's not an eeePC 3) I never had any failed services before the update. I tried to disable this service, but the service still tries to start and fails on every boot. I read about systemd-backlight here: http://www.freedesktop.org/software/sys … rvice.html but it doesn't really help much to explain why it tries to load this service in the firstplace. I have not tried masking it, but this would not fix the underlying problem anyway.
The systemctl status doesn't provide any usful information.
systemd-backlight@backlight:eeepc-wmi.service - Load/Save Screen Backlight Brightness of backlight:eeepc/wmi
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
Active: failed (Result: exit-code) since Di 2014-03-04 18:51:41 CET; 20min ago
Docs: man:[email protected](8)
Process: 185 ExecStart=/usr/lib/systemd/systemd-backlight load %I (code=exited, status=1/FAILURE)
Main PID: 185 (code=exited, status=1/FAILURE)
Mär 04 18:51:41 archbox systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:eeepc/wmi...
Mär 04 18:51:41 archbox systemd[1]: systemd-backlight@backlight:eeepc-wmi.service: main process exited, code=exited, status=1/FAILURE
Mär 04 18:51:41 archbox systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:eeepc/wmi.
Mär 04 18:51:41 archbox systemd[1]: Unit systemd-backlight@backlight:eeepc-wmi.service entered failed state.
Regards,
blackout23
Last edited by blackout23 (2014-03-07 01:24:29)You're not alone. I have the same problem, though Google really doesn't show anyone else who does. What's your hardware situation look like?
Here's my lcpci:
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4)
00:1c.4 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 (rev c4)
00:1c.5 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 (rev c4)
00:1c.6 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Z77 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
01:00.0 PCI bridge: PLX Technology, Inc. Device 8747 (rev ba)
02:08.0 PCI bridge: PLX Technology, Inc. Device 8747 (rev ba)
02:10.0 PCI bridge: PLX Technology, Inc. Device 8747 (rev ba)
03:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 680] (rev a1)
03:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)
05:00.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)
06:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio]
07:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire Controller (rev 01)
08:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
09:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
0a:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Last edited by dhaines (2014-03-05 01:37:50) -
[Solved] systemd fails to start spawning /bin/plymouth
Hello all,
I currently can't get my system to boot up, systemd hangs and after a while enters emergency mode.
journalctl -xb
show the following error:
systemd[257]: Failed at step EXEC spwaning /bin/plymouth:
-- Subject: Process /bin/plymouth could not be executed
.. The process /bin/plymouth could not be executed and failed.
-- The error number returned while executing this process is 2.
I am not sure what to make of this, as far as I know plymouth is some splash screen utility which I have never installed. I also can't find any corresponding .service files. I also tried appending plymouth.enable=0 to the kernel command line, to no effect. Does anyone know this problem (since my hardware is currently in a rather shaky state I would not rule out some related error)?
Last edited by x2b (2013-09-11 17:55:32)x2b wrote:I am not sure what to make of this, as far as I know plymouth is some splash screen utility which I have never installed.
Yes, that's plymouth.
I also can't find any corresponding .service files. I also tried appending plymouth.enable=0 to the kernel command line, to no effect. Does anyone know this problem (since my hardware is currently in a rather shaky state I would not rule out some related error)?
Might have something to do with https://bugs.archlinux.org/task/31031 so plymouth should not be the problem.
Edit: I just checked my journal and I could not find any plymouth related messages in there, but I remember seeing those before, too (must have been before february 20th, that's as far back as my journal goes). When did you do your last update?
Last edited by cookies (2013-09-11 13:58:43) -
[SOLVED]systemd-tmpfiles-setup.service fails
Hi,
I have installed arch on an old laptop (dell inspiron 6000). I haven't used arch linux for last 2 years. It seems system management style has changed drastically.
Anyways, systemctl status systemd-tmpfiles-setup.service returns this;
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sal 2015-06-09 11:00:18 EEST; 38min ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 228 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
Main PID: 228 (code=exited, status=1/FAILURE)
Haz 09 11:00:18 yasar-laptop systemd[1]: Starting Create Volatile Files and Directories...
Haz 09 11:00:18 yasar-laptop systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
Haz 09 11:00:18 yasar-laptop systemd[1]: Failed to start Create Volatile Files and Directories.
Haz 09 11:00:18 yasar-laptop systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Haz 09 11:00:18 yasar-laptop systemd[1]: systemd-tmpfiles-setup.service failed.
Is this something that I should be concerned? I don't really know what this service supposed to do?
If I should be concerned, how to troubleshoot it? Keep in mind that this is a fresh arch install.
Last edited by yasar11732 (2015-06-09 16:31:04)Thanks,
I have add acl option to fstab file, it works now. If anyone else has this problem, here is how my fstab file looks now;
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
UUID=936297ec-2bc3-45ef-bdb0-0a4ce7239204 / ext4 rw,relatime,data=ordered 0 1
UUID=d1fd9d31-99b5-45ba-97f4-a4c20b96e48b /var reiserfs rw,relatime,acl 0 2
UUID=6a9b3e39-8ea2-446f-9a71-79faab7cdafe /home xfs rw,relatime,attr2,inode64,noquota 0 2
# UUID=eb0b40d3-43ac-4f1f-8b29-97cd16a534d4
UUID=eb0b40d3-43ac-4f1f-8b29-97cd16a534d4 none swap defaults 0 0 -
[solved] systemd power control doesn't work
Since there is no way of getting systemctl power control work without sudo, I tried modifying sudoers to allow my user to operate them without password.
However, it still won't work.
I tried that
cross ALL = NOPASSWD: /usr/sbin/hibernate,/usr/bin/systemctl suspend,/usr/bin/systemctl reboot,/usr/bin/systemctl suspend,/usr/bin/systemctl hibernate
and I tried that
cross ALL = NOPASSWD: /usr/bin/systemctl
The result was the same:
$ systemctl suspend
Failed to issue method call: Access denied
Failed to issue method call: Access denied
Last edited by impact (2012-11-09 11:28:17)impact wrote:
Since there is no way of getting systemctl power control work without sudo, I tried modifying sudoers to allow my user to operate them without password.
However, it still won't work.
I tried that
cross ALL = NOPASSWD: /usr/sbin/hibernate,/usr/bin/systemctl suspend,/usr/bin/systemctl reboot,/usr/bin/systemctl suspend,/usr/bin/systemctl hibernate
and I tried that
cross ALL = NOPASSWD: /usr/bin/systemctl
The result was the same:
$ systemctl suspend
Failed to issue method call: Access denied
Failed to issue method call: Access denied
you have to use "sudo systemctl suspend" still, sudoers is only affecting sudo behavior as it was mentioned...
nahuy_systemd wrote:systemd very bad system. I solved this. I moved to CRUX.
...and you registered to the forum just to tell us that? well, if I were you, i would either change the doctor or make him prescribe me another pills -
[SOLVED]systemd: help on executing oneshots, timing issues
Hi,
I have problems with systemd. I want to upload a firmware to my bluetooth adapter which needs the device already created by bluetoothd. I made the service file /usr/lib/systemd/system/fw-upload-bcm20702a0.service
Unit]
Description=uploading firmware to BCM20702A0 buetooth adapter
Requires=bluetooth.service
After=bluetooth.service
[Service]
Type=oneshot
ExecStart=/usr/bin/brcm_patchram_plus_usb --patchram /lib/firmware/BCM20702A0_001.001.024.0156.0204.hcd hci0
[Install]
Alias=fw-upload-bcm20702a0.service
WantedBy=graphical.target
Manually executing this after system startup with
systemctl start fw-upload-bcm20702a0.service
works. But during system startup I get this error:
[root@gruenix ~]# systemctl status fw-upload-bcm20702a0.service
fw-upload-bcm20702a0.service - uploading firmware to BCM20702A0 buetooth adapter
Loaded: loaded (/usr/lib/systemd/system/fw-upload-bcm20702a0.service; enabled)
Active: failed (Result: exit-code) since Mo 2013-04-15 10:39:15 CEST; 36s ago
Process: 1273 ExecStart=/usr/bin/brcm_patchram_plus_usb --patchram /lib/firmware/BCM20702A0_001.001.024.0156.0204.hcd hci0 (code=exited, status=1/FAILURE)
Apr 15 10:39:15 gruenix brcm_patchram_plus_usb[1273]: device hci0 could not be found
Apr 15 10:39:15 gruenix brcm_patchram_plus_usb[1273]: option patchram with arg /lib/firmware/BCM20702A0_001.001.024.0156.0204.hcd
Apr 15 10:39:15 gruenix systemd[1]: fw-upload-bcm20702a0.service: main process exited, code=exited, status=1/FAILURE
Apr 15 10:39:15 gruenix brcm_patchram_plus_usb[1273]: hci0
Apr 15 10:39:15 gruenix systemd[1]: Failed to start uploading firmware to BCM20702A0 buetooth adapter.
Apr 15 10:39:15 gruenix systemd[1]: Unit fw-upload-bcm20702a0.service entered failed state
The error indicates that the device hci0 is not created in time. But what else can I do to assure that?
Harvey
Last edited by Harey (2013-08-14 09:49:22)Today I revisited my problem and solved it. Just in case anybody is interested in the solution:
Preface: You need 2 small packages for this to work
1. hex2hcd - converts a hex file extracted from the windows driver package to hcd format
2. brcm_patchram_plus - a tool from broadcom to upload firmware files into the usb adpater
I made to AUR packages for convenience:
https://aur.archlinux.org/packages/?O=0&K=hex2hcd-git
and
https://aur.archlinux.org/packages/brcm … _plus-git/
Then you convert your windows firmware file to hcd format with hex2hcd and store it as /lib/firmware/fw-{vendor_id}_{device_id}.hcd (in my case: /lib/firmware/fw-0489_e031.hcd).
Now for the tricky part part: Create a script like this (improvements and comments welcome):
#!/bin/bash
# BCM20702A0 BT Adapter upload rampatch
# env Variables
logfile=/var/log/rampatch.log
# logfile check
if ! test -f ${logfile} ; then
# logfile does not exist, so create it
touch $logfile
fi
echo "-------------------------------------------------------" >> $logfile
entrytime=$(date +"%Y-%m-%d %H:%M:%S")
echo $entrytime " applying rampatch to BCM20702A0 bluetooth adapter" >> $logfile
# wait for hci0 to become available and usable
sleep 1
/usr/bin/brcm_patchram_plus_usb --patchram /lib/firmware/fw-0489_e031.hcd hci0 >> $logfile
entrytime=$(date +"%Y-%m-%d %H:%M:%S")
echo $entrytime " ..done" >> $logfile
echo "-------------------------------------------------------" >> $logfile
(This one writes to a logfile in /var/log/ for easier debugging)
This has to be triggered by systemd, so we need a service file /etc/systemd/system/loadfw.service:
[Unit]
Description=Load firmware into BCM20702A0 bluetooth USB adapter
After=basic.target
After=suspend.target
After=hibernate.target
[Service]
Type=oneshot
ExecStart=-{put your script location here}start_BCM20702A0.sh
[Install]
WantedBy=basic.target
WantedBy=suspend.target
WantedBy=hibernate.target
Enable it via
systemctl enable loadfw.service
and bazinga - the firmware gets loaded at every boot, suspend and hibernate.
Harvey -
Suspends fails the first time, but succeeds the second time
Hi all,
I am running Arch Linux on my Dell XPS 15 9530 laptop, and overall I am very happy with the combination. I have however had some issues with suspending.
The problem is that the first time I try to suspend the machine it seems to go to sleep, but then two seconds later it automatically wakes up again. If I then immediately try again to suspend, it works (it does not wake up automatically). Does anyone know what could be going on, and how this can be fixed?
Usually I suspend from my gnome 3 desktop, but I have also tried to suspend directly using 'systemctl suspend' without having an X server running, and the result is exactly the same. I have tried a few versions of the vanilla kernel, but also the linux-lts and the linux-ck images, but to no avail.
Here is the output from dmesg, where suspend fails:
PM: Syncing filesystems ... done.
PM: Preparing system for mem sleep
bbswitch: enabling discrete graphics
Freezing user space processes ... (elapsed 0.543 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
sd 1:0:0:0: [sda] Synchronizing SCSI cache
smsc75xx 3-1:1.0 enp0s20u1: entering SUSPEND2 mode
sd 1:0:0:0: [sda] Stopping disk
Removing pn544
PM: suspend of devices complete after 334.544 msecs
PM: late suspend of devices complete after 0.201 msecs
ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
PM: noirq suspend of devices complete after 26.944 msecs
ACPI: Preparing to enter system sleep state S3
PM: Saving platform NVS memory
Disabling non-boot CPUs ...
kvm: disabling virtualization on CPU1
smpboot: CPU 1 is now offline
kvm: disabling virtualization on CPU2
smpboot: CPU 2 is now offline
kvm: disabling virtualization on CPU3
smpboot: CPU 3 is now offline
kvm: disabling virtualization on CPU4
smpboot: CPU 4 is now offline
kvm: disabling virtualization on CPU5
smpboot: CPU 5 is now offline
kvm: disabling virtualization on CPU6
smpboot: CPU 6 is now offline
kvm: disabling virtualization on CPU7
smpboot: CPU 7 is now offline
ACPI: Low-level resume complete
PM: Restoring platform NVS memory
Enabling non-boot CPUs ...
x86: Booting SMP configuration:
smpboot: Booting Node 0 Processor 1 APIC 0x2
kvm: enabling virtualization on CPU1
Intel pstate controlling: cpu 1
CPU1 is up
smpboot: Booting Node 0 Processor 2 APIC 0x4
kvm: enabling virtualization on CPU2
Intel pstate controlling: cpu 2
CPU2 is up
smpboot: Booting Node 0 Processor 3 APIC 0x6
kvm: enabling virtualization on CPU3
Intel pstate controlling: cpu 3
CPU3 is up
smpboot: Booting Node 0 Processor 4 APIC 0x1
kvm: enabling virtualization on CPU4
Intel pstate controlling: cpu 4
CPU4 is up
smpboot: Booting Node 0 Processor 5 APIC 0x3
kvm: enabling virtualization on CPU5
Intel pstate controlling: cpu 5
CPU5 is up
smpboot: Booting Node 0 Processor 6 APIC 0x5
kvm: enabling virtualization on CPU6
Intel pstate controlling: cpu 6
CPU6 is up
smpboot: Booting Node 0 Processor 7 APIC 0x7
kvm: enabling virtualization on CPU7
Intel pstate controlling: cpu 7
CPU7 is up
ACPI: Waking up from system sleep state S3
acpi LNXPOWER:01: Turning OFF
xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
PM: noirq resume of devices complete after 73.424 msecs
PM: early resume of devices complete after 0.091 msecs
mei_me 0000:00:16.0: irq 49 for MSI/MSI-X
snd_hda_intel 0000:00:03.0: irq 50 for MSI/MSI-X
snd_hda_intel 0000:00:1b.0: irq 53 for MSI/MSI-X
mei_me 0000:00:16.0: NFC MEI VERSION: IVN 0x1 Vendor ID 0x1 Type 0x1
Probing NFC pn544
ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
usb 3-1: reset high-speed USB device number 2 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
ata2.00: configured for UDMA/133
sd 1:0:0:0: [sda] Starting disk
usb 3-1: reset high-speed USB device number 2 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
usb 3-1: reset high-speed USB device number 2 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd75180
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd751c0
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd75200
smsc75xx 3-1:1.0 enp0s20u1: resuming from SUSPEND2
usb 3-4: reset full-speed USB device number 3 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
usb 3-4: reset full-speed USB device number 3 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
usb 3-4: reset full-speed USB device number 3 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9ac0
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9a80
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9a40
usb 3-6: reset full-speed USB device number 4 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
usb 3-6: reset full-speed USB device number 4 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
[drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
usb 3-6: reset full-speed USB device number 4 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804174ddc80
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804174ddcc0
usb 3-11: reset high-speed USB device number 6 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
usb 3-11: reset high-speed USB device number 6 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
usb 3-11: reset high-speed USB device number 6 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9480
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9440
usb 3-9: reset full-speed USB device number 5 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
usb 3-9: reset full-speed USB device number 5 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
pciehp 0000:00:1c.0:pcie04: Link Training Error occurs
pciehp 0000:00:1c.0:pcie04: Failed to check link status
dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -19
PM: Device 00:08 failed to resume: error -19
usb 3-9: reset full-speed USB device number 5 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db000
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db040
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db080
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880417451e80
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880417451ec0
PM: resume of devices complete after 2769.054 msecs
PM: Finishing wakeup.
Restarting tasks ...
iwlwifi 0000:06:00.0: no hotplug settings from platform
rtsx_pci 0000:07:00.0: no hotplug settings from platform
done.
Bluetooth: hci0: read Intel version: 370710018002030d00
Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
video LNXVIDEO:00: Restoring backlight state
video LNXVIDEO:01: Restoring backlight state
bbswitch: disabling discrete graphics
ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
smsc75xx 3-1:1.0 enp0s20u1: link down
smsc75xx 3-1:1.0 enp0s20u1: link down
smsc75xx 3-1:1.0 enp0s20u1: kevent 4 may have been dropped
smsc75xx 3-1:1.0 enp0s20u1: link down
smsc75xx 3-1:1.0 enp0s20u1: link down
and here where suspend succeeds:
smsc75xx 3-1:1.0 enp0s20u1: kevent 4 may have been dropped
smsc75xx 3-1:1.0 enp0s20u1: link up, 100Mbps, full-duplex, lpa 0xC5E1
smsc75xx 3-1:1.0 enp0s20u1: link up, 100Mbps, full-duplex, lpa 0xC5E1
PM: Syncing filesystems ... done.
PM: Preparing system for mem sleep
bbswitch: enabling discrete graphics
Freezing user space processes ... (elapsed 0.412 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
sd 1:0:0:0: [sda] Synchronizing SCSI cache
smsc75xx 3-1:1.0 enp0s20u1: entering SUSPEND2 mode
sd 1:0:0:0: [sda] Stopping disk
Removing pn544
PM: suspend of devices complete after 780.265 msecs
PM: late suspend of devices complete after 0.387 msecs
ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
PM: noirq suspend of devices complete after 26.988 msecs
ACPI: Preparing to enter system sleep state S3
PM: Saving platform NVS memory
Disabling non-boot CPUs ...
kvm: disabling virtualization on CPU1
smpboot: CPU 1 is now offline
kvm: disabling virtualization on CPU2
smpboot: CPU 2 is now offline
kvm: disabling virtualization on CPU3
smpboot: CPU 3 is now offline
kvm: disabling virtualization on CPU4
smpboot: CPU 4 is now offline
kvm: disabling virtualization on CPU5
smpboot: CPU 5 is now offline
kvm: disabling virtualization on CPU6
smpboot: CPU 6 is now offline
kvm: disabling virtualization on CPU7
smpboot: CPU 7 is now offline
ACPI: Low-level resume complete
PM: Restoring platform NVS memory
Enabling non-boot CPUs ...
x86: Booting SMP configuration:
smpboot: Booting Node 0 Processor 1 APIC 0x2
kvm: enabling virtualization on CPU1
Intel pstate controlling: cpu 1
CPU1 is up
smpboot: Booting Node 0 Processor 2 APIC 0x4
kvm: enabling virtualization on CPU2
Intel pstate controlling: cpu 2
CPU2 is up
smpboot: Booting Node 0 Processor 3 APIC 0x6
kvm: enabling virtualization on CPU3
Intel pstate controlling: cpu 3
CPU3 is up
smpboot: Booting Node 0 Processor 4 APIC 0x1
kvm: enabling virtualization on CPU4
Intel pstate controlling: cpu 4
CPU4 is up
smpboot: Booting Node 0 Processor 5 APIC 0x3
kvm: enabling virtualization on CPU5
Intel pstate controlling: cpu 5
CPU5 is up
smpboot: Booting Node 0 Processor 6 APIC 0x5
kvm: enabling virtualization on CPU6
Intel pstate controlling: cpu 6
CPU6 is up
smpboot: Booting Node 0 Processor 7 APIC 0x7
kvm: enabling virtualization on CPU7
Intel pstate controlling: cpu 7
CPU7 is up
ACPI: Waking up from system sleep state S3
acpi LNXPOWER:01: Turning OFF
xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
PM: noirq resume of devices complete after 73.411 msecs
PM: early resume of devices complete after 0.097 msecs
mei_me 0000:00:16.0: irq 49 for MSI/MSI-X
snd_hda_intel 0000:00:03.0: irq 50 for MSI/MSI-X
snd_hda_intel 0000:00:1b.0: irq 53 for MSI/MSI-X
mei_me 0000:00:16.0: NFC MEI VERSION: IVN 0x1 Vendor ID 0x1 Type 0x1
Probing NFC pn544
ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
usb 3-4: reset full-speed USB device number 3 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
ata2.00: configured for UDMA/133
sd 1:0:0:0: [sda] Starting disk
usb 3-4: reset full-speed USB device number 3 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
usb 3-4: reset full-speed USB device number 3 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9ac0
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9a80
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9a40
usb 3-1: reset high-speed USB device number 2 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
usb 3-1: reset high-speed USB device number 2 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
usb 3-1: reset high-speed USB device number 2 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd75180
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd751c0
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd75200
smsc75xx 3-1:1.0 enp0s20u1: resuming from SUSPEND2
usb 3-9: reset full-speed USB device number 5 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
usb 3-9: reset full-speed USB device number 5 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
[drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
usb 3-9: reset full-speed USB device number 5 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db000
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db040
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db080
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880417451e80
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880417451ec0
usb 3-6: reset full-speed USB device number 4 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
usb 3-6: reset full-speed USB device number 4 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
usb 3-6: reset full-speed USB device number 4 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804174ddc80
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804174ddcc0
usb 3-11: reset high-speed USB device number 6 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
usb 3-11: reset high-speed USB device number 6 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
pciehp 0000:00:1c.0:pcie04: Link Training Error occurs
pciehp 0000:00:1c.0:pcie04: Failed to check link status
dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -19
PM: Device 00:08 failed to resume: error -19
usb 3-11: reset high-speed USB device number 6 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9480
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9440
PM: resume of devices complete after 2801.389 msecs
PM: Finishing wakeup.
Restarting tasks ...
iwlwifi 0000:06:00.0: no hotplug settings from platform
rtsx_pci 0000:07:00.0: no hotplug settings from platform
done.
Bluetooth: hci0: read Intel version: 370710018002030d00
Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
video LNXVIDEO:00: Restoring backlight state
video LNXVIDEO:01: Restoring backlight state
bbswitch: disabling discrete graphics
ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
systemd[1]: Requested transaction contradicts existing jobs: File exists
systemd[1]: Service sleep.target is not needed anymore. Stopping.
smsc75xx 3-1:1.0 enp0s20u1: kevent 4 may have been dropped
smsc75xx 3-1:1.0 enp0s20u1: link down
smsc75xx 3-1:1.0 enp0s20u1: link down
It seems to me like the only real difference has to do with the xhci_hcd errors, perhaps the following:
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
Any input or help would be highly appreciated.Rexilion wrote:Maybe you could confirm your suspicion by rmmoding xhci before suspend and modprobing it after resume?
Thanks for the response. I should have said so, but I had already tried that, but without any luck. It seems like it doesn't change anything. -
Tip regarding the "systemd[1]: Failed to start Journal Service" error
Just a tip regarding the well-known
systemd[1]: Failed to start Journal Service
error (which I ran into last weekend) to maybe save one or two among you a couple of hours of your time:
The error is described here https://bbs.archlinux.org/viewtopic.php?id=151012 as well as in several other threads in other language boards / in other forums etc. It is usually (as in the linked thread) 'solved' by reinstalling the system - good old Windows magic, also useful when dealing with systemd.
The Problem with this error is that you do not get into your system. Instead, systemd will print you the mentioned "Failed to start Journal Service" error message a couple of million times. There are also no logs that you could retrieve (when booting from a livesystem) and that would give you any helpful hints, since journal is systemd's logging service, old-style system logs are not kept, and the dmesg log doesn't survive the reboot with default settings.
As pointed out in the above mentioned thread, you will see a few more instructive error messages when adding 'emergency' to the kernel line in the bootloader config.
Now there may be plenty of reasons why the systemd journal service might not work. The most common and most annoying, however, appears to be this one:
In this case you will see that the problem actually lies in
systemd[1]: Cannot open /etc/machine-id: No such file or directory
Now, 'man machine-id' reveals that "the /etc/machine-id file contains the unique machine id of the local system that is set during installation. (...) The machine ID is usually generated from a random source (...)". It is obviously perfectly justified to refuse to boot the system because an absolutely insignificant random number is missing. As far as systemd is concerned anyway.
Usually, it seems, the /etc/machine-id is set by /usr/bin/systemd-machine-id-setup during installation or system upgrade. It is not documented anywhere that this is a rather important step and that you should better check if this was or was not actually done before rebooting. Obviously (but for no apparent reasons) systemd fails to run this (or to run this successfully) sometimes.
Also to be recommended: Always retain (back up) your old kernel and initramfs and edit your bootloader config appropriately to be able to boot with your old kernel again ... just to have one or two options left to get back into the system in case of running into an unpleasant surprise from the side of systemd or other packages.
The solution is, obviously, to create this file /etc/machine-id ... You probably want to do that from a livesystem (if you want to try it from the emergency shell, you would need to remount / (i.e. root) as rw and hope that systemd will not punish you for that) by just running the program that was designed for creating this file manually: /usr/bin/systemd-machine-id-setup
http://permalink.gmane.org/gmane.comp.s … devel/7528 states that it might also work with merely creating the file 'touch /etc/machine-id'. Though I didn't try that since I had enough fun with systemd for one week and didn't want to break my system again just to see if that works.Jristz wrote:
ackalker wrote:Sorry for necrobumping this.
Generating the machine-id in a consistent way is very important when working with KVM and containers, where the machine-id can be set for the VM or container. See `man systemd-machine-id-setup`.
Again, _don't_ just put some random UUID in there, especially not in the systemd package install script, this makes provisioning Arch Linux containers a PITA.
If you thing that the way that arch is handlynbg the machine-id is wrong or can be improved, then file a bug.
He already did.
Jristz wrote:Anyway, I thing if reinstalling systemd package or if systemd have a command to reinitialize the machine-id file.
Like so many of your posts, I had to read this a half dozen times before it made any sense. I think you're hinting at the utility that ackalker already pointed out in the post you're replying to. And, if you read the install scriptlet, you wouldn't need to think about whether or not reinstalling would be an option. You would know that it isn't.
Maybe you are looking for
-
Crystal Report print layout error during print preview
Hi Everyone, When I try print preview a marketing document, it will work the first time, and then when I try to print preview again it brings up a window asking me to login into the database with the sa username and password. When putting in the corr
-
A while back I made a gamecenter account that was not associated with an Apple ID, it was with my email, now my gamecenter account IS my Apple ID. I want to delete it and make a new one, but i can't figure out how. Help!
-
Which Airplay speakers are reliable?
I have two Bose SoundLink Air speakers. Often AirPlay can connect, sometimes not. And when not, it's the same for iTunes and for iOS: a long wait and then nothing. I also have a Denon AVR-X4000. Same story. Chance of successful connection is about 4
-
I have created a photoshop web gallery using bridge. I see the thumbs, pages,photos.js and photos.xml file in my folder. I'm using Dreamweaver to creat my webpages. How do I get the gallery viewable or seen on my website. I'm a newbie at this. Please
-
Has anybody been able to use their N78 phones at 3G speed with T-Mobile? I am only able to get Edge. When I insert the AT&T sim I get 3G. Is there any special configuration required for T-Mobile? Solved! Go to Solution.