linux-kernel - [regression] Bug 216817 - btusb device with ID 0489:e0d0 no longer working after v6.0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <12c40aac-8f3b-fea2-17bb-d6a954d26597@leemhuis.info>
Date:   Mon, 19 Dec 2022 12:10:03 +0100
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Luiz Augusto von Dentz <luiz.dentz@...il.com>
Cc:     Andrew M <quantumphazor@...il.com>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        LKML <linux-kernel@...r.kernel.org>,
        Marcel Holtmann <marcel@...tmann.org>,
        Johan Hedberg <johan.hedberg@...il.com>,
        "linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>
Subject: [regression] Bug 216817 - btusb device with ID 0489:e0d0 no longer working after v6.0

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.