Update kernel 3.17.1-1 + bluetooth fails cause?correlate?coincidence?

cfr · 2014-10-23 02:48:25

I just updated Arch which brought the kernel to 3.17.1-1. On reboot, I got a failure from the rfkill unblocking service.

$ systemctl --failed
  UNIT                           LOAD   ACTIVE SUB    DESCRIPTION
● systemd-rfkill@rfkill0.service loaded failed failed Load/Save RF Kill Switch Status of rfkill0

$ systemctl status systemd-rfkill\@* 
● systemd-rfkill@rfkill0.service - Load/Save RF Kill Switch Status of rfkill0
   Loaded: loaded (/usr/lib/systemd/system/systemd-rfkill@.service; static)
   Active: failed (Result: exit-code) since Iau 2014-10-23 03:10:22 BST; 16min ago
     Docs: man:systemd-rfkill@.service(8)
  Process: 1004 ExecStart=/usr/lib/systemd/systemd-rfkill load %I (code=exited, status=1/FAILURE)
 Main PID: 1004 (code=exited, status=1/FAILURE)

Hyd 23 03:10:22 MyMachine systemd[1]: systemd-rfkill@rfkill0.service: main process exited, code=exited, status=1/FAILURE
Hyd 23 03:10:22 MyMachine systemd[1]: Failed to start Load/Save RF Kill Switch Status of rfkill0.
Hyd 23 03:10:22 MyMachine systemd[1]: Unit systemd-rfkill@rfkill0.service entered failed state.

● systemd-rfkill@rfkill1.service - Load/Save RF Kill Switch Status of rfkill1
   Loaded: loaded (/usr/lib/systemd/system/systemd-rfkill@.service; static)
   Active: active (exited) since Iau 2014-10-23 03:10:22 BST; 16min ago
     Docs: man:systemd-rfkill@.service(8)
  Process: 1003 ExecStart=/usr/lib/systemd/systemd-rfkill load %I (code=exited, status=0/SUCCESS)
 Main PID: 1003 (code=exited, status=0/SUCCESS)

Hyd 23 03:10:22 MyMachine systemd[1]: Started Load/Save RF Kill Switch Status of rfkill1.

● systemd-rfkill@rfkill2.service - Load/Save RF Kill Switch Status of rfkill2
   Loaded: loaded (/usr/lib/systemd/system/systemd-rfkill@.service; static)
   Active: active (exited) since Iau 2014-10-23 03:10:22 BST; 16min ago
     Docs: man:systemd-rfkill@.service(8)
  Process: 1002 ExecStart=/usr/lib/systemd/systemd-rfkill load %I (code=exited, status=0/SUCCESS)
 Main PID: 1002 (code=exited, status=0/SUCCESS)

Hyd 23 03:10:22 MyMachine systemd[1]: Started Load/Save RF Kill Switch Status of rfkill2.

Given anything failed, I'm not surprised it is the bluetooth since I had a lot of issues with bluetooth when I first got the laptop:

$ rfkill list
1: tpacpi_bluetooth_sw: Bluetooth
        Soft blocked: yes
        Hard blocked: yes
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

Nonetheless, I have gotten somewhat used to bluetooth working as it has been completely unproblematic for a long time. I rather assumed that some combination of firmware, kernel and/or driver updates had fixed whatever issues afflicted it originally.

If necessary, I can try resetting the firmware to defaults. However, this has two disadvantages. The first is that it will wipe my EFI boot entries (not a big deal but annoying). The second is that it has a less than even chance of working. (That is, all the annoyance but no benefit.)

As usual, the software thinks that the switch is blocked as can be seen in the journal:

thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked

It therefore quite sensibly decides that bluetooth.target is unneeded and proceeds to disable it. Trying

# echo 1 >| /sys/devices/platform/thinkpad_acpi/bluetooth_enable

fails:

-bash: echo: write error: Operation not permitted

Any suggestions for fruitful avenues of investigation would be greatly appreciated. I admit that I have never really understood what is going on: I didn't understand why it worked and failed randomly, and then I didn't understand why it mysteriously started working so reliably and now I don't understand why I am back at square -1.

Arch Linux

#1 2014-10-23 02:48:25

Update kernel 3.17.1-1 + bluetooth fails cause?correlate?coincidence?

Board footer