From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 80791] "Bluetooth: hci0: ACL packet for unknown connection handle" must be hidden behind "debug"
Date: Mon, 03 Aug 2026 08:25:01 +0000 [thread overview]
Message-ID: <bug-80791-62941-8xCXt1KPiU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-80791-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=80791
webcaptcha (webcapcha@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |webcapcha@gmail.com
--- Comment #15 from webcaptcha (webcapcha@gmail.com) ---
Do we have any updates on this?
I have notificattions on journal errors and this spam me so bad. Every 30
seconds or so I get a notification.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2026-08-03 8:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-80791-62941@https.bugzilla.kernel.org/>
2014-07-26 20:40 ` [Bug 80791] Lot of "hci0 sco packet for unknown connection handle" bugzilla-daemon
2023-09-05 10:06 ` bugzilla-daemon
2023-09-05 10:06 ` bugzilla-daemon
2023-09-05 10:09 ` bugzilla-daemon
2023-09-05 10:09 ` bugzilla-daemon
2023-09-05 10:12 ` bugzilla-daemon
2023-09-05 10:25 ` [Bug 80791] "Bluetooth: hci0: ACL packet for unknown connection handle" must be hidden behind "debug" bugzilla-daemon
2023-09-08 10:24 ` bugzilla-daemon
2023-10-27 8:36 ` bugzilla-daemon
2023-10-27 8:38 ` bugzilla-daemon
2023-10-27 8:39 ` bugzilla-daemon
2023-10-27 8:40 ` bugzilla-daemon
2025-09-05 23:17 ` bugzilla-daemon
2025-09-10 22:05 ` bugzilla-daemon
2025-09-11 11:19 ` bugzilla-daemon
2025-09-11 11:58 ` bugzilla-daemon
2026-08-03 8:25 ` bugzilla-daemon [this message]
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=bug-80791-62941-8xCXt1KPiU@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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