[PATCH] usb: storage: Ignore UAS driver for SanDisk Extreme Pro 55AF storage device

[Jie Deng]

The SanDisk Extreme Pro 55AF storage device(0781:55af) has poor compatibility with UAS drivers.
The logs:
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.359859][ 0] [ T163] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.385708][ 0] [ T163] usb 2-1: New USB device found, idVendor=0781, idProduct=55af, bcdDevice=10.85
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.385709][ 0] [ T163] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.385710][ 0] [ T163] usb 2-1: Product: Extreme Pro 55AF
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.385711][ 0] [ T163] usb 2-1: Manufacturer: SanDisk
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.385711][ 0] [ T163] usb 2-1: SerialNumber: 323234323935343030343636
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.927603][ 0] [ T306] usbcore: registered new interface driver usb-storage
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.940511][ 0] [ T306] scsi host3: uas
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.940584][ 0] [ T306] usbcore: registered new interface driver uas
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.940843][ 0] [ T188] scsi 3:0:0:0: Direct-Access SanDisk Extreme Pro 55AF 1085 PQ: 0 ANSI: 6
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.941363][ 0] [ T188] scsi 3:0:0:1: Enclosure SanDisk SES Device 1085 PQ: 0 ANSI: 6
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.941697][ 0] [ T188] sd 3:0:0:0: Attached scsi generic sg0 type 0
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.941783][ 0] [ T188] scsi 3:0:0:1: Attached scsi generic sg1 type 13
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.942296][ 0] [ T189] sd 3:0:0:0: [sda] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB)
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.942373][ 0] [ T189] sd 3:0:0:0: [sda] Write Protect is off
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.942374][ 0] [ T189] sd 3:0:0:0: [sda] Mode Sense: 37 00 10 00
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.942534][ 0] [ T189] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.943586][ 0] [ T189] sd 3:0:0:0: [sda] Optimal transfer size 2097152 bytes
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.976797][ 0] [ T189] sda: sda1
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.977898][ 0] [ T189] sd 3:0:0:0: [sda] Attached SCSI disk
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.980406][ 0] [ T267] scsi 3:0:0:1: Failed to get diagnostic page 0x1
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.980408][ 0] [ T267] scsi 3:0:0:1: Failed to bind enclosure -19
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.980414][ 0] [ T267] ses 3:0:0:1: Attached Enclosure device
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.981068][ 0] [ C0] sd 3:0:0:0: [sda] tag#10 data cmplt err -75 uas-tag 1 inflight: CMD
Jun 23 18:21:48 FD-0528-pc kernel: [ 1.981071][ 0] [ C0] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00
Jun 23 18:21:48 FD-0528-pc kernel: [ 33.819186][ 0] [ T188] sd 3:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
Jun 23 18:21:48 FD-0528-pc kernel: [ 33.819188][ 0] [ T188] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00
Jun 23 18:21:48 FD-0528-pc kernel: [ 33.843186][ 0] [ T309] scsi host3: uas_eh_device_reset_handler start

Device decriptor is below:
Bus 002 Device 003: ID 0781:55af SanDisk Corp. Extreme Pro 55AF
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.20
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x0781 SanDisk Corp.
idProduct 0x55af
bcdDevice 10.85
iManufacturer 2 SanDisk
iProduct 3 Extreme Pro 55AF
iSerial 1 323234323935343030343636
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0079
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 896mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 98
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 32
Data-in pipe (0x03)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 32
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 32
Status pipe (0x02)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 0
Command pipe (0x01)

So ignore UAS driver for this device.

Signed-off-by: Jie Deng <deng...@kylinos.cn>
---
drivers/usb/storage/unusual_uas.h | 7 +++++++
1 file changed, 7 insertions(+)

diff --git a/drivers/usb/storage/unusual_uas.h b/drivers/usb/storage/unusual_uas.h
index 1477e31d7763..9f093a6af7f9 100644
--- a/drivers/usb/storage/unusual_uas.h
+++ b/drivers/usb/storage/unusual_uas.h
@@ -199,3 +199,10 @@ UNUSUAL_DEV(0x4971, 0x8024, 0x0000, 0x9999,
"External HDD",
USB_SC_DEVICE, USB_PR_DEVICE, NULL,
US_FL_ALWAYS_SYNC),
+
+/* Reported-by: Jie Deng <deng...@kylinos.cn> */
+UNUSUAL_DEV(0x0781, 0x55af, 0x0000, 0x9999,
+ "SanDisk",
+ "Extreme Pro 55AF",
+ USB_SC_DEVICE, USB_PR_DEVICE, NULL,
+ US_FL_IGNORE_UAS),
--
2.25.1

[Greg KH]

On Thu, Jul 03, 2025 at 05:29:46PM +0800, Jie Deng wrote:
> diff --git a/drivers/usb/storage/unusual_uas.h b/drivers/usb/storage/unusual_uas.h
> index 1477e31d7763..9f093a6af7f9 100644
> --- a/drivers/usb/storage/unusual_uas.h
> +++ b/drivers/usb/storage/unusual_uas.h
> @@ -199,3 +199,10 @@ UNUSUAL_DEV(0x4971, 0x8024, 0x0000, 0x9999,
> "External HDD",
> USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> US_FL_ALWAYS_SYNC),
> +
> +/* Reported-by: Jie Deng <deng...@kylinos.cn> */
> +UNUSUAL_DEV(0x0781, 0x55af, 0x0000, 0x9999,
> + "SanDisk",
> + "Extreme Pro 55AF",
> + USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> + US_FL_IGNORE_UAS),
> --
> 2.25.1
>
>

Please read the comment at the top of this file for where to put the
entry.

thanks,

greg k-h

[Jie Deng]

The SanDisk Extreme Pro 55AF storage device(0781:55af) has poor compatibility with UAS drivers.
The logs:

[ 1.359859][ 0] [ T163] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd

[ 1.385708][ 0] [ T163] usb 2-1: New USB device found, idVendor=0781, idProduct=55af, bcdDevice=10.85

[ 1.385709][ 0] [ T163] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1

[ 1.385710][ 0] [ T163] usb 2-1: Product: Extreme Pro 55AF

[ 1.385711][ 0] [ T163] usb 2-1: Manufacturer: SanDisk

[ 1.385711][ 0] [ T163] usb 2-1: SerialNumber: 323234323935343030343636

[ 1.927603][ 0] [ T306] usbcore: registered new interface driver usb-storage

[ 1.940511][ 0] [ T306] scsi host3: uas

[ 1.940584][ 0] [ T306] usbcore: registered new interface driver uas

[ 1.940843][ 0] [ T188] scsi 3:0:0:0: Direct-Access SanDisk Extreme Pro 55AF 1085 PQ: 0 ANSI: 6

[ 1.941363][ 0] [ T188] scsi 3:0:0:1: Enclosure SanDisk SES Device 1085 PQ: 0 ANSI: 6

[ 1.941697][ 0] [ T188] sd 3:0:0:0: Attached scsi generic sg0 type 0

[ 1.941783][ 0] [ T188] scsi 3:0:0:1: Attached scsi generic sg1 type 13

[ 1.942296][ 0] [ T189] sd 3:0:0:0: [sda] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB)

[ 1.942373][ 0] [ T189] sd 3:0:0:0: [sda] Write Protect is off

[ 1.942374][ 0] [ T189] sd 3:0:0:0: [sda] Mode Sense: 37 00 10 00

[ 1.942534][ 0] [ T189] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA

[ 1.943586][ 0] [ T189] sd 3:0:0:0: [sda] Optimal transfer size 2097152 bytes

[ 1.976797][ 0] [ T189] sda: sda1

[ 1.977898][ 0] [ T189] sd 3:0:0:0: [sda] Attached SCSI disk

[ 1.980406][ 0] [ T267] scsi 3:0:0:1: Failed to get diagnostic page 0x1

[ 1.980408][ 0] [ T267] scsi 3:0:0:1: Failed to bind enclosure -19

[ 1.980414][ 0] [ T267] ses 3:0:0:1: Attached Enclosure device

[ 1.981068][ 0] [ C0] sd 3:0:0:0: [sda] tag#10 data cmplt err -75 uas-tag 1 inflight: CMD

[ 1.981071][ 0] [ C0] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00

[ 33.819186][ 0] [ T188] sd 3:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD

[ 33.819188][ 0] [ T188] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00

diff --git a/drivers/usb/storage/unusual_uas.h b/drivers/usb/storage/unusual_uas.h
index 1477e31d7763..6b1a08e2e724 100644
--- a/drivers/usb/storage/unusual_uas.h
+++ b/drivers/usb/storage/unusual_uas.h
@@ -52,6 +52,13 @@ UNUSUAL_DEV(0x059f, 0x1061, 0x0000, 0x9999,
USB_SC_DEVICE, USB_PR_DEVICE, NULL,
US_FL_NO_REPORT_OPCODES | US_FL_NO_SAME),

+/* Reported-by: Jie Deng <deng...@kylinos.cn> */
+UNUSUAL_DEV(0x0781, 0x55af, 0x0000, 0x9999,
+ "SanDisk",
+ "Extreme Pro 55AF",
+ USB_SC_DEVICE, USB_PR_DEVICE, NULL,
+ US_FL_IGNORE_UAS),

+
/* Reported-by: Zhihong Zhou <zhouz...@greatwall.com.cn> */
UNUSUAL_DEV(0x0781, 0x55e8, 0x0000, 0x9999,
"SanDisk",
--
2.25.1

[Jie Deng]

I'm very sorry for not reading the file to be modified carefully.

The second version of the patch has been modified as required.

Thanks

jie deng

[Greg KH]

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/process/submitting-patches.rst for what
needs to be done here to properly describe this.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot

[Jie Deng]

v2:
* According to the file modification rules (sort by VendorID
first, then by ProductID.) Add the newly added "UNUSUAL_DEV"
in the correct position.
v1:
* The newly added "UNUSUAL_DEV" was directly added to the end
without modifying the format according to the file.

[Greg KH]

Why is there two "v2" patches sent here? Shouldn't this be "v3"?

confused,

greg k-h

[Greg KH]

On Mon, Jul 07, 2025 at 02:25:07PM +0800, Jie Deng wrote:

> The SanDisk Extreme Pro 55AF storage device(0781:55af) has poor compatibility with UAS drivers.
> The logs:
> [ 1.359859][ 0] [ T163] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd

Nit, the [] stuff should all be removed, it's not relevant, right?

So new devices are being made that can not handle UAS? Are you sure
there's not some other quirk that could be used here instead? How does
this device work on other operating systems with the UAS drivers there?

thanks,

greg k-h

[邓杰]

----

 

主　题：Re: [PATCH v2] usb: storage: Ignore UAS driver for SanDisk Extreme Pro 55AF storage device
日　期：2025-07-07 16:47
发件人：Greg KH
收件人：邓杰;

On Mon, Jul 07, 2025 at 02:25:07PM +0800, Jie Deng wrote:
> The SanDisk Extreme Pro 55AF storage device(0781:55af) has poor compatibility with UAS drivers.
> The logs:
> [ 1.359859][ 0] [ T163] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd

> ---
> v2:
> * According to the file modification rules (sort by VendorID
> first, then by ProductID.) Add the newly added "UNUSUAL_DEV"
> in the correct position.
> v1:
> * The newly added "UNUSUAL_DEV" was directly added to the end
> without modifying the format according to the file.
>
> ---
> drivers/usb/storage/unusual_uas.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/usb/storage/unusual_uas.h b/drivers/usb/storage/unusual_uas.h
> index 1477e31d7763..6b1a08e2e724 100644
> --- a/drivers/usb/storage/unusual_uas.h
> +++ b/drivers/usb/storage/unusual_uas.h
> @@ -52,6 +52,13 @@ UNUSUAL_DEV(0x059f, 0x1061, 0x0000, 0x9999,
> USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> US_FL_NO_REPORT_OPCODES | US_FL_NO_SAME),
>

> +/* Reported-by: Jie Deng */

> +UNUSUAL_DEV(0x0781, 0x55af, 0x0000, 0x9999,
> + "SanDisk",
> + "Extreme Pro 55AF",
> + USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> + US_FL_IGNORE_UAS),
> +

> /* Reported-by: Zhihong Zhou */

> UNUSUAL_DEV(0x0781, 0x55e8, 0x0000, 0x9999,
> "SanDisk",
> --
> 2.25.1

Why is there two "v2" patches sent here? Shouldn't this be "v3"?

confused,

greg k-h

 

The first sent V2 patch was missing the description of the differences

between V1 and V2 patches. The V2 patch sent for the second time only

adds a description of the differences from the V1 patch compared to the

V2 patch sent for the first time. There is no modification to the code.

So it is rashly believed that it does not need to be defined as a V3 patch.

 

[Jie Deng]

The first sent  V2 patch was missing the description of the differences 

[Jie Deng]

在 2025/7/7 16:47, Greg KH 写道:

[Jie Deng]

Thank you for your reply.

1. The information within [] is redundant and should be removed
2. Regarding your question, before submitting the patch,
I conducted the following tests:
1) linux + x86: The SanDisk Extreme Pro 55AF device can be recognized
normally when using the uas driver. USB controller model (VendorID:
1D94, DeviceID: 145F,Chengdu Haiguang IC Design Co., Ltd.USB 3.0 Host
controller)
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).
3) linux + arm64: Add the parameter "USB-storage.quirks =0781:55af:u" in
grub.
The SanDisk Extreme Pro 55AF device runs the usb storage driver without
any error
and can be recognized normally.

[Greg KH]

Think about what you would do if you got sent 2 "v2" patches? :)

Remember, some of us get hundreds/thousands of emails to handle a day,
please make it very obvious what to do here.

thanks,

greg k-h

[Greg KH]

On Tue, Jul 08, 2025 at 01:55:47PM +0800, Jie Deng wrote:
> 2. Regarding your question, before submitting the patch,
> I conducted the following tests:
> 1) linux + x86: The SanDisk Extreme Pro 55AF device can be recognized
> normally when using the uas driver. USB controller model (VendorID:
> 1D94, DeviceID: 145F,Chengdu Haiguang IC Design Co., Ltd.USB 3.0 Host
> controller)

So it all works, great!

> 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?

> 3) linux + arm64: Add the parameter "USB-storage.quirks =0781:55af:u" in
> grub.
> The SanDisk Extreme Pro 55AF device runs the usb storage driver without any
> error
> and can be recognized normally.

Let's track down and fix the arm64 issue here please, and not paper over
it by saying that this whole device will not work well on all arches.

thakns,

greg k-h

[Jie Deng]

I'm very sorry. I'll pay attention when submitting patches later

[Jie Deng]

在 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

2. 0781:55ab SanDisk Corp.SanDisk 3.2Gen1 device also runs the uas driver,
but there is no error as mentioned above.

[Greg KH]

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

[Jie Deng]

Thank you for your suggestions. I’ll review them thoroughly going
forward.🙂