linux-kernel - Re: Strange problem with USB device

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210608182038.GA1812516@rowland.harvard.edu>
Date:   Tue, 8 Jun 2021 14:20:38 -0400
From:   Alan Stern <stern@...land.harvard.edu>
To:     Larry Finger <Larry.Finger@...inger.net>
Cc:     linux-usb@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        ierturk@...e.org
Subject: Re: Strange problem with USB device

On Tue, Jun 08, 2021 at 12:41:23PM -0500, Larry Finger wrote:
> Hi,
> 
> In https://bugzilla.suse.com/show_bug.cgi?id=1186889, a user is
> reporting that his Bluetooth component of a Realtek RTL8822CE is not

Is that a USB device?  That is, does it connect to the computer 
via a USB cable?  I'll assume it does...

> being found in openSUSE's kernel 5.3.18. His lsusb scan is as follows:
> 
> $ lsusb
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera
> Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 
> The Bluetooth device is found and works in Windows 10, where the Device
> Manager reports hardware ID's of 0bda:b00c. This combination is in
> driver btusb.
> 
> Is there a bug in the USB bus scan in kernel 5.3.18 that has since been
> fixed, or is there still a bug that misses this device?

Given only the information you have provided, it is impossible to 
answer that question.  Broadly speaking, lots of bugs in the USB 
subsystem have been fixed since kernel 5.3.18, but I don't know 
if any of them would affect detecting new devices on the bus like 
this.

One thing you might try is to turn on USB debugging before 
plugging in the device:

echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control

The additional information this adds to the dmesg log may be 
helpful.

Alan Stern