Bug 83730

Summary:	Failed to start Load/Save RF Kill Switch Status of rfkill3
Product:	systemd	Reporter:	Michael Biebl <mbiebl>
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED FIXED	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Michael Biebl 2014-09-10 19:20:29 UTC

Version: 215
Bugs-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759489



Since the update from v208 to v215, I get a failing
systemd-rfkill@rfkill3.service service during boot:

systemd-rfkill@rfkill3.service
loaded failed failed    Load/Save RF Kill Switch Status of rfkill3

# journalctl -b | grep rfkill3
Aug 27 17:48:28 pluto systemd-rfkill[676]: Failed to get rfkill device 'rfkill3': No such file or directory
Aug 27 17:48:28 pluto systemd[1]: systemd-rfkill@rfkill3.service: main process exited, code=exited, status=1/FAILURE
Aug 27 17:48:28 pluto systemd[1]: Failed to start Load/Save RF Kill Switch Status of rfkill3.
Aug 27 17:48:28 pluto systemd[1]: Unit systemd-rfkill@rfkill3.service entered failed state.

Interestingly, I don't seem to have a rfkill3 hardware

# ls -al /var/lib/systemd/rfkill/
-rw-r--r--  1 root root    2 Aug 27 17:48 pci-0000:03:00.0:phy0
-rw-r--r--  1 root root    2 Aug 27 17:48 platform-thinkpad_acpi:tpacpi_bluetooth_sw
-rw-r--r--  1 root root    2 Aug 27 17:48 platform-thinkpad_acpi:tpacpi_wwan_sw

# rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: yes
	Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

Comment 1 Michael Biebl 2014-09-15 12:28:16 UTC

If I mask the systemd-rfkill@.service, I'll get the following output after a reboot

# rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
3: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no


Apparently it is the hci0 device, which is failing/goes away, as soon as systemd-rfkill operates on it.

Comment 2 Michael Biebl 2014-09-15 12:35:31 UTC

Digging a bit deeper, it seems, as soon as systemd-rfkill operates on rfkill0 (tpacpi_bluetooth_sw: Bluetooth) the rfkill3 device (hci0: Bluetooth) goes away.

Comment 3 Michael Biebl 2014-09-15 12:50:20 UTC

(In reply to comment #2)
> Digging a bit deeper, it seems, as soon as systemd-rfkill operates on
> rfkill0 (tpacpi_bluetooth_sw: Bluetooth) the rfkill3 device (hci0:
> Bluetooth) goes away.

# rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no <------
	Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
3: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

# /lib/systemd/systemd-rfkill load rfkill0 
libudev: udev_device_new_from_syspath: device 0x7f5ecc47a2d0 has devpath '/devices/platform/thinkpad_acpi/rfkill/rfkill0'
libudev: udev_device_read_db: device 0x7f5ecc47a2d0 filled with db file data

# rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: yes <------
	Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

Comment 4 Lennart Poettering 2014-12-09 00:42:57 UTC

Should be fixed in current git.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.