On Mon, 13 Nov 2017 07:01:30 +0300 Andrey Astafyev <1@xxxxxxxxx> wrote: > 13.11.2017 00:42, Jérôme Carretero пишет: > > Nov 12 16:20:59 Bidule kernel: sd 22:0:0:0: [sdaa] tag#2 > > uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT > > [...] > > Do you see such things? > > > Hi, I've seen dmesg output like this so I've added my device to > quirks list like any other Seagate USB drive. Hi Andrey, Hans, For my devices, adding US_FL_NO_ATA_1X to unusual_uas.h didn't change anything, and while adding US_FL_IGNORE_UAS (using quirks=0bc2:ab34:u,0bc2:ab38:u) there are still device resets, but they cause shorter hangs in system activity (~1 second when UAS was more like ~20). Is the US_FL_NO_ATA_1X supposed to get rid of the R/W errors? The first entry I saw about this quirk was so that the device can be used at all (wouldn't be able to mount without it). I'll follow up: when scrubbing the devices after a sequence of experiments, there were checksum errors, so I'll retry with a more reproducible sequence to try and get something more solid. I wouldn't want to disable UAS just to see that reliability has been reduced (one Arch bug report mentions something like that https://bugs.archlinux.org/task/48362). Regards, -- Jérôme PS: The controllers I tested do the same: 09:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) 0c:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03) -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
