Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. 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#52214 - [linux-firmware] Bluetooth mouse only works for a few seconds after controller init

Attached to Project: Arch Linux
Opened by Jan Steffens (heftig) - Tuesday, 20 December 2016, 13:54 GMT
Last edited by Jan Steffens (heftig) - Wednesday, 21 December 2016, 18:09 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Laurent Carlier (lordheavy)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

My bluetooth mouse only works for a few seconds after the bt controller initializes. At first, it seems only its "frame rate" is reduced drastically, then it completely stops working. It also makes pairing nearly impossible. "hciconfig hci0 reset" briefly gets the mouse working again.

Firmware revision "0.0 build 95 week 37 2016" from [testing]/linux-firmware 20161205.91ddce4-1 is broken.
Firmware revision "0.0 build 30 week 18 2016" from [core]/linux-firmware 20161005.9c71af9-1 works fine.

The driver will only print the version if a firmware is already loaded, so after a complete power-off (to clear the firmware) btusb has to be unloaded and reloaded in order to print the version.

Kernel is linux-zen 4.8.14-1.

Hardware:
Intel Wireless 8260
Logitech MX Master
This task depends upon

Closed by  Jan Steffens (heftig)
Wednesday, 21 December 2016, 18:09 GMT
Reason for closing:  Upstream
Comment by Jan Steffens (heftig) - Tuesday, 20 December 2016, 15:29 GMT
These messages are new with the broken firmware:

Bluetooth: hci0: Failed to send Intel_Write_DDC (-22)
Bluetooth: hci0 urb ffff880832248240 failed to resubmit (2)

As well as quite a few repeats of

Bluetooth: hci0 command 0x200c tx timeout

Comment by Jan Steffens (heftig) - Wednesday, 21 December 2016, 17:54 GMT
The "failed to resubmit" message seems to be a consequence of unloading the driver, never mind.

The failed DDC write is interesting, though.
Comment by Jan Steffens (heftig) - Wednesday, 21 December 2016, 18:09 GMT

Loading...