FW Desktop 395-128GB - BIOS 03.02: ucsi_acpi USBC000:00: unknown error 0

[kk-1]

Hello,

I have FW Desktop 395-128GB - BIOS 03.02 and use openSUSE Tumbleweed with kernel 6.17.2-1-default.
keep getting the following when I plug my USB NVMe enclosures (one of the USB-C ports at the back):
...
pcieport 0000:00:08.3: PME: Spurious native interrupt!
ucsi_acpi USBC000:00: unknown error 0
...

Sometimes the NVMe enclosure disconnects and leaves the filesystem corrupted.
I fixed it since I have ext4, but it's annoying.

Please help us.

[JohnAZoidberg]

Does the enclosure and cable work fine on other systems?
Does it work fine on the front ports?

fyi @amstan

[kk-1]

I never had any problem with my other system before. I just tried the same cable+nvme enclosure on my other system which has the same Linux and kernel version. Those two lines of dmesg were not there. Other system were Minisforum UM790pro and the port I tried was frontal USB4 Port (Alt PD). There may be somekind of signaling stuff related to the ports (back USB 4 C-type) of FW Desktop or may be the Linux kernel module (for your USB system) needs an update. Hope either you may fix it by tweaking the BIOS or the Linux guys will do sth. I can not try the enclosure on other ports as the cable is type c from the both end.

[JohnAZoidberg]

Those two lines of dmesg were not there.

The UCSI error message doesn't cause any issues.

I can not try the enclosure on other ports as the cable is type c from the both end.

Can you try the front two USB-C ports, please?

What's the nvme enclosure that you're using?
Could you also provide sudo lsusb -v output for that please?

[kk-1]

Here is the summary of what I have done:
The front USB-C (pluggable) port is ok and does not generate any "ucsi_acpi USBC000:00: unknown error 0" dmesg line.
Back USB-C ports, they do. Different cables and nvme enclosures (RTL 9210, RTL9220) are tried in both front and back ports.
Maybe the BIOS needs options for ACPI settings stuff.
I do not know if any kernel boot parameter can fix that.

lsusb line of the nvme envlosure (RTL9210) attached to back USB-C
Bus 006 Device 005: ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter

lsusb line of the nvme envlosure (RTL9220) attached to back USB-C (same port as above)
Bus 006 Device 006: ID 0bda:9220 Realtek Semiconductor Corp. Ugreen Storage Device

sudo lsusb -v output of the RTL9220:

Bus 006 Device 006: ID 0bda:9220 Realtek Semiconductor Corp. Ugreen Storage Device
Negotiated speed: SuperSpeed+ (10Gbps)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.20
bDeviceClass 0 [unknown]
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x0bda Realtek Semiconductor Corp.
idProduct 0x9220 Ugreen Storage Device
bcdDevice f1.00
iManufacturer 1 Ugreen
iProduct 2 Ugreen Storage Device
iSerial 3 0132680008A5
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)
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x002a
bNumDeviceCaps 3
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000006
BESL Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 2047 micro seconds
SuperSpeedPlus USB Device Capability:
bLength 20
bDescriptorType 16
bDevCapabilityType 10
bmAttributes 0x00000001
Sublink Speed Attribute count 2
Sublink Speed ID count 1
wFunctionalitySupport 0x1100
Min functional Speed Attribute ID: 0
Min functional RX lanes: 1
Min functional TX lanes: 1
bmSublinkSpeedAttr[0] 0x000a4030
Speed Attribute ID: 0 10Gb/s Symmetric RX SuperSpeedPlus
bmSublinkSpeedAttr[1] 0x000a40b0
Speed Attribute ID: 0 10Gb/s Symmetric TX SuperSpeedPlus
Device Status: 0x0000
(Bus Powered)

[kk-1]

The message:

ucsi_acpi USBC000:00: unknown error 0

still persists for the recent BIOS update of version 3.03

[JohnAZoidberg]

Again, the UCSI message is not a problem.

Sometimes the NVMe enclosure disconnects and leaves the filesystem corrupted.

This is a problem. Does this occur on all ports?
I assume this would generate disconnect dmesg messages. Do you see those?
When does this disconnect occur? Just randomly? When entering or exiting sleep?

Maybe this issue is related
#111

[kk-1]

Yes, I guess, as in issue number 111, you stated, it is a power issue. Recently, the Thunderbolt NVMe enclosure I bought experienced similar problems. Hope that the next BIOS update will resolve it. The front USB-C port has no problems and no UCSI error in the dmesg for that port. But of course, things operate at a lower speed. We can close the issue pending the new BIOS update. But till then, the back USB 4 ports are risky to use.

[kk-1]

BIOS 3.04 and still the Thunderbolt NVMe enclosure shows the same inconsistency on the back USB4 ports.
In the middle of folder rsync, the drive gets disconnected. still the same dmesg:
ucsi_acpi USBC000:00: unknown error 0

And the drive during rsync:
...
I/O error, dev nvme2n1, sector 422560768 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 2
[37682.129948] [ T619] EXT4-fs warning (device nvme2n1p1): ext4_end_bio:368: I/O error 10 writing to inode 58589507 starting block 52820192)
[37682.129957] [ T49033] EXT4-fs (nvme2n1p1): failed to convert unwritten extents to written extents -- potential data loss! (inode 58589507, error -5)
[37682.129964] [ T619] EXT4-fs warning (device nvme2n1p1): ext4_end_bio:368: I/O error 10 writing to inode 58589507 starting block 52821216)
[37682.129964] [ T49033] Buffer I/O error on device nvme2n1p1, logical block 52817920
...