From: Greg KH <gregkh@linuxfoundation.org>
To: Jie Deng <dengjie03@kylinos.cn>
Cc: stern@rowland.harvard.edu, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, usb-storage@lists.one-eyed-alien.net
Subject: Re: [PATCH v2] usb: storage: Ignore UAS driver for SanDisk Extreme Pro 55AF storage device
Date: Wed, 9 Jul 2025 08:21:31 +0200 [thread overview]
Message-ID: <2025070902-service-foam-1da5@gregkh> (raw)
In-Reply-To: <92f1e73f-5814-4e01-98b6-1c9c0b87f903@kylinos.cn>
On Wed, Jul 09, 2025 at 11:40:03AM +0800, Jie Deng wrote:
>
> 在 2025/7/8 15:33, Greg KH 写道:
> > > 2) linux + arm64: The SanDisk Extreme Pro 55AF device will report an error
> > > when
> > > using the uas driver and the driver cannot be loaded. USB Controller model
> > > (Vendor ID: 1912, Device ID: 0014,uPD720201 USB 3.0 Host Controller).
> > Ok, that sounds like an arm64 issue we should resolve. Why can the
> > driver not be loaded at all? What happens?
> 1. During the process of loading the uas driver, the following error message
> will occur,
> resulting in the failure of driver loading:
> scsi 3:0:0:1: Failed to get diagnostic page 0x1
> scsi 3:0:0:1: Failed to bind enclosure -19
> ses 3:0:0:1: Attached Enclosure device
> sd 3:0:0:0: [sda] tag#10 data cmplt err -75 uas-tag 1 inflight: CMD
> sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00
> sd 3:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
> sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00
Any chance you can use usbmon to try to figure out why the arm64 system
is sending different commands or failures than x86 is?
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-09 6:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 9:29 [PATCH] usb: storage: Ignore UAS driver for SanDisk Extreme Pro 55AF storage device Jie Deng
2025-07-03 10:01 ` Greg KH
2025-07-04 6:11 ` [PATCH v2] " Jie Deng
2025-07-04 8:24 ` Greg KH
2025-07-07 6:25 ` Jie Deng
2025-07-07 8:47 ` Greg KH
2025-07-07 9:52 ` Jie Deng
2025-07-08 7:32 ` Greg KH
2025-07-09 3:13 ` Jie Deng
2025-07-07 8:49 ` Greg KH
2025-07-08 5:55 ` Jie Deng
2025-07-08 7:33 ` Greg KH
[not found] ` <92f1e73f-5814-4e01-98b6-1c9c0b87f903@kylinos.cn>
2025-07-09 6:21 ` Greg KH [this message]
2025-07-10 6:28 ` Jie Deng
2025-07-04 7:39 ` [PATCH] " Jie Deng
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=2025070902-service-foam-1da5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dengjie03@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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