> On 13 Jan 2018, at 6:20 PM, Johannes Choo <1742...@bugs.launchpad.net> wrote: > > Hi, I am facing a related bug. I am using an SSD enclosure utilizing the > ASM1352R controller as well. This controller supports RAID-0, RAID-1 and > other configurations with up to two SSDs, and I'm currently using it > with only one SSD; the product advertises as ASM1352R-Safe in this > configuration, which is also what it advertises as when in RAID-1. I am > running Debian buster.
Most issues like this are distro-agnostic. > > The advertised product IDs and serial, etc. are all different for me. > Nevertheless, the bug still remains, and the fix proposed by OP works. By disabling UAS, the speed should be slower. > > OP mentioned "With/without UAS the issue persisted". I suspect that OP > might be confused and does not realize that the fix he proposes is > responsible for the message "UAS is blacklisted for this device, using > usb-storage instead"; the quirk he used disables UAS support from the > kernel side. Well, that’s the part I tried to understand, but apparently I offended him/her somehow =/ > > Nevertheless, fix OP proposes is not a universal fix. ASMedia, reputable > hardware manufacturer that it is, manufactures multiple chips with > different architectures and capabilities under the same > vendorId:productId identifier. Blacklisting this identifier will > blacklist all its controllers, which may not exactly be a bad thing as > multiple other models have issues with UAS under Linux as well. Ideally we should solve this without having to disable UAS completely. > > Inspection of latest upstream source seems that it is not handled > upstream, though I have not tried running it. > > I'd be happy to contribute however I can but I have my hands tied if you > need more info: I'm running Debian buster, and I'm running the > controller with only one SSD. Nevertheless, it seems to me that this is > an upstream bug and not Ubuntu-kernel specific. A full dmesg when this issue happens will be really helpful. > > -- > You received this bug notification because you are subscribed to linux > in Ubuntu. > https://bugs.launchpad.net/bugs/1742318 > > Title: > USB-Storage Quirk for 174c:1356 > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > A usb-storage quirk is needed for the Mediasonic ProRaid 2 Bay 2.5' > SATA HDD / SSD Enclosure - USB 3.1 Gen-II Type-C (HUR6-SU31) for > reliable use in Ubuntu/Kubuntu 14-17.10. Using quirk 'u' appears to > have fixed disconnect issues during install and use. > > Linux Version: Ubuntu 4.13.0-16.19-generic 4.13.4 > > Device ID:174c:1356 ASMedia Technology Inc. > > usb 9-1: new SuperSpeed USB device number 2 using xhci_hcd > usb 9-1: New USB device found, idVendor=174c, idProduct=1356 > usb 9-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 > usb 9-1: Product: ASM1352R-Fast > usb 9-1: Manufacturer: ASMT > usb 9-1: SerialNumber: 0000000000000001 > usb 9-1: UAS is blacklisted for this device, using usb-storage instead > > Note: With/without UAS the issue persisted. I disabled UAS to prevent > devices sleeping to eliminate that as a possibility. > > Symptoms: Before using the quirk, the enclosure would completely stop > responding during an install attempt, and the usb host would > eventually be disabled. The device's LEDs would continue to blink as > if being accessed. > > Fix: I specified the quirk by appending "usb- > storage.quirks=174c:1356:u" to the linux line in Grub. Hopefully > others can verify this (if I'm not insane) and include a patch for > this upstream in the Kernel. > > Note: For those who install to a device such as this, you may need to > modify your installation before booting it, by creating a file > "/etc/modprobe.d/asm1352r-usb-quirk.conf" with contents "options usb- > storage quirks=0x174c:0x1356:u". I have seen others (through Google) > issuing the same "u" quirk for several ASMedia devices...Perhaps their > chipsets need this? > > This is my first bug report. If any more information is needed, please > inform me. I'd like to thank a TJ- in Ubuntu's IRC for helping nail > this down. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742318/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742318 Title: USB-Storage Quirk for 174c:1356 Status in linux package in Ubuntu: Incomplete Bug description: A usb-storage quirk is needed for the Mediasonic ProRaid 2 Bay 2.5' SATA HDD / SSD Enclosure - USB 3.1 Gen-II Type-C (HUR6-SU31) for reliable use in Ubuntu/Kubuntu 14-17.10. Using quirk 'u' appears to have fixed disconnect issues during install and use. Linux Version: Ubuntu 4.13.0-16.19-generic 4.13.4 Device ID:174c:1356 ASMedia Technology Inc. usb 9-1: new SuperSpeed USB device number 2 using xhci_hcd usb 9-1: New USB device found, idVendor=174c, idProduct=1356 usb 9-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 usb 9-1: Product: ASM1352R-Fast usb 9-1: Manufacturer: ASMT usb 9-1: SerialNumber: 0000000000000001 usb 9-1: UAS is blacklisted for this device, using usb-storage instead Note: With/without UAS the issue persisted. I disabled UAS to prevent devices sleeping to eliminate that as a possibility. Symptoms: Before using the quirk, the enclosure would completely stop responding during an install attempt, and the usb host would eventually be disabled. The device's LEDs would continue to blink as if being accessed. Fix: I specified the quirk by appending "usb- storage.quirks=174c:1356:u" to the linux line in Grub. Hopefully others can verify this (if I'm not insane) and include a patch for this upstream in the Kernel. Note: For those who install to a device such as this, you may need to modify your installation before booting it, by creating a file "/etc/modprobe.d/asm1352r-usb-quirk.conf" with contents "options usb- storage quirks=0x174c:0x1356:u". I have seen others (through Google) issuing the same "u" quirk for several ASMedia devices...Perhaps their chipsets need this? This is my first bug report. If any more information is needed, please inform me. I'd like to thank a TJ- in Ubuntu's IRC for helping nail this down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
