Created attachment 143621 [details] Snap shot that shows the packets flooding Hi, I have been using iMX board with Ubuntu and Bluez. During Handsfree phone call, I can see lot of hci sco packets with unknown connection handle. This hangs my system. I can see from some of the tickets as it is an issue with the drivers. Can anyone help me, how to solve this issue ? Atleast let me know, which driver to be modified ? Please refer the attached snapshot for the packet flooding. Thanks in Advance for your support. Thanks & Regards, Vinod.
I can reproduce this on a Lenovo x100e on 3.16.0-rc6 plus some git.
*** Bug 85161 has been marked as a duplicate of this bug. ***
*** Bug 90151 has been marked as a duplicate of this bug. ***
This is still relevant as of 6.4.14. There's absolutely no need to log this message more than once or ever. The kernel doesn't log TCP packets being dropped/lost/whatever. There's no need to log bluetooth's packets either unless debugging has been enabled.
In 6.4 the message is slightly different: Aug 28 11:13:15 hp kernel: Bluetooth: hci0: ACL packet for unknown connection handle 3837 | wc -l -> 25 for August 28 alone.
Luiz, Could you look into this please?
When connecting my laptop to my smartphone I get this message almost every 2 seconds. I don't think the user can even do anything about it, could you please show it _just once_? [278536.979041] input: Smartphone X (AVRCP) as /devices/virtual/input/input20 [278557.775313] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278573.330987] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278574.837013] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278577.025169] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278579.533122] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278587.617396] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278601.656461] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278603.847227] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278605.494469] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278607.640811] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278609.998596] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278611.898942] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278626.172392] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278627.966819] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278630.108002] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278634.449240] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278637.205311] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278639.417526] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278650.205987] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278651.664703] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278659.509455] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278661.063814] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278663.972533] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278666.922671] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278669.291930] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278673.299147] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278675.681829] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278693.982873] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278695.476906] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [278703.181558] Bluetooth: hci0: ACL packet for unknown connection handle 3837
Is this mailing list still relevant/active/actual or I should CC different people? This bug report has received zero attention from kernel Bluetooth developers and it seems to be trivial to fix.
The issue has now been known for close to a decade.
Sorry for a flood of messages but I really want this issues to be attended. Otherwise multiple people have a flood of useless messages in their kernel log.