public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0
Date: Sun, 18 Dec 2022 04:28:43 +0000	[thread overview]
Message-ID: <bug-216817-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 216817
           Summary: btusb device with ID 0489:e0d0 no longer working after
                    v6.0
           Product: Drivers
           Version: 2.5
    Kernel Version: 6.0, 6.0.12
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: quantumphazor@gmail.com
        Regression: No

The internal USB Bluetooth device in my laptop no longer works since v6.0

Device in question:
ID 0489:e0d0 Foxconn / Hon Hai

Works fine in 5.19.x and fails after 6.0
I ran a bisect that resulted in it breaking after this commit:
26afbd826ee326e63a334c37fd45e82e50a615ec Bluetooth: Add initial implementation
of CIS connections

System: Lenovo ThinkPad T14 (AMD) Gen 2

dmesg output:

[    0.978396] usb 5-4: new full-speed USB device number 2 using xhci_hcd
[    1.142461] usb 5-4: New USB device found, idVendor=0489, idProduct=e0d0,
bcdDevice= 0.01
[    1.142467] usb 5-4: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[    4.591285] Bluetooth: Core ver 2.22
[    4.591304] Bluetooth: HCI device and connection manager initialized
[    4.591308] Bluetooth: HCI socket layer initialized
[    4.591309] Bluetooth: L2CAP socket layer initialized
[    4.591315] Bluetooth: SCO socket layer initialized
[    4.871972] usbcore: registered new interface driver btusb
[    4.883484] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection
command is advertised, but not supported.
[    4.973465] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.973468] Bluetooth: BNEP filters: protocol multicast
[    4.973472] Bluetooth: BNEP socket layer initialized
[    4.975525] Bluetooth: hci0: unexpected cc 0x2060 length: 1 < 7
[    4.975537] Bluetooth: hci0: Opcode 0x2060 failed: -38
[    6.985714] Bluetooth: hci0: command tx timeout

Attached is output of lsusb -v -d 0489:e0d0

-- 
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:[~2022-12-18  4:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-18  4:28 bugzilla-daemon [this message]
2022-12-18  4:30 ` [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
2022-12-19  8:33 ` bugzilla-daemon
2022-12-19 10:55 ` bugzilla-daemon
2022-12-19 21:06 ` bugzilla-daemon
2022-12-19 21:10 ` bugzilla-daemon
2022-12-19 21:13   ` [Bug,216817] " bluez.test.bot
2022-12-20  3:25 ` [Bug 216817] " bugzilla-daemon
2022-12-20 20:25 ` bugzilla-daemon
2022-12-21 11:19 ` bugzilla-daemon
2023-01-11 19:44 ` bugzilla-daemon
2023-01-11 19:44 ` bugzilla-daemon
2023-01-16 13:29 ` bugzilla-daemon
2023-01-17 19:22 ` bugzilla-daemon
2023-01-26 16:21 ` 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-216817-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox