crashoverride wrote:On a side note:
For those of you expressing concern about the health of my HDD, thank you for the letters, prayers, and flowers showing your support! [emoji38]
I am happy to report that the copy from /dev/zero completed without issue over SATA. The drive has been placed back in its enclosure and is again faithfully in service on my XU4. My HDD and me both look forward to further contributions to the community.
rooted wrote:What is the performance penalty with it disabled?
[ 5.550533] usb 4-1.2: new SuperSpeed USB device number 4 using xhci-hcd
[ 5.597126] usb 4-1.2: New USB device found, idVendor=0bc2, idProduct=2322
[ 5.625245] usb 4-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 5.653541] usb 4-1.2: Product: Expansion
[ 5.678566] usb 4-1.2: Manufacturer: Seagate
[ 5.703706] usb 4-1.2: SerialNumber: [REDACTED]
[ 5.710282] usb 3-1.1.2: new low-speed USB device number 5 using xhci-hcd
[ 5.764330] usb 4-1.2: UAS is blacklisted for this device, using usb-storage instead
[ 5.776433] usb-storage 4-1.2:1.0: USB Mass Storage device detected
[ 5.787555] usb-storage 4-1.2:1.0: Quirks match for vid 0bc2 pid 2322: 800000
[ 5.799280] scsi host0: usb-storage 4-1.2:1.0
$ dd if=/dev/zero of=nothing bs=4M status=progress
3925868544 bytes (3.9 GB, 3.7 GiB) copied, 30.0232 s, 131 MB/s^C
938+0 records in
938+0 records out
3934257152 bytes (3.9 GB, 3.7 GiB) copied, 30.0918 s, 131 MB/s
crashoverride wrote:Bus 004 Device 004: ID 0bc2:2322 Seagate RSS LLC
crashoverride wrote:I am happy to report that the copy from /dev/zero completed without issue over SATA
crashoverride wrote:crashoverride wrote:2) We need to allow end users to disable UAS. There is already an issue for this here: https://github.com/hardkernel/linux/issues/290
I discovered you can do this as a parameter on the kernel command line in boot.ini
- Code: Select all
usb-storage.quirks=0x0bc2:0x2322:u
crashoverride wrote:crashoverride wrote:I tried blacklisting UAS, but the kernel does not not load any driver (mass storage) at all.
- Code: Select all
modprobe.blacklist=uas
rooted wrote:What is the performance penalty with it disabled?
crashoverride wrote:In my case, there isn't one!![]()
130 MB/s is the maximum transfer rate of the drive observed when it was directly connected via SATA.
rncwnd wrote:Tried that too, but it doesn't work. After reboot boot.ini is reverted.
#------------------------------------------------------------------------------------------------------
# Basic Ubuntu Setup. Don't touch unless you know what you are doing.
# --------------------------------
setenv bootrootfs "usb-storage.quirks=0x0bc2:0x2322:u console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes net.ifnames=0"
tkaiser wrote:Whatever this task should be able to 'test'. Are you searching for data corruption or only 'it's already way too late' situations?
crashoverride wrote:The intention was to force the HDD to remap any bad sectors.
tkaiser wrote:You trust (again) in a HDD that already threw bad sectors and don't try to check for data integrity errors from now on
tkaiser wrote:after that much of testing and wasting your time
tkaiser wrote:Do you plan to search for 'solutions' that only apply to this micro community here
tkaiser wrote:or will you be responsible and contribute fix/information upstream?
tkaiser wrote:Simple question: will either you or mattrix take the additional time to report UAS issues with two more Seagate enclosures or not?
Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes
crashoverride wrote:usb-storage.quirks=0x0bc2:0x2322:u
I've been seeing issues like this with a bevy of external drives hooked up through USB, on every single GNU/Linux distribution that is running kernel 4.3 or later.
crashoverride wrote:It has already been reported.
tkaiser wrote:A bug that has been reported over at Ubuntu doesn't affect this kernel at all.
tkaiser wrote:So I see, the ODROID XU4 micro community prefers to remain insular, prefers to consider UAS being broken/dangerous/whatever and doesn't care about bugs fixed upstream.
Okay, nothing suspicious there.
crashoverride wrote:Right now there is an issue of everyone blaming XU4 "broken USB3".
tkaiser wrote:we the great ODROID XU4 micro community know better than the rest
mattrix wrote:So you have sent a patch for 0x0bc2x0x2322 & 0x0bc2:0x3321 ?
ERROR Transfer event for disabled endpoint or incorrect stream ring
messages randomly.usb-storage.quirks=0x2537:0x1068:u
in kernel parameter, it worked stably without UAS mode.WRITE
$ dd if=/dev/zero of=test3 oflag=direct bs=8M count=256
256+0 records in
256+0 records out
2147483648 bytes (2.1 GB, 2.0 GiB) copied, 10.8362 s, 198 MB/s
READ
$ dd if=test3 of=/dev/null iflag=direct bs=8M
256+0 records in
256+0 records out
2147483648 bytes (2.1 GB, 2.0 GiB) copied, 7.96288 s, 270 MB/s
WRITE
$ dd if=/dev/zero of=test3 oflag=direct bs=8M count=256
256+0 records in
256+0 records out
2147483648 bytes (2.1 GB, 2.0 GiB) copied, 12.2283 s, 176 MB/s
READ
$ dd if=test3 of=/dev/null iflag=direct bs=8M
256+0 records in
256+0 records out
2147483648 bytes (2.1 GB, 2.0 GiB) copied, 10.1888 s, 211 MB/s
odroid wrote:Is there any list of Linux compatible UAS chipsets?
#------------------------------------------------------------------------------
#
# USB attached SCSI (UAS) control
#
#------------------------------------------------------------------------------
#
# Disables the UAS driver for all devices. The driver is known to cause issues
# with many USB storage devices.
# 0 : normal UAS behavior
# 1 : UAS is globally disabled
#
# default: 1
#
#------------------------------------------------------------------------------
setenv disable_uas "1"
memeka wrote:What's wrong with having uas and usb-storage as modules?
#if IS_ENABLED(CONFIG_USB_UAS)
if (uas_use_uas_driver(intf, id, NULL))
return -ENXIO;
#endif
crashoverride wrote:However, I have not tested it.
tkaiser wrote:crashoverride wrote:However, I have not tested it.
You have not even tested whether your Seagate disk featuring just another broken firmware only needs the usual quirk(s) to work quite well with UAS since you're so busy protecting ODROID XU4 community from evil UAS [emoji38]
https://github.com/hardkernel/linux/com ... t-21984566
BTW: All the 'benchmarks' done here with dd trying to get a clue whether Mass Storage is as fast as UAS with HDDs are plain stupid if it's about normal disk usage and especially dealing with a lot of smaller files (since UAS has less overhead and supports NCQ).
tkaiser wrote:You have not even tested whether your Seagate disk featuring just another broken firmware only needs the usual quirk(s) to work quite well with UAS
tkaiser wrote:since you're so busy protecting ODROID XU4 community from evil UAS
odroid wrote:0bc2:a003 Seagate RSS LLC Backup Plus
odroid wrote:174c:5106 ASMedia Technology Inc. ASM1051
tkaiser wrote:And if you read through the Github issue referenced above Hans de Goede recommends a specific fix (disable USB-3 bulk streams). Why not giving that a try?
moon.linux wrote:We should enable CONFIG_DYNAMIC_DEBUG and CONFIG_USB_DEBUG to trace the usb handshakes between the USB device.
crashoverride wrote:Perhaps someone can elaborate on how disabling USB-3 bulk streams on XU4 will fix the issue on my x86 PC.
tkaiser wrote:You're still referring to this 'test' here
tkaiser wrote:I would neither call this a proper test setup nor a testing methodology.
odroid wrote:Is it possible to make a white-list of UAS compatible controller instead of black-list?
Return to Linux Kernel 4.14 Debugging Party
Users browsing this forum: No registered users and 2 guests