From: Massimo Burcheri <massimo@burcheri.de>
To: Oliver Neukum <oneukum@suse.com>
Cc: linux-usb <linux-usb@vger.kernel.org>
Subject: Re: SanDisk Extreme Pro 55AF and UAS
Date: Thu, 21 Sep 2023 14:01:17 +0200 [thread overview]
Message-ID: <ab4b54381f1237d3ebe087433971c26af7265aa1.camel@gmail.com> (raw)
In-Reply-To: <d910b948-7448-46d3-ba98-42bc6e644626@suse.com>
On Tue, 2023-09-19 at 15:47 +0200, Oliver Neukum wrote:
> On 19.09.23 15:34, Massimo Burcheri wrote:
> > Searching the web for these error messages I found I needed to disable UAS
> > and continue with usb-storage:
> > options usb-storage quirks=0781:55af:u
> > That works, but reduces the performance a lot. What is broken?
> Probably your device. Are you using bus powered devices?
Which device, Linux machine or NVMedrive/enclosure?
Yes, the drive is bus powered.
The drive with same cable still works fine with UAS on my other Linux machine.
The drive with same cable works on the failing machine with usb-storage module,
only uas is failing.
What could that be?
Best regards,
Massimo
next prev parent reply other threads:[~2023-09-21 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 13:34 SanDisk Extreme Pro 55AF and UAS Massimo Burcheri
2023-09-19 13:47 ` Oliver Neukum
2023-09-21 12:01 ` Massimo Burcheri [this message]
2023-09-27 15:53 ` Massimo Burcheri
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=ab4b54381f1237d3ebe087433971c26af7265aa1.camel@gmail.com \
--to=massimo@burcheri.de \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
/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