* [Bug 222120] New: Intel CNVi: Wi-Fi roam drops active Bluetooth audio, ACL stays up (8086:e440 / 8086:e476)
@ 2026-10-12 10:02 bugzilla-daemon
0 siblings, 0 replies; only message in thread
From: bugzilla-daemon @ 2026-10-12 10:02 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=222120
Bug ID: 222120
Summary: Intel CNVi: Wi-Fi roam drops active Bluetooth audio,
ACL stays up (8086:e440 / 8086:e476)
Product: Drivers
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: nanericwang@gmail.com
Regression: No
Hardware
00:14.3 Wi-Fi [8086:e440] iwlwifi
firmware 106.c88d33af.0 sc-a0-wh-b0-c106.ucode (iwlmld)
00:14.7 Bluetooth [8086:e476] btintel_pcie
Headset: EDIFIER ClearCall 200, 0C:AE:BD:D3:B9:40
A2DP (SBC XQ) and HFP. The device stayed connected.
Software
Linux 7.2.9-2-cachyos (CachyOS build of tag cachyos-7.2.9-2)
BlueZ 5.87, PipeWire 1.6.9
Bluetooth firmware: intel/ibt-00a0-01a1-pci.sfi
version 214-29.26, timestamp 2026.29 build 96982, SHA1 0x239ed887
Audio was playing. Wi-Fi roamed. The A2DP and SCO transports went idle.
bluetoothd logged nothing. btintel_pcie logged nothing. PipeWire then
printed:
spa.bluez5: Failure in Bluetooth audio transport .../sep1/fd0
pw.node: (bluez_output....) running -> error (Received error event)
That PipeWire line is what it prints when an A2DP sink that was already
running leaves the active state.
Local time 2026-10-12, UTC+8. wlp0s20f3 lines are
"disconnect from AP <bssid> for new auth to <bssid>", all under 20:df:73.
16:00:38 roam
16:00:54 A2DP sep1/fd0 dies
16:00:55 roam
16:01:12 roam
16:01:32 SCO fd49 dies
16:01:38 A2DP sep1/fd0 dies again
16:01:46 roam
From 15:44 to 16:02 the same ESS roamed nine times. Those three audio
failures are inside that window.
btintel_pcie has no path that tears down A2DP or SCO because iwlwifi
roamed. The ACL stayed up. The controller dropped the audio channel
while Wi-Fi was using the radio.
Boot log, separate from the drop. DSBR was applied. Bluetooth still
came up. The .ddc file is 16 bytes. The first record is ID 0x0128,
value 0x18. btintel_load_ddc_config() sends HCI 0xfc8b and returns on
the first error, so ID 0x0126 is never sent. The caller ignores the
error.
Bluetooth: hci0: dsbr: enable: 0x01 value: 0x0b
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-00a0-01a1-pci.ddc
Bluetooth: hci0: Failed to send Intel_Write_DDC (-95)
This is not Launchpad 2088151. That one is Write_DDC -16, then hardware
error 0x0f, on intel/ibt-0093-0291.ddc.
Same PCI id, different bug: kernel bug 221346 is a shutdown hang in
synchronize_irq().
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-10-12 10:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-10-12 10:02 [Bug 222120] New: Intel CNVi: Wi-Fi roam drops active Bluetooth audio, ACL stays up (8086:e440 / 8086:e476) bugzilla-daemon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox