Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#74860 - Unkillable process when connecting to an unreachable Bluetooth device

Attached to Project: Arch Linux
Opened by Peter Sutton (foxxy) - Thursday, 26 May 2022, 19:50 GMT
Last edited by Toolybird (Toolybird) - Friday, 29 July 2022, 05:23 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When I attempt to connect to an unreachable Bluetooth device, the process becomes unkillable (kill -9 doesn't work) and I have to use SysReq to get the system to reboot. Sometimes I can rmmod btusb and then the process terminates.

This bug surfaced about 6m to 1yr ago, disappeared for a month or two and now is back. I've attached an example C program that causes the issue.

$ gcc -lbluetooth example.c && ./a.out # Then try ^C the program

I'm a noob when reporting this type of bugs. I've attached some parts of dmesg that look relevant. Let me know what else you need.

I've got a Intel(R) Dual Band Wireless AC 8260, REV=0x201
   example.c (0.4 KiB)
   dmesg.log (16.8 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Friday, 29 July 2022, 05:23 GMT
Reason for closing:  Upstream
Comment by Peter Sutton (foxxy) - Friday, 17 June 2022, 09:06 GMT
We found the issue and reported upstream. https://marc.info/?l=linux-bluetooth&m=165391099701107&w=2
Comment by Toolybird (Toolybird) - Friday, 29 July 2022, 05:23 GMT
Great that you found the issue. Hopefully upstream has fixed it? There is not much Arch can do here, so if it's still an issue then please keep liaising with upstream to try and get a resolution.

Loading...