messages from 2026-11-12 20:37:45 to 2026-11-15 01:20:10 UTC [more...]
[PATCH 00/12] docs: ioctl-number: update entries
2026-11-15 1:19 UTC (15+ messages)
` [PATCH 01/12] docs: ioctl-number: update MM entries
` docs: ioctl-number: update entries
` [PATCH 02/12] docs: ioctl-number: update sound entries
` [PATCH 03/12] docs: ioctl-number: update block entries
` [PATCH 04/12] docs: ioctl-number: update networking entries
` [PATCH 05/12] docs: ioctl-number: update video/fbdev entries
` [PATCH 06/12] docs: ioctl-number: update SCSI entries
` [PATCH 07/12] docs: ioctl-number: update MTD entries
` [PATCH 08/12] docs: ioctl-number: update USB entries
` [PATCH 09/12] docs: ioctl-number: update virtualization entries
` [PATCH 10/12] docs: ioctl-number: update FS entries
` [PATCH 11/12] docs: ioctl-number: update platform entries
` [PATCH 12/12] docs: ioctl-number: update DRM entries
[PATCH 0/4] Bluetooth: qca: Fix WCN3950 power-off
2026-11-14 20:46 UTC (7+ messages)
` [PATCH v2 0/4] Bluetooth: qca: Power off WCN3950
` [PATCH v2 2/4] Bluetooth: qca: Power off after unregistering the HCI device
` [PATCH v2 3/4] Bluetooth: qca: Handle failed power-pulse writes
` [PATCH v2 1/4] Bluetooth: hci_serdev: Track whether the serial port is open
` [v2,1/4] "
` [PATCH v2 4/4] Bluetooth: qca: Power off WCN3950
[PATCH 2/4] Bluetooth: hci_serdev: Track whether the serial port is open
2026-11-14 20:46 UTC (5+ messages)
` [PATCH 0/1] Bluetooth: hci_mrvl: Fix duplicate serdev open/close
` [PATCH 1/1] Bluetooth: hci_mrvl: Leave the serdev port lifetime to hci_serdev
` Bluetooth: hci_mrvl: Fix duplicate serdev open/close
[PATCH RESEND BlueZ] test: functional: retry pairable when Busy
2026-11-14 20:37 UTC (2+ messages)
` [RESEND,BlueZ] "
Hi,,,I am investigating a reproducible Bluetooth SAR initialization warning on an Intel AX201 controller in an ASUS ExpertBook B5402CBA running Gentoo Linux.,,The warning occurs during firmware initialization on both Linux 7.3.3 and 7.3.4:,,```,Bluetooth: hci0: Applying legacy Bluetooth SAR,Bluetooth: hci0: Failed to send sar ddc id:0x0137 (-22),```,,I captured the initial firmware initialization with btmon and confirmed that the controller explicitly rejects Intel DDC Config Write (0xfc8b), ID 0x0137, with HCI status 0x12.,,**Environment**,,- Hardware: Intel AX201 (USB 8087:0026),- Laptop: ASUS ExpertBook B5402CBA,- Kernel: Gentoo Linux 7.3.4-bdsm (also observed on 7.3.3-bdsm),- Bluetooth firmware: 2026.29, build 82200,- Firmware SHA1 reported by controller: 0xd3d4fa22,- CNVi TOP: 0x00080400,- CNVr TOP: 0x01300504,- Intel DDC file: intel/ibt-0040-4150.ddc (symlink to ibt-0040-0041.ddc),,**Confirmed HCI sequence**,,```,DDC ID Payload HCI status,0x0128 18 Success (0x00),0x0129 03 00 Success (0x00),0x0131 06 Success (0x00),0x0132 06 Success (0x00),0x0133 07 Success (0x00),0x0137 06 08 08 Invalid HCI Command Parameters (0x12),```,,The initial DDC configuration file contains only IDs 0x0128 and 0x0129, and both are applied successfully.,,The legacy SAR parameters come from the ACPI BRDS method at:,,```,\_SB.PC00.XHCI.RHUB.HS10,```,,The method reads the Bluetooth SAR values from the ASUS GNVS SystemMemory region. The controller initialization takes the legacy SAR path.,,In `btintel_set_legacy_sar()`, the first three SAR commands succeed. The next command, ID 0x0137 with payload `06 08 08`, is rejected. The function then returns without sending the remaining legacy SAR commands.,,**Questions**,,1. Is legacy SAR DDC ID 0x0137 with a three-byte BR/EDR payload expected to be supported by this AX201 firmware and hardware generation?,2. Are the payload values `06 08 08` valid for this command, or could the rejection indicate incompatible ACPI-provided SAR values?,3. If this rejection is expected for some Intel controllers, should `btintel` check capability or handle the unsupported command differently, while preserving the required radio power restrictions?,4. Could this result in only partial application of the platform's Bluetooth SAR settings?,,The controller finishes initialization and Bluetooth remains usable. I am not claiming that this warning causes the separate intermittent hardware error 0x0c observed on the system.,,I can provide a sanitized btmon capture, relevant DSDT/BRDS excerpts, and kernel initialization logs if useful.,,Thanks for looking into this
2026-11-14 19:08 UTC
[STABLE 6.6] Bluetooth MediaTek controller reset fixes
2026-11-14 17:35 UTC
[PATCH bluez] gatt-client: Fix not emitting MTU on reconnection
2026-11-14 17:00 UTC (2+ messages)
` [bluez] "
[PATCH BlueZ] audio/media: Fix build with --disable-hfp
2026-11-14 16:01 UTC (2+ messages)
` [BlueZ] "
[PATCH BlueZ] client/telephony: Fix missing string.h include
2026-11-14 16:01 UTC (2+ messages)
` [BlueZ] "
[PATCH v10 1/2] Bluetooth: L2CAP: Restrict LE credits to connected CoCs
2026-11-14 6:05 UTC (7+ messages)
` [PATCH v10 2/2] Bluetooth: L2CAP: Keep credits from completing security upgrades
` [PATCH v11 1/2] Bluetooth: L2CAP: Restrict LE credits to connected CoCs
` [v11,1/2] "
` [PATCH v12 1/2] "
` [PATCH v12 2/2] Bluetooth: L2CAP: Keep credits from completing security upgrades
` [PATCH v11 "
[PATCH] Bluetooth: btintel: Don't log unsupported debug features as an error
2026-11-14 3:03 UTC (2+ messages)
` "
[bluetooth-next:master] BUILD SUCCESS da3cc02587c629420603df4395179ec82955c941
2026-11-14 2:58 UTC
[syzbot] [bluetooth?] WARNING in l2cap_chan_le_send_credits
2026-11-13 23:38 UTC
[PATCH BlueZ v6 0/6] bap: Release cached ASEs on ClearConfiguration
2026-11-13 18:24 UTC (8+ messages)
` [PATCH BlueZ v6 1/6] shared/bap: Add bt_bap_foreach_stream and bt_bap_stream_get_rpac
` bap: Release cached ASEs on ClearConfiguration
` [PATCH BlueZ v6 2/6] shared/bap: Update the remote PAC when reusing an ASE
` [PATCH BlueZ v6 3/6] bap: Release cached ASEs on ClearConfiguration of an endpoint
` [PATCH BlueZ v6 4/6] client/player: Add endpoint.clear command
` [PATCH BlueZ v6 5/6] doc/functional-bap: Document clearing a cached configuration
` [PATCH BlueZ v6 6/6] test: functional: Cover "
[PATCH BlueZ v3 0/4] Bearer.LE1: Add ReadRSSI
2026-11-13 18:23 UTC (6+ messages)
` [PATCH BlueZ v3 1/4] org.bluez.Bearer: Add ReadRSSI method
` Bearer.LE1: Add ReadRSSI
` [PATCH BlueZ v3 2/4] adapter: Add btd_adapter_get_conn_info
` [PATCH BlueZ v3 3/4] bearer: Add ReadRSSI method
` [PATCH BlueZ v3 4/4] test: functional: add bearer ReadRSSI test
[PATCH bluez 1/2] shared/gatt-client: Fix init when Service Changed lacks Indicate
2026-11-13 17:08 UTC (4+ messages)
` "
[PATCH v3 0/2] Add struct_offsetofend() for pointer arithmetic
2026-11-13 17:04 UTC (4+ messages)
` [PATCH v3 1/2] overflow: Add offsetofend() variant of struct_offset()
` Add struct_offsetofend() for pointer arithmetic
` [PATCH v3 2/2] treewide: Use struct_offset()
[PATCH v1] Bluetooth: 6lowpan: Always consume the skb in chan_recv_cb
2026-11-13 17:03 UTC (2+ messages)
` [v1] "
[PATCH 1/2] Bluetooth: hci_bcm: Drop CONFIG_PM guards
2026-11-13 17:01 UTC (3+ messages)
` [PATCH 2/2] Bluetooth: btusb: Prevent conditional compilation
` [1/2] Bluetooth: hci_bcm: Drop CONFIG_PM guards
[PATCH bluez v2 0/2] shared/gatt-client: Fix init when Service Changed lacks Indicate
2026-11-13 16:53 UTC (3+ messages)
` [PATCH bluez v2 1/2] "
` [PATCH bluez v2 2/2] unit/test-gatt: Add Service Changed registration tests
[PATCH BlueZ 0/2] cups: Make printer discovery work again
2026-11-13 16:35 UTC (4+ messages)
` [PATCH BlueZ 1/2] cups: Read the IEEE 1284 device ID over SDP
` [PATCH BlueZ 2/2] cups: Port printer discovery to the ObjectManager API
[PATCH BlueZ v2 0/4] Bearer.LE1: Add ReadRSSI
2026-11-13 16:33 UTC (7+ messages)
` [PATCH BlueZ v2 1/4] org.bluez.Bearer: Add ReadRSSI method
` Bearer.LE1: Add ReadRSSI
` [PATCH BlueZ v2 2/4] adapter: Add btd_adapter_get_conn_info
` [PATCH BlueZ v2 3/4] bearer: Add ReadRSSI method
` [PATCH BlueZ v2 4/4] test: functional: add bearer ReadRSSI test
[BUG] Bluetooth: L2CAP: slab-use-after-free reading chan->sdu->len after the receive callback has consumed the SDU (seen on 7.3.1)
2026-11-13 16:32 UTC (6+ messages)
` [PATCH] Bluetooth: L2CAP: clear the SDU before the receive callback
[PATCH v6 1/2] Bluetooth: btintel: Add TOP silent reset hooks
2026-11-13 14:16 UTC (5+ messages)
` [PATCH v6 2/2] Bluetooth: btintel_pcie: Add TOP silent reset support
` [v6,1/2] Bluetooth: btintel: Add TOP silent reset hooks
[syzbot] [mm?] [bluetooth?] BUG: unable to handle kernel NULL pointer dereference in __refill_objects_node
2026-11-13 13:57 UTC (4+ messages)
[PATCH v2 00/19] driver core: Authorize device trust before driver binding
2026-11-13 11:30 UTC (3+ messages)
` [PATCH v2 11/19] driver core: Introduce a generic device trust level
[PATCH BlueZ] bearer: Fix LE Disconnect for devices with a random address
2026-11-13 10:57 UTC (2+ messages)
` [BlueZ] "
[RFC PATCH BlueZ 1/1] advertising: Fix double-free in client_free
2026-11-13 9:27 UTC (2+ messages)
` [PATCH BlueZ v2] "
[PATCH net] 6lowpan: fix netdev_priv() type confusion in lowpan_event()
2026-11-13 4:32 UTC (3+ messages)
[PATCH BlueZ v5 0/6] bap: Release cached ASEs on ClearConfiguration
2026-11-13 3:42 UTC (8+ messages)
` [PATCH BlueZ v5 1/6] shared/bap: Add bt_bap_foreach_stream and bt_bap_stream_get_rpac
` bap: Release cached ASEs on ClearConfiguration
` [PATCH BlueZ v5 2/6] shared/bap: Update the remote PAC when reusing an ASE
` [PATCH BlueZ v5 3/6] bap: Release cached ASEs on ClearConfiguration of an endpoint
` [PATCH BlueZ v5 4/6] client/player: Add endpoint.clear command
` [PATCH BlueZ v5 5/6] doc/functional-bap: Document clearing a cached configuration
` [PATCH BlueZ v5 6/6] test: functional: Cover "
[RFC PATCH BlueZ 1/1] advertising: Fix double-free in client_free
2026-11-13 3:33 UTC (2+ messages)
` "
[bluetooth-next:master] BUILD SUCCESS c9644a9257d15b27882f4afb36c0341f81f8f35b
2026-11-13 0:24 UTC
[PATCH] Bluetooth: btusb: Wait for setup to finish before system sleep
2026-11-12 22:35 UTC (4+ messages)
` "
[RFC PATCH RESEND] asha: Defer BR/EDR inquiry while streaming
2026-11-12 21:42 UTC (5+ messages)
` [RFC PATCH v2] "
` [RFC PATCH v3] "
[PATCH v3] Bluetooth: mgmt: drop advertising instances the controller cannot carry
2026-11-12 21:25 UTC (2+ messages)
` [v3] "
[PATCH] Bluetooth: btusb: Add QCA Rome support for Surface Laptop 3 AMD (0cf3:e303)
2026-11-12 21:23 UTC (2+ messages)
` "
page: | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox