From: Simon Mikuda <simon.mikuda@streamunlimited.com>
To: linux-bluetooth@vger.kernel.org
Cc: Simon Mikuda <simon.mikuda@streamunlimited.com>
Subject: [PATCH BlueZ] bap: Reset broadcast source stream when ISO io is lost
Date: Sun, 22 Nov 2026 12:50:02 +0100 [thread overview]
Message-ID: <20261122115002.1064419-1-simon.mikuda@streamunlimited.com> (raw)
When a broadcast source transport is released while its ISO connect is
in flight, the late callback still moves the stream to STREAMING and
the io closes right after. Nothing resets the stream, so every later
Acquire() fails with "Request Acquire Reply Input/output error" and the
broadcast shows as active with no BIG on air, until bluetoothd
restarts.
Move such a stream back to CONFIG.
Steps to reproduce:
1. Start and stop a broadcast source (a PipeWire BAP broadcast sink
node) a few times in quick succession.
2. The broadcast shows as active, but nothing is on air, and stopping
and starting it again doesn't help until bluetoothd restarts.
Assisted-by: Claude:claude-opus-5-5
---
profiles/audio/bap.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/profiles/audio/bap.c b/profiles/audio/bap.c
index 457ba5de8..0731e1f23 100644
--- a/profiles/audio/bap.c
+++ b/profiles/audio/bap.c
@@ -2919,6 +2919,13 @@ static void setup_io_disconnected(int cond, void *user_data)
setup_io_close(setup, NULL);
+ if (bt_bap_pac_get_type(setup->ep->lpac) == BT_BAP_BCAST_SOURCE &&
+ bt_bap_stream_get_state(setup->stream) ==
+ BT_BAP_STREAM_STATE_STREAMING) {
+ DBG("stream %p: io lost while streaming", setup->stream);
+ bt_bap_stream_disable(setup->stream, false, NULL, NULL);
+ }
+
bap_update_cigs(setup->ep->data);
}
base-commit: 1adfe662efeff12997df9ddd0960dbd0de9c8ea7
--
2.43.0
next reply other threads:[~2026-11-22 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-22 11:50 Simon Mikuda [this message]
2026-11-22 18:40 ` [BlueZ] bap: Reset broadcast source stream when ISO io is lost bluez.test.bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261122115002.1064419-1-simon.mikuda@streamunlimited.com \
--to=simon.mikuda@streamunlimited.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox