All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 220564] New: Wrong indentification of Bluetooth in Lenovo Legion Pro 5 and 0489:e111 Foxconn / Hon Hai Wireless_Device
Date: Wed, 10 Sep 2025 23:30:56 +0000	[thread overview]
Message-ID: <bug-220564-62941@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=220564

            Bug ID: 220564
           Summary: Wrong indentification of Bluetooth in Lenovo Legion
                    Pro 5 and 0489:e111 Foxconn / Hon Hai Wireless_Device
           Product: Drivers
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: jcubic@onet.pl
        Regression: No

I commented on https://bugzilla.kernel.org/show_bug.cgi?id=80791

But I think that this is something unrelated, since the error message:

hci0: ACL packet for unknown connection handle 3837

in my case it may be an error in the driver, I have a flood of errors in logs.
I have a new laptop from 2025 (Lenovo Legion Pro 5 16IAX10 Ultra 7 255HX) and
the system I have (fedora 42 xfce) with kernel 6.16.5-200.fc42.x86_64 detects
something as MTP Wireless Device. There is an icon on the desktop. I think that
this is because of wrong detected Bluetooth device in the Bluetooth driver. The
laptop don't have any MTP device.

gio mount -l shows:

Volume(0): Wireless Device
  Type: GProxyVolume (GProxyVolumeMonitorMTP)


mtp-detect returns:

libmtp version: 1.1.19
Listing raw device(s)
Device 0 (VID=0489 and PID=e111) is a Vizio (for Lenovo) LIFETAB S9714.
   Found 1 device(s):
   Vizio (for Lenovo): LIFETAB S9714 (0489:e111) @ bus 3, dev 6
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB
interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.

lsusb:
Bus 003 Device 006: ID 0489:e111 Foxconn / Hon Hai Wireless_Device


I've enabled debugging with /sys/kernel/debug/dynamic_debug/control

This is part of the logs from btmon:

> ACL Data RX: Handle 3837 flags 0x02 dlen 143         #26475 [hci0] 238.821952
      Channel: 259 len 139 [PSM 0 mode Basic (0x00)] {chan 65535}
        32 00 9f d2 95 00 01 00 e6 0a 03 00 00 00 00 00  2...............
        00 dd 9a 00 00 00 00 00 00 08 0a 00 00 00 00 00  ................
        00 d7 04 00 00 71 cc 00 00 e9 11 00 00 00 00 00  .....q..........
        00 fe 0e 01 00 00 00 00 00 9e d2 95 00 6a d2 95  .............j..
        00 07 d6 50 00 fc 07 00 00 00 00 c0 df ff 3f 00  ...P..........?.
        00 02 00 20 00 02 00 00 00 02 00 20 00 02 00 00  ... ....... ....
        00 02 00 20 00 02 00 00 00 02 00 20 00 02 00 09  ... ....... ....
        00 5c 01 00 00 02 00 09 00 00 00 00 00 02 00 20  .\............. 
        00 02 00 00 00 02 00 20 00 02 00                 ....... ...     
> HCI Event: Number of Completed Pack.. (0x13) plen 5  #26476 [hci0] 238.854712
        Num handles: 1
        Handle: 50
        Count: 1
bluetoothd[1539]: < ACL Data TX.. flags 0x02 dlen 850  #26477 [hci0] 238.854861
      Channel: 3778 len 846 [PSM 0 mode Basic (0x00)] {chan 65535}

This is output of journalctl -k

wrz 11 00:38:50 jcubic kernel: hdev 0000000021bf8090 len 147
wrz 11 00:38:50 jcubic kernel: hci0 ACL data packet
wrz 11 00:38:50 jcubic kernel: hci0: len 143 handle 0x0efd flags 0x0002
wrz 11 00:38:50 jcubic kernel: Bluetooth: hci0: ACL packet for unknown
connection handle 3837
wrz 11 00:38:50 jcubic kernel: hci0 Event packet
wrz 11 00:38:50 jcubic kernel: hci0: event 0x13
wrz 11 00:38:50 jcubic kernel: hci0: num 1

I listen to music almost non-stop with Bluetooth speakers, and the error happen
during short music interruption. I think that it started to happen after I've
upgraded to testing kernel in Fedora.

This is a related bug in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=2392938

I hope that the provided info is enough, I used Grok (LLM) to help with
debugging.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2025-09-10 23:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10 23:30 bugzilla-daemon [this message]
2025-09-10 23:31 ` [Bug 220564] Wrong indentification of Bluetooth in Lenovo Legion Pro 5 16IAX10 and 0489:e111 Foxconn / Hon Hai Wireless_Device bugzilla-daemon
2025-09-13 15:42 ` bugzilla-daemon
2025-09-13 16:39 ` bugzilla-daemon
2025-10-19 16:45 ` bugzilla-daemon
2025-10-20 19:54 ` bugzilla-daemon
2025-10-21  9:02 ` bugzilla-daemon
2025-11-14 20:04 ` bugzilla-daemon
2026-01-06 22:13 ` [Bug 220564] hci0: ACL packet for unknown connection handle 3837 and sound interruption bugzilla-daemon
2026-01-06 22:15 ` 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-220564-62941@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 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.