You are not logged in.
Fresh install of Arch, not even 24 hours
Kernel: x86_64 Linux 4.20.10-arch1-1-ARCH
systemd: 241 (241.0-1-arch)
My bit older-ish inspiron-3541 laptop after going to suspension or sleeping, it refuses to start most if not all services after resuming
The journalctl says the following:
febr 21 16:41:38 inspiron-3541 systemd[1]: NetworkManager-dispatcher.service: Failed to set invocation ID for unit: File exists
febr 21 16:41:38 inspiron-3541 systemd[1]: Failed to start Network Manager Script Dispatcher Service.Showed NetworkManager-dispatcher now, but it says the same about tty, gnome-terminal, sleep.target and even shutdown/reboot too
Tried looking for this specific error message, with no success
Most relevant result said it's a bug in systemd that was supposed to be fixed in systemd 240
I have the same kernel and systemd on a desktop computer, but that doesn't show these errors
Offline
Welcome to the arch linux forums Hunman does the system's CPU support RDRAND?
lscpu | grep --color rdrandOnline
Thank you, it says it does
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt topoext perfctr_nb bpext ptsc perfctr_llc hw_pstate ssbd vmmcall bmi1 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale flushbyasid decodeassists pausefilter pfthreshold overflow_recov
Offline
Can you link to the previous bug reports you found? I can see where the error message is coming from https://github.com/systemd/systemd/blob … it.c#L4974
but not why there is a collision.
Online
I've found these at various places:
https://github.com/systemd/systemd/issues/5236
https://github.com/Angristan/OpenVPN-install/issues/77
https://bugzilla.altlinux.org/show_bug.cgi?id=34550
https://bugs.debian.org/921267
They all say "Failed to set invocation ID", but with the excaption of the last one, it didn't say "File exists"
Offline
The first three reports are all from a different warning https://github.com/systemd/systemd/blob … it.c#L3488
The debian bug report may be the same issue with the error coming from
https://github.com/systemd/systemd/blob … it.c#L4998 or
https://github.com/systemd/systemd/blob … it.c#L3563 (I missed this call in my first look through the code)
Online
I think I have a similar issue. After suspend the sound stop working. Also when I try to shutdown (only if I suspend before) I get "A stop job is running for session c1 of user...", one or two minutes later the shutdown fails.
Offline
Yeah, that's what happens to me and then in the end it says failed to start shutdown.
When you check your journal, with this command (-r for reverse order), can you see something like this somewhere in red?
journalctl -rfebr 21 15:01:41 inspiron-3541 systemd[1]: sleep.target: Failed to set invocation ID for unit: File exists
After looking through the SystemD sourcecode, it seems the "File exists" part comes from here:
https://github.com/systemd/systemd/blob … ror.c#L138
Offline
I would suggest either trying using Arch_Linux_Archive#How_to_restore_all_packages_to_a_specific_date to downgrade the system to when
systemd 240 was in the repositories to see if it is a new issue with 241 or report the issue upstream https://github.com/systemd/systemd/issues
Edit:
If you run systemctl daemon-reload either before or after suspend does that trigger the error messages?
Last edited by loqs (2019-02-21 20:05:23)
Online
Downgraded to two versions
February 1st - systemd version 240.34-3
Problem persisted (didn't see the daemon-reload edit yet)
January 1st - systemd version 239.370-1
Problem was not present
Tried with daemon-reload first, then without it after a reboot
Could suspend and reawaken repeatedly without a problem
The rebooting right after upgrading from 239.370-1 to 241.7-2 already resulted in a "Failed to start Shutdown" error
daemon-reload didn't work on 241
Last edited by Hunman (2019-02-21 21:34:17)
Offline
Yeah, that's what happens to me and then in the end it says failed to start shutdown.
When you check your journal, with this command (-r for reverse order), can you see something like this somewhere in red?
journalctl -rjournalctl wrote:febr 21 15:01:41 inspiron-3541 systemd[1]: sleep.target: Failed to set invocation ID for unit: File exists
After looking through the SystemD sourcecode, it seems the "File exists" part comes from here:
https://github.com/systemd/systemd/blob … ror.c#L138
Yes, I have that line.
Offline
Offline
@Ignacc could you forward https://bugzilla.kernel.org/show_bug.cgi?id=85911 to linux-crypto@vger.kernel.org with a CC to tytso@mit.edu ?
To ensure the kernel developers are aware it is still an issue and to consider disabling RDRAND on affected hardware until it can be fixed.
Edit:
Theodore Ts'o is aware so no point in emailing him.
Does the patch from https://github.com/systemd/systemd/issu … -490284361 work for you?
Last edited by loqs (2019-05-08 00:40:58)
Online