linux-kernel - Re: [PATCH] usb: add QUIRK_NO

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

Message-ID: <2026020527-ivy-gathering-93a7@gregkh>
Date: Thu, 5 Feb 2026 07:51:17 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: A1RM4X <dev@...m4x.com>
Cc: linux-usb@...r.kernel.org, limiao@...inos.cn, oneukum@...e.com,
	huanglei@...inos.cn, lijiayi@...inos.cn,
	johannes.bruederl@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb: add QUIRK_NO_BOS for several devices

On Wed, Feb 04, 2026 at 02:51:35PM -0500, A1RM4X wrote:
> I added a clean patch to this email.

Thanks, but again, we can not take attached patches :(

> I own the devices mentioned in the patch. For all 3 devices, the USB
> port speed (10Gbps) is reached on Windows, they just negotiate 5Gbps
> speed on Linux. After applying the patch, as mentioned earlier, they
> reach the correct speed. I just did a 3 hours record on the Avermedia
> on Linux and it works as expected with a patched kernel.

Ok, it looks like there is a very broken USB controller chip out there
in all of these devices.

> Here is an updated dmesg output after following your instructions on
> the current kernel master:
> 
> [  701.425991] usb 2-2: new SuperSpeed Plus Gen 2x1 USB device number
> 2 using xhci_hcd
> [  706.735379] usb 2-2: unable to get BOS descriptor or descriptor too short
> [  706.735390] usb 2-2: unable to read config index 0 descriptor/start: -19
> [  706.920395] usb 2-2: Device not responding to setup address.
> [  707.127380] usb 2-2: Device not responding to setup address.
> [  707.335050] usb 2-2: device not accepting address 3, error -71
> [  707.338647] usb usb2-port2: attempt power cycle
> [  708.656278] usb 2-2: new SuperSpeed USB device number 5 using xhci_hcd
> [  708.859889] usb 2-2: LPM exit latency is zeroed, disabling LPM.
> [  708.955893] usb 2-2: New USB device found, idVendor=2b89,
> idProduct=5871, bcdDevice= 0.00
> [  708.955895] usb 2-2: New USB device strings: Mfr=6, Product=7, SerialNumber=3
> [  708.955896] usb 2-2: Product: UGREEN 35871
> [  708.955897] usb 2-2: Manufacturer: UGREEN 35871
> [  708.955897] usb 2-2: SerialNumber: PRODUCT
> [  709.142354] hid-generic 0003:2B89:5871.0007: hiddev99,hidraw6: USB
> HID v1.11 Device [UGREEN 35871 UGREEN 35871] on
> usb-0000:0b:00.0-2/input4
> [  709.165518] videodev: Linux video capture interface: v2.00
> [  709.187290] uvcvideo 2-2:1.1: Unknown video format
> 30313050-0000-0010-8000-00aa00389b71
> [  709.187297] uvcvideo 2-2:1.0: Found UVC 1.00 device UGREEN 35871 (2b89:5871)
> [  709.224374] usbcore: registered new interface driver uvcvideo

Sorry, I wasn't specific.  What happens with your patch applied, and
THEN you run 'lsusb -v' on the system?  Does the devices reset then?

> Regarding the Signed‑off‑by line, if I can't sign it with my content
> creator name, please sign it yourself. Whether I put my name on this
> patch is not important, what is important is the kernel to function
> properly with those devices.

For obvious reasons, we can't sign off on other people's patches.  But
we can rewrite them, I'll go do that later today, and give you
reported-by credit.

Note, for the future, if you wish to contribute kernel patches, please
read the documentation section about how to write changelog text, as
what you provided we couldn't take as-is.

thanks,

greg k-h