From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Andrew M <quantumphazor@gmail.com>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: [regression] Bug 216817 - btusb device with ID 0489:e0d0 no longer working after v6.0
Date: Mon, 19 Dec 2022 12:10:03 +0100 [thread overview]
Message-ID: <12c40aac-8f3b-fea2-17bb-d6a954d26597@leemhuis.info> (raw)
Hi, this is your Linux kernel regression tracker speaking.
I noticed a regression report in bugzilla.kernel.org. As many (most?)
kernel developer don't keep an eye on it, I decided to forward it by
mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216817 :
> Andrew M 2022-12-18 04:28:43 UTC
>
> 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
See the ticket for more details.
BTW, let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:
#regzbot introduced: 26afbd826ee3
https://bugzilla.kernel.org/show_bug.cgi?id=216817
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
reply other threads:[~2022-12-19 11:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=12c40aac-8f3b-fea2-17bb-d6a954d26597@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=quantumphazor@gmail.com \
--cc=regressions@lists.linux.dev \
/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).