On 2014-12-03 10:53, Oliver Neukum wrote: > On Wed, 2014-12-03 at 10:41 +0100, Marcin Zajączkowski wrote: >> 2014-12-03 Oliver Neukum wrote: >>> On Wed, 2014-12-03 at 00:29 +0100, Marcin Zajączkowski wrote: >>>> Hi, >>>> >>>> After upgrade to Fedora 21 with 3.17.3-300.fc21.x86_64 (from 3.14.x in >>>> Fedora 19) my USB 3.0 drive (Seagate Backup+ 1TB) stopped working with >>>> USB 3.0 port (works fine with USB 2.0 port). >>>> >>>> When plug in for the first time (USB 3.0 port) I see in log: >>>> >>>>> kernel: xhci_hcd 0000:04:00.0: ERROR Transfer event for disabled >>>> endpoint or incorrect stream ring >>>>> kernel: xhci_hcd 0000:04:00.0: @0000000241eec570 11979000 00000002 >>>> 05000000 01078001 >>> >>> Are you using the UAS driver? >> >> Probably yes. How can check that and/or switch to not UAS driver for a test? > > Sysfs holds the information. I can be comfortably queried with the > "usb-devices" script. > > To switch drivers you can use the "no UAS" quirk which can be given as > a module parameter like other quirks. Thanks Olivier for your reply. UAS keyword helped me to ignore UAS for my drive (via `options usb-storage quirks=vendorId:productId:u`) and my drive can again be used via USB 3.0 port. I was also able to reproduce bug with the latest stable kernel version 3.17.4-301.fc21.x86_64 and I have found a few other UAS related bugs, but most of them seem to be already closed (fixed): https://bugzilla.redhat.com/show_bug.cgi?id=1121288 https://bugzilla.kernel.org/show_bug.cgi?id=79511 http://lists.opensuse.org/archive/opensuse-bugs/2014-07/msg00919.html I have also seen a patch on that mailing list submitted by Hans de Goede which disables UAS for ASM1051 devices: http://www.spinics.net/lists/linux-usb/msg113537.html What would you propose to do with the issue with that Seagate drive (family?)? To either track it or to temporary disable UAS for them globally (to not produce system crashes). Marcin -- 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
