On Fri, Oct 03, 2014 at 11:42:37AM +0200, Hans de Goede wrote: > There are a large numbers of issues with ASM1051 devices in uas mode: > > 1) They do not support REPORT SUPPORTED OPERATION CODES > > 2) They use out of spec 8 byte status iu-s when they have no sense data, > switching to normal 16 byte status iu-s when they do have sense data. > > 3) They hang / crash when combined with some disks, e.g. a Crucial M500 ssd. > > 4) They hang / crash when stressed (through e.g. sg_reset --bus) with disks > with which then normally do work (once 1 & 2 are worked around). > > Where as in BOT mode they appear to work fine, so the best way forward with > these devices is to just blacklist them for uas usage. > > Unfortunately this is easier said then done. as older versions of the ASM1053 > (which works fine) use the same usb-id as the ASM1051. > > When connected over USB-3 the 2 can be told apart by the number of streams > they support. So this patch adds some less then pretty code to disable uas for > the ASM1051. When connected over USB-2, simply disable uas alltogether for > devices with the shared usb-id. > > Cc: stable@xxxxxxxxxxxxxxx # 3.16 > Signed-off-by: Hans de Goede <hdegoede@xxxxxxxxxx> > Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > -- > Upstream commit-id a9c54caa456dccba938005f6479892b589975e6a > --- > drivers/usb/storage/uas-detect.h | 27 +++++++++++++++++++++++---- > 1 file changed, 23 insertions(+), 4 deletions(-) This doesn't apply at all to 3.16-stable :( -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html