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: Fri, 05 Sep 2025 23:17:35 +0000 [thread overview]
Message-ID: <bug-80791-62941-IK2G0ByQ3Z@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-80791-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=80791
Jakub Jankiewicz (jcubic@onet.pl) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jcubic@onet.pl
--- Comment #11 from Jakub Jankiewicz (jcubic@onet.pl) ---
I have a similar issue. My hardware:
laptop Lenovo Legion Pro 5 16IAX10 Ultra 7 255HX (from 2025)
System Fedora 42 Xfce.
uname -a
Linux jcubic 6.16.4-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Aug 28 19:47:10
UTC 2025 x86_64 GNU/Linux
My Bluetooth Adapter:
Bus 003 Device 007: ID 0489:e111 Foxconn / Hon Hai Wireless_Device
dmesg output
[ 49.567615] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[ 599.542960] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[ 1437.569560] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[ 3859.566676] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[ 4453.577203] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[ 4567.071519] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[ 4924.313398] usb 3-10: USB disconnect, device number 5
[ 5240.053501] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[ 5628.063962] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[ 5949.560492] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[ 6101.594003] perf: interrupt took too long (2534 > 2500), lowering
kernel.perf_event_max_sample_rate to 78000
[ 7169.561230] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[ 7223.579889] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[ 9081.183509] perf: interrupt took too long (3191 > 3167), lowering
kernel.perf_event_max_sample_rate to 62000
[ 9387.061556] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[ 9403.597909] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A
(start=1409651 end=1409652) time 125 us, min 1574, max 1600, scanline start
1572, end 1573
[ 9674.574688] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[10152.077253] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[11119.576619] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[12687.069915] Bluetooth: hci0: ACL packet for unknown connection handle 3837
[14921.072319] perf: interrupt took too long (3990 > 3988), lowering
kernel.perf_event_max_sample_rate to 50000
[20399.081113] Bluetooth: hci0: ACL packet for unknown connection handle 3837
All Bluetooth entries marked in red
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2025-09-05 23:17 UTC|newest]
Thread overview: 16+ 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 [this message]
2025-09-10 22:05 ` bugzilla-daemon
2025-09-11 11:19 ` bugzilla-daemon
2025-09-11 11:58 ` bugzilla-daemon
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-IK2G0ByQ3Z@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;
as well as URLs for NNTP newsgroup(s).