Linux USB
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: Gregkh <gregkh@linuxfoundation.org>
Cc: c2mismo <c2mismo@tuta.io>, Linux Usb <linux-usb@vger.kernel.org>
Subject: Re: USB: Lexar E300 21c4:b083 fails SuperSpeedPlus negotiation due to missing BOS descriptor — request for NO_BOS quirk
Date: Sat, 9 May 2026 17:31:20 +0200	[thread overview]
Message-ID: <20260509173120.7c15ee19.michal.pecio@gmail.com> (raw)
In-Reply-To: <2026050910-shopping-perceive-b23a@gregkh>

On Sat, 9 May 2026 06:07:19 +0200, Gregkh wrote:
> On Fri, May 08, 2026 at 09:18:22PM +0200, c2mismo wrote:
> > 
> > Dear USB subsystem maintainers,
> > 
> > I have a Lexar E300 M.2 SSD enclosure (idVendor=0x21c4,
> > idProduct=0xb083) that supports USB 3.2 Gen 2 (10 Gbps). Under
> > Linux it always negotiates down to 5 Gbps, while on Windows the
> > same hardware (cable, port) works correctly at 10 Gbps
> > (CrystalDiskMark ~1087 MB/s vs ~450 MB/s on Linux).
> > 
> > The kernel log shows that the device initially attempts SuperSpeed
> > Plus (Gen 2x1) but fails to provide a valid BOS descriptor, causing
> > an error -71 and a forced fallback to SuperSpeed (5 Gbps):

Where does it show that?
 
> > [  179.146227] usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 4 using xhci_hcd
> > [  182.237405] usb 2-1: USB disconnect, device number 4
> > [  182.420843] sd 12:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> > [  182.552343] usb usb2-port1: config error
> > [  183.131966] usb 2-1: new SuperSpeed USB device number 5 using xhci_hcd

Users with confirmed BOS problems had different logs:
https://bugzilla.kernel.org/show_bug.cgi?id=218943
https://bugzilla.kernel.org/show_bug.cgi?id=220027

> > i did try to add the following entry to drivers/usb/core/quirks.c
> > in the usb_quirk_list[]:
> > 
> > { USB_DEVICE(0x21c4, 0xb083), .driver_info = USB_QUIRK_NO_BOS },
> > 
> > I am running Arch Linux with kernel 7.0.3 (in the recent version
> > does not contain the NO_BOS definition in its source),  
> 
> 7.0.3 has that quirk flag, so this should work.

Well, maybe it's doesn't because it's a different issue?

Regards,
Michal

      reply	other threads:[~2026-05-09 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 19:18 USB: Lexar E300 21c4:b083 fails SuperSpeedPlus negotiation due to missing BOS descriptor — request for NO_BOS quirk c2mismo
2026-05-09  4:07 ` Gregkh
2026-05-09 15:31   ` Michal Pecio [this message]

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=20260509173120.7c15ee19.michal.pecio@gmail.com \
    --to=michal.pecio@gmail.com \
    --cc=c2mismo@tuta.io \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@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