Process unkillable when connecting to unreachable BT device

foxxy · 2022-05-16 08:45:12

When connecting to an unreachable Bluetooth device, the process hangs. SIGKILL doesn't work, the syscall is hung trying to connect. I have to SysRq to force a reboot. The software ran fine for years without this issue. It appeared 6 months ago, disappeared for a month, and has reappeared. Here's a Python program that causes the issue:

import socket

with socket.socket(family=socket.AF_BLUETOOTH,
                   proto=socket.BTPROTO_RFCOMM) as sock:
    print('Connecting, try ^C')
    sock.connect(('00:18:E4:40:00:06', 1))

I get the same issue with a C program, so I don't think it's to do with user-land software. I don't know where is best or how to report this issue, so I've put it here.

Sometimes I can `sudo rmmod btusb` and then `^C` works, but this is above 50/50.

Last edited by foxxy (2022-05-16 08:51:25)

seth · 2022-05-16 12:28:48

https://stackoverflow.com/questions/767 … s-on-linux
https://unix.stackexchange.com/question … te-process

https://docs.python.org/3/library/socke … settimeout or https://docs.python.org/3/library/socke … etblocking ?

Alternatively does altering the supervision timeout help?
https://stackoverflow.com/questions/249 … s-on-linux

foxxy · 2022-05-17 09:54:57

Thanks seth. I tried all linked suggestions, sadly they didn't help. I'm going to try the LTS kernel to see if that has the issue.

Arch Linux

#1 2022-05-16 08:45:12

Process unkillable when connecting to unreachable BT device

#2 2022-05-16 12:28:48

Re: Process unkillable when connecting to unreachable BT device

#3 2022-05-17 09:54:57

Re: Process unkillable when connecting to unreachable BT device

Board footer