Bug 216792 - bluetoothd: src/adapter.c:set_device_privacy_complete() Set device flags return status: Invalid Parameters
Summary: bluetoothd: src/adapter.c:set_device_privacy_complete() Set device flags retu...
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-08 21:48 UTC by Erik Quaeghebeur
Modified: 2023-04-06 10:08 UTC (History)
2 users (show)

See Also:
Kernel Version: 5.15.80
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Erik Quaeghebeur 2022-12-08 21:48:23 UTC
I have "Intel Corp. AX200 Bluetooth" in a Lenovo Thinkpad T14 AMD.
Every time I boot, I get the following error in my logs:

bluetoothd: src/adapter.c:set_device_privacy_complete() Set device flags return status: Invalid Parameters

I cannot say whether this has any actual impact, as my bluetooth devices mostly work, but sometimes have issues (disconnecting for a while, not appearing in list of audio devices,…). In any case, it is a message at the error level, so ideally it is fixed.

In context:

kernel: Bluetooth: hci0: Waiting for firmware download to complete
kernel: Bluetooth: hci0: Firmware loaded in 1684355 usecs
kernel: Bluetooth: hci0: Waiting for device to boot
kernel: Bluetooth: hci0: Device booted in 14608 usecs
kernel: Loading firmware: intel/ibt-20-1-3.ddc
kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
[…]
kernel: Bluetooth: hci0: Firmware revision 0.3 build 106 week 39 2022
[…]
bluetoothd[705]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
bluetoothd[705]: src/adapter.c:set_device_privacy_complete() Set device flags return status: Invalid Parameters
kernel: Bluetooth: hci0: Bad flag given (0x2) vs supported (0x1)
Comment 1 Luiz Von Dentz 2022-12-08 22:26:17 UTC
What bluetoothd version is that? I think I fixed a similar problem where we were not checking the supported flags before passing to the kernel.
Comment 2 Erik Quaeghebeur 2022-12-08 22:35:18 UTC
(In reply to Luiz Von Dentz from comment #1)
> What bluetoothd version is that? […]

bluez-5.65

Note You need to log in before you can comment on or make changes to this bug.