usbrtl sometimes doesn't reload firmware
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
Jammy |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
[Impact]
The btrtl driver in the 5.15 jammy kernel sometimes doesn't (re-) load firmware which results in the BT adapter running potentially old firmware rather than the current version from /lib/firmware provided by the linux-firmware package.
This will show in logs like so:
Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=dfc6 lmp_ver=0a lmp_subver=d922
Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: unknown IC info, lmp subver d922, hci rev dfc6, hci ver 000a
Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: assuming no firmware upload needed
The driver reads subver from the adapter to determine chip type. But that value is overwritten by a firmware load. In the above case, a firmware was already loaded which returns subver d922 which the driver does not recognize and it therefore won't load new firmware.
[Test Case]
1) Boot machine with USB adapter plugged in.
2) Verify firmware is loaded.
3) Reboot a couple of times and verify that firmware is reloaded every time.
[Where Problems Could Occur]
Limited to Realtek USB bluetooth adapters that use the btrtl driver. Issues could show up as Bluetooth connection/
description: | updated |
no longer affects: | linux-hwe-5.15 (Ubuntu) |
no longer affects: | linux (Ubuntu Focal) |
no longer affects: | linux-hwe-5.15 (Ubuntu Focal) |
no longer affects: | linux-hwe-5.15 (Ubuntu Jammy) |
Changed in linux (Ubuntu Jammy): | |
status: | New → Confirmed |
description: | updated |
description: | updated |
Changed in linux (Ubuntu Jammy): | |
status: | Confirmed → Fix Committed |
This bug is awaiting verification that the linux/5.15.0-83.92 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- jammy-linux' to 'verification- done-jammy- linux'. If the problem still exists, change the tag 'verification- needed- jammy-linux' to 'verification- failed- jammy-linux' .
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!