Unit systemd-rfkill.service fails after update

English Install/Boot/Login
1

Greetings,

Maybe someone have encountered a similar problem. Today after updates at boot systemd-rfkill.service fails. In system logs I see:

systemd[1]: Starting Load/Save RF Kill Switch Status…
systemd-rfkill[982]: Read event structure of invalid size.
systemd[1]: systemd-rfkill.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: systemd-rfkill.service: Failed with result ‘exit-code’.
systemd[1]: Failed to start Load/Save RF Kill Switch Status.
systemd[1]: Starting Load/Save RF Kill Switch Status…
systemd-rfkill[1136]: Read event structure of invalid size.
systemd[1]: systemd-rfkill.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: systemd-rfkill.service: Failed with result ‘exit-code’.
systemd[1]: Failed to start Load/Save RF Kill Switch Status.

But after my system boots up and I restart systemd-rfkill.service (sudo systemctl restart systemd-rfkill.service) then it doesn’t fail. After a while it enters into [FONT=arial]inactive (dead) state, but it might be a normal behaviour.
[/FONT]
My system:

Operating System: openSUSE Tumbleweed 20210307
KDE Plasma Version: 5.21.1
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.11.2-1-default
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz
Memory: 15,0 GiB of RAM
Graphics Processor: Mesa DRI Intel® UHD Graphics 620

Anyone having similar problem? Any suggestions? Thank you :slight_smile:

2

A bug report has been filed, feel free to add a comment: https://bugzilla.opensuse.org/show_bug.cgi?id=1183147

Gene

3

Nice, Thank you :slight_smile:

4

I’m getting the same , and this, also - note for systemd-rfkill.SOCKET

sudo systemctl status systemd-rfkill.socket
● systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch
     Loaded: loaded (/usr/lib/systemd/system/systemd-rfkill.socket; static)
     Active: failed (Result: service-start-limit-hit) since Wed 2021-03-10 09:25:24 GMT; 44min ago
   Triggers: ● systemd-rfkill.service
       Docs: man:systemd-rfkill.socket(8)
     Listen: /dev/rfkill (Special)

Mar 10 09:25:20 laptop systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Mar 10 09:25:24 laptop systemd[1]: systemd-rfkill.socket: Failed with result 'service-start-limit-hit'.

a (very brief) search around for " Failed with result ‘service-start-limit-hit’." seems to suggest that either a folder is missing, has the wrong permissions, or is still mounted read-only at that point during the boot process

So this could be an underlying reason - but I stress, I’ve not done any digging around to confirm this

Regards

5

The service fails with a different error message on my system:


 sudo systemctl status systemd-rfkill
● systemd-rfkill.service - Load/Save RF Kill Switch Status
     Loaded: loaded (/usr/lib/systemd/system/systemd-rfkill.service; static)
     Active: failed (Result: exit-code) since Wed 2021-03-10 12:28:08 PST; 14min ago
TriggeredBy: ● systemd-rfkill.socket
       Docs: man:systemd-rfkill.service(8)
    Process: 11478 ExecStart=/usr/lib/systemd/systemd-rfkill (code=exited, status=1/FAILURE)
   Main PID: 11478 (code=exited, status=1/FAILURE)
      Error: 5 (Input/output error)

Also, I noticed that I need to restart the service after resume from suspend to RAM to get it running again.

Gene

6

Hi Gene

That’s why I specified systemd-rfkill.socket

If you just do

sudo systemctl status systemd-rfkill

it will tell you about systemd-rfkill.service by default

You’ll find there is a systemd-rfkill.socket as well

I’m not sure which one starts up (or tries to start up) first

7

Actually, I am - I just wasn’t paying attention


sudo systemctl status systemd-rfkill.service

● systemd-rfkill.service - Load/Save RF Kill Switch Status
     Loaded: loaded (/usr/lib/systemd/system/systemd-rfkill.service; static)
     Active: failed (Result: exit-code) since Thu 2021-03-11 08:01:01 GMT; 14min ago
TriggeredBy: ● systemd-rfkill.socket
       Docs: man:systemd-rfkill.service(8)
    Process: 1166 ExecStart=/usr/lib/systemd/systemd-rfkill (code=exited, status=1/FAILURE)
   Main PID: 1166 (code=exited, status=1/FAILURE)
      Error: 5 (Input/output error)

systemd-rfkill.service appears to be triggered by systemd-rfkill.socket - which has already failed

8

Today’s systemd update has resolved this.


2021-03-18 15:37:50 | install | openSUSE-release | 20210317-915.1
2021-03-18 15:37:49 | install | systemd | 246.11-1.1

> journalctl -b -p err # Imediately after booting.
-- Logs begin at Mon 2021-02-08 10:34:29 PST, end at Thu 2021-03-18 17:21:24 PDT. --
Mar 18 15:41:52 Mobile-PC kernel: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
Mar 18 15:42:04 Mobile-PC lightdm[1714]: gkr-pam: unable to locate daemon control file

Gene