* [Bug 222310] New: [Intel Panther Lake][btintel_pcie] Bluetooth A2DP playback stalls; HCI packet completion warnings
@ 2026-11-21 15:06 bugzilla-daemon
0 siblings, 0 replies; only message in thread
From: bugzilla-daemon @ 2026-11-21 15:06 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=222310
Bug ID: 222310
Summary: [Intel Panther Lake][btintel_pcie] Bluetooth A2DP
playback stalls; HCI packet completion warnings
Product: Drivers
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: aros@gmx.com
Regression: No
Bluetooth A2DP audio playback fails on an Intel Panther Lake system using the
`btintel_pcie` driver.
The Bluetooth speakers pair and connect successfully. BlueZ reports an
established connection, and PipeWire/WirePlumber correctly discover the device
and create an A2DP output sink using the standard SBC codec.
However, no audio is heard. PipeWire playback clients become stuck: `pw-play`
starts but never completes playback of a short WAV file and must be interrupted
manually.
During the failure, `pw-top` shows both the Bluetooth output sink and the
playback client in the RUNNING state, but neither processes audio:
```
S ID QUANT RATE WAIT BUSY W/Q B/Q ERR FORMAT
R 152 0 0 0.0us 0.0us ??? ??? 0 S16LE 2 48000
bluez_output...
R 265 0 0 0.0us 0.0us ??? ??? 0 S16LE 1 48000 pw-play
```
Other audio devices operate with nonzero quantum and rate values.
WirePlumber also logs repeated Bluetooth transmission-completion warnings:
```
spa.bluez5.sink.media: Missing completion reports for packet
Bluetooth adapter firmware bug?
```
A Bluetooth codec-switching attempt also produced:
```
spa.bluez5: media codec switch ... failed (org.bluez.Error.Failed)
spa.bluez5.device: failed to switch codec (-19)
```
The symptoms suggest a failure to establish or advance the A2DP media
transport. A problem involving `btintel_pcie`, controller firmware, or
Bluetooth transport handling is suspected, although a PipeWire/WirePlumber or
BlueZ issue has not been ruled out.
## Hardware
- Platform: Intel Core Ultra Series 3 (Panther Lake), HP OmniBook 7
- Bluetooth controller: Intel CNVi Bluetooth, PCI ID `8086:e476`, revision `01`
- Subsystem: `8086:0011`
- Kernel driver: `btintel_pcie`
- Bluetooth firmware: `intel/ibt-00a0-01a1-iml.sfi` and
`intel/ibt-00a0-01a1-pci.sfi`
- Firmware version reported during loading: `19-36.26`
- Running firmware timestamp: `2026.36`, build `102163`
- Bluetooth speakers: SVEN MC-30, Bluetooth Classic A2DP, SBC
## Software
- Distribution: Fedora 45
- PipeWire: 1.6.11
- WirePlumber: 1.6.11
- BlueZ: bluez-5.88-1.fc45.x86_64
- Kernel: 7.3.4-300.fc45.x86_64
## Steps to reproduce
1. Boot the system and connect the SVEN MC-30 speakers over Bluetooth.
2. Confirm that BlueZ reports the speakers as connected.
3. Confirm that PipeWire selects the standard SBC A2DP profile (`a2dp-sink`).
4. Set the Bluetooth output sink as the default audio output.
5. Attempt playback:
```
pw-play --target <bluetooth-sink-name>
/usr/share/sounds/alsa/Front_Center.wav
```
6. Observe that no audio is heard and `pw-play` does not finish.
7. Run `pw-top` while playback is stalled.
## Expected behavior
The speakers should play audio using the standard SBC codec. PipeWire should
process audio normally, and `pw-play` should terminate after the WAV file
finishes.
## Actual behavior
- Bluetooth pairing and connection succeed.
- The standard SBC A2DP profile is available and active.
- The Bluetooth audio sink is created and selected.
- Playback is silent.
- `pw-play` never finishes until manually interrupted.
- During the stalled playback, the Bluetooth sink and `pw-play` show `QUANT=0`,
`RATE=0` and no processing activity in `pw-top`.
- WirePlumber has reported missing Bluetooth packet-completion notifications.
## Additional observations
- Disconnecting and reconnecting the speakers through `bluetoothctl` succeeds
but does not resolve the problem.
- Changing sink volume and unmuting the output have no effect.
- Switching from standard SBC to SBC-XQ causes the speakers to become
unresponsive, with their Bluetooth indicator turning red. SBC-XQ may be
unsupported or incorrectly handled by the speakers; this is not necessarily
related to the original failure.
- Returning to standard SBC restores the reported Bluetooth connection and
audio sink, but playback remains broken.
- Intel firmware initialization appears successful in the boot log, including
`Fseq status: Success (0x00)`.
- This is the first attempt to use these speakers with this computer, so no
previously working kernel version is known.
- A clean-boot retest and a cross-device speaker test have not yet been
reported.
## Diagnostic assessment
The problem does not appear to be caused by ordinary application-level audio
routing, volume, or mute configuration.
The Bluetooth output is recognized and the playback client is created, but its
PipeWire processing graph does not advance.
The `Missing completion reports for packet` warnings may indicate a Bluetooth
controller or firmware transport problem. However, these warnings alone do not
prove that the PCIe Bluetooth driver is responsible.
Further investigation may require tracing A2DP media transport acquisition and
HCI packet completion handling in the Intel PCIe Bluetooth driver.
--
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-11-21 15:06 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-21 15:06 [Bug 222310] New: [Intel Panther Lake][btintel_pcie] Bluetooth A2DP playback stalls; HCI packet completion warnings bugzilla-daemon
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.