You are not logged in.
- Topics: Active | Unanswered
#1 2014-06-21 15:44:10
- Larsson
- Member
- From: Sweden
- Registered: 2010-03-22
- Posts: 157
uas problem in linux 3.15.1, need advice on the problem [SOLVED]
After upgrading linux to 3.15.1 I cannot mount my Seagate expansion desktop hard drive. When I try to mount it, my whole system freezes and I need to pull the battery. This only happens with my usb3 compatible harddrive and not my usb2 only. Now I've downgraded to 3.14 again and everything is back to normal. I've monitored dmesg up to where it crashes and noticed lot of UAS (USB Attached SCSI) messages and believe that is the culprit. Since my system crashes and I don't see anything in /var/log after, I really don't know how to investigate it further and would appreciate if you had some suggestions on where to look next?
Last edited by Larsson (2014-06-23 15:41:05)
"If the person you are talking to doesn't appear to be listening, be patient. It may simply be that he has a small piece of fluff in his ear." - A.A. Milne (Winnie-the-Pooh)
Offline
#2 2014-06-21 16:32:18
- Cloudee
- Member
- Registered: 2014-06-20
- Posts: 1
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
Hey, I've got a similar issue. My Century CMB25U3BL6G external HDD case (which supports uas) stopped working after kernel upgrade to 3.15.1.
The usb HDD case can be detected as an xhci device, but can't detect and storage in it.
Since my whole OS is in this HDD case, I could just manage to switch to 3.10.44-1-lts kernel.
-edit- P.s another HDD case which doesn't support UAS works well, but since that case is for 3.5' HDD, I can't put my 2.5' SSD in to boot system with it.
The lsusb output for this HDD case is below (under kernel 3.10.44-1-lts, since I can't boot with kernel 3.15.1):
$ sudo lsusb -v -d 4971:8017
Bus 003 Device 003: ID 4971:8017 SimpleTech
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x4971 SimpleTech
idProduct 0x8017
bcdDevice 81.04
iManufacturer 1 CMB25U36G
iProduct 2 CMB25U36G
iSerial 3 111122223333
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 121
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4 USB Mass Storage
bmAttributes 0xc0
Self Powered
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 6 MSC Bulk-Only Transport
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 98
iInterface 10 MSC USB Attached SCSI
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 0
Command pipe (0x01)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 0
MaxStreams 16
Status pipe (0x02)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 16
Data-in pipe (0x03)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 16
Data-out pipe (0x04)
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 32 micro seconds
Device Status: 0x000d
Self Powered
U1 Enabled
U2 EnabledLast edited by Cloudee (2014-06-21 16:36:23)
Offline
#3 2014-06-21 16:47:04
- andy123
- Member
- Registered: 2011-11-04
- Posts: 169
- Website
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
From looking at the config, UAS is seemingly build as a module. So how about blacklisting it?
I mean, UAS is technically an improvement and you should try to get it working, so reporting a kernel bug is probably in order, but to make your harddrive work for now, blacklisting seems like the easiest solution.
i'm sorry for my poor english wirting skills…
Offline
#4 2014-06-21 20:53:35
- Da_Coynul
- Member
- From: United States of America
- Registered: 2010-10-02
- Posts: 85
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
Same problem here. I posted a bug report to the linux-usb mailing list as it seems USB issues are not handled on the Kernel Bug Tracker.
For me. blacklisting the uas module is not really helpful. While the system does not lock up when the drive is attached, the drive is simply not detected (does not show up with fdisk -l).
Jonathan
Last edited by Da_Coynul (2014-06-21 20:58:04)
Offline
#5 2014-06-21 21:05:11
- andy123
- Member
- Registered: 2011-11-04
- Posts: 169
- Website
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
Same problem here. I posted a bug report to the linux-usb mailing list as it seems USB issues are not handled on the Kernel Bug Tracker.
For me. blacklisting the uas module is not really helpful. While the system does not lock up when the drive is attached, the drive is simply not detected (does not show up with fdisk -l).Jonathan
USB on bugzilla.kernel.org:
https://bugzilla.kernel.org/buglist.cgi … _id=321501
i'm sorry for my poor english wirting skills…
Offline
#6 2014-06-21 21:38:40
- Da_Coynul
- Member
- From: United States of America
- Registered: 2010-10-02
- Posts: 85
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
Andy -
Please read this recent comment by kernel maintainer Greg Kroah-Hartman about why the USB developers don't use bugzilla.
Jonathan
USB on bugzilla.kernel.org:
https://bugzilla.kernel.org/buglist.cgi … _id=321501
Last edited by Da_Coynul (2014-06-21 21:42:40)
Offline
#7 2014-06-21 21:54:07
- andy123
- Member
- Registered: 2011-11-04
- Posts: 169
- Website
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
Good to know… So why do they even keep it open? o.O
Anyways, I hope you get a response on the mailing list.
i'm sorry for my poor english wirting skills…
Offline
#8 2014-06-22 11:29:56
- Larsson
- Member
- From: Sweden
- Registered: 2010-03-22
- Posts: 157
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
Good to know… So why do they even keep it open? o.O
Anyways, I hope you get a response on the mailing list.
If you get some useful response, can you post it here?
"If the person you are talking to doesn't appear to be listening, be patient. It may simply be that he has a small piece of fluff in his ear." - A.A. Milne (Winnie-the-Pooh)
Offline
#9 2014-06-22 11:46:55
- Da_Coynul
- Member
- From: United States of America
- Registered: 2010-10-02
- Posts: 85
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
Larsson,
Yes, I will. BTW, could you post the output of
lsusb -vI will forward the results to the linux-usb mailing list. I am sure the USB developers will want to know that various hardware is affected by this regression. Thanks.
Jonathan
If you get some useful response, can you post it here?
Offline
#10 2014-06-22 12:03:09
- Larsson
- Member
- From: Sweden
- Registered: 2010-03-22
- Posts: 157
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
Sure thing.
Bus 002 Device 004: ID 0bc2:3312 Seagate RSS LLC
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0bc2 Seagate RSS LLC
idProduct 0x3312
bcdDevice 7.37
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 85
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8b EP 11 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0a EP 10 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 98
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x08 EP 8 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Command pipe (0x01)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x89 EP 9 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Status pipe (0x02)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0a EP 10 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8b EP 11 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-in pipe (0x03"If the person you are talking to doesn't appear to be listening, be patient. It may simply be that he has a small piece of fluff in his ear." - A.A. Milne (Winnie-the-Pooh)
Offline
#11 2014-06-22 14:21:35
- matse
- Member
- Registered: 2011-04-27
- Posts: 299
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
I have a similiar problem with my external (encrypted) harddrive: I can't luksOpen it not anymore since kernel 3.15.1,
here is the relevant lsusb -v output:
Bus 001 Device 013: ID 0bc2:3312 Seagate RSS LLC
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0bc2 Seagate RSS LLC
idProduct 0x3312
bcdDevice 7.40
iManufacturer 1 Seagate
iProduct 2 Expansion Desk
iSerial 3 NA4LVQ5N
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 85
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8b EP 11 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0a EP 10 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 98
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x08 EP 8 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Command pipe (0x01)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x89 EP 9 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Status pipe (0x02)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0a EP 10 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8b EP 11 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-in pipe (0x03)
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 512 micro seconds
Device Status: 0x0001
Self PoweredAnd in this thread I explain my problem in more detail - it could be the same problem as described here 
greetings
matse
Offline
#12 2014-06-22 14:30:36
- Da_Coynul
- Member
- From: United States of America
- Registered: 2010-10-02
- Posts: 85
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
I was able to get my external drive working again by telling the usb-storage module to ignore uas for the device. Here is how to do it:
First, create a file named ignore_uas.conf in the /etc/modprobe.d directory containing the following*:
options usb-storage quirks=Vendor_ID:Product_ID:u*(substitute your actual Vendor_ID and Product_ID obtained from the lsusb -v command).
Next, regenerate your inital ramdisk:
# mkinitcpio -p linuxFinally, reboot your computer.
Although this is not a solution to broken uas, at least it will let you use your drive as before
Offline
#13 2014-06-22 23:11:32
- matse
- Member
- Registered: 2011-04-27
- Posts: 299
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
Da_Coynul: Thanks! That helped - at least I can now mount and use my external drive as before! I hope this issue gets fixed, soon 
Offline
#14 2014-06-23 08:21:36
- manoma080
- Member
- Registered: 2014-06-21
- Posts: 2
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
I have an external USB 3.0 Hitachi Touro Mobile Pro and the same problem happened. Da_Coynul's solution works great for me! 
Bus 003 Device 007: ID 4971:1012 SimpleTech
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x4971 SimpleTech
idProduct 0x1012
bcdDevice 47.98
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 85
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 98
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Command pipe (0x01)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Status pipe (0x02)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-in pipe (0x03)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-out pipe (0x04)Offline
#15 2014-06-23 15:42:04
- Larsson
- Member
- From: Sweden
- Registered: 2010-03-22
- Posts: 157
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
Since there's a workaround (have not tried it yet) and the bug is reported, I've marked the thread as solved.
"If the person you are talking to doesn't appear to be listening, be patient. It may simply be that he has a small piece of fluff in his ear." - A.A. Milne (Winnie-the-Pooh)
Offline
#16 2014-06-24 12:24:10
- siavashserver
- Member
- Registered: 2011-02-11
- Posts: 73
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
@Da_Coynul : Thank you very much! Fixed the issue for me
EDIT: I've this issue with a USB 3.0 Seagate Backup Plus 1TB; And my motherboard is an ASUS P5Q, which supports USB 2.
Bus 001 Device 002: ID 0bc2:a003 Seagate RSS LLC Backup Plus
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0bc2 Seagate RSS LLC
idProduct 0xa003 Backup Plus
bcdDevice 8.36
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 85
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8b EP 11 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0a EP 10 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 98
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x08 EP 8 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Command pipe (0x01)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x89 EP 9 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Status pipe (0x02)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0a EP 10 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8b EP 11 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-in pipe (0x03)Last edited by siavashserver (2014-06-24 13:26:35)
Offline
#17 2014-06-27 15:07:16
- Endres
- Member
- Registered: 2012-08-02
- Posts: 5
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
Got that issue with an USB3 Anker Hard Disk Enclosure only using USB3. While connecting it via a USB2 Cable it works. ID is 357d:7788.
Using the workaround it also works with USB3. Thanks.
Offline
#18 2014-06-27 16:59:50
- Atronach
- Banned
- Registered: 2010-11-13
- Posts: 48
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
The quirk helped me too (Hitachi Touro Desk Pro), I just wonder where did you found the quirk flag "u"? What does it do exactly?...out of curiosity. I've looked into /usr/lib/modules/3.15.1-1-ARCH/build/Documentation/kernel-parameters.txt (supplied by the linux-docs package) where a lof of usb-storage quirk flags are described but none such as the "u" - why it isn't there and where can I find it documented? Also if it merely disables the uas module for the specified device why disabling the module globally by adding
install uas /bin/false to a /etc/modprobe.d *.conf file doesn't help? Thanks.
Last edited by Atronach (2014-06-27 17:05:38)
Offline
#19 2014-06-27 19:40:43
- R00KIE
- Forum Fellow
- From: Between a computer and a chair
- Registered: 2008-09-14
- Posts: 4,734
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
@Atronach
Your question is a good question, the u flag is not (yet?) documented in the docs. Looking at the source code this can be found:
case 'u':
f |= US_FL_IGNORE_UAS;This seems to be exactly what the doctor ordered and it's going to be useful to me too, I have just been bitten by this with a new external HD I bought.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
#20 2014-06-27 22:19:27
- Da_Coynul
- Member
- From: United States of America
- Registered: 2010-10-02
- Posts: 85
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
Atronach -
There is a thread in the linux-usb mailing list archives where the rationale for this method of disabling uas was discussed. I found the actual quirk by looking through the source code.
Jonathan
The quirk helped me too (Hitachi Touro Desk Pro), I just wonder where did you found the quirk flag "u"? What does it do exactly?...out of curiosity. I've looked into /usr/lib/modules/3.15.1-1-ARCH/build/Documentation/kernel-parameters.txt (supplied by the linux-docs package) where a lof of usb-storage quirk flags are described but none such as the "u" - why it isn't there and where can I find it documented? Also if it merely disables the uas module for the specified device why disabling the module globally by adding
install uas /bin/falseto a /etc/modprobe.d *.conf file doesn't help? Thanks.
Last edited by Da_Coynul (2014-06-28 00:41:44)
Offline
#21 2014-06-28 07:16:10
- R00KIE
- Forum Fellow
- From: Between a computer and a chair
- Registered: 2008-09-14
- Posts: 4,734
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
If using the quirk for usb-storage then blacklisting uas does not seem to be needed, tested it just now with my disk. On the other hand blacklisting uas might leave you scratching your head later on why something does not get detected.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
#22 2014-06-28 13:06:20
- Atronach
- Banned
- Registered: 2010-11-13
- Posts: 48
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
...blacklisting uas does not seem to be needed...
But of course, by disabling uas globally I actually meant without using the quirk at the same time. The idea was to fix the issue for all the affected devices so I would not have to create the quirk for every new device I'd experience the issue with, at least for the time being until the bug is taken care of.
However I have only one device affected by this so I'm happy with the quirk alone, I was just little confused and thinking out loud why disabling uas globally doesn't fix the issue as the quirk does (supposing it only disables uas...).
Last edited by Atronach (2014-06-28 15:52:53)
Offline
#23 2014-06-28 13:59:57
- R00KIE
- Forum Fellow
- From: Between a computer and a chair
- Registered: 2008-09-14
- Posts: 4,734
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
From my limited test I'd say that it's not possible to disable it globally without recompiling the kernel without uas support, unless a generic vid:pid (something like *:* I didn't test but it might work) can be passed as a quick, otherwise if you just blacklist uas then anything that would require uas will not work.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
#24 2014-06-28 20:37:38
- rubenvb
- Member
- Registered: 2011-01-14
- Posts: 101
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
I've run into the same problem. lsusb -v snipped to include my external USB3.0 HDD enclosure:
Bus 008 Device 002: ID 174c:5106 ASMedia Technology Inc. Transcend StoreJet 25M3
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x174c ASMedia Technology Inc.
idProduct 0x5106 Transcend StoreJet 25M3
bcdDevice 0.01
iManufacturer 2 ASMedia
iProduct 3 AS2105
iSerial 1 00000000000000000000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 85
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 98
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-in pipe (0x03)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Status pipe (0x02)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Command pipe (0x01)
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 2047 micro seconds
Device Status: 0x0001
Self Powered I can confirm that adding a .conf file to /etc/modprobe.d with (note to the careless reader: these specific values are only for the hardware shown above):
options usb-storage quirks=0x174c:0x5106:uas suggested above works around the issue for me.
This was my first break-on-upgrade and it happening on the kernel itself...
It makes me think about installing Debian.
/sarcasm
Offline
#25 2014-07-08 23:06:09
- wolfdogg
- Member
- From: Portland, OR, USA
- Registered: 2011-05-21
- Posts: 545
Re: uas problem in linux 3.15.1, need advice on the problem [SOLVED]
same problem, using external usb harddrive,
a couple keywords that need to be in this thread which helped me understand this was related to UAS are found in dmesg output is uas_eh_abort_handler, see below
dmesg | less | grep sdb
[ 7.447069] sd 6:0:0:0: [sdb] 488378645 4096-byte logical blocks: (2.00 TB/1.81 TiB)
[ 7.448566] sd 6:0:0:0: [sdb] Write Protect is off
[ 7.448569] sd 6:0:0:0: [sdb] Mode Sense: 2b 00 10 08
[ 7.449690] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 7.451692] sd 6:0:0:0: [sdb] 488378645 4096-byte logical blocks: (2.00 TB/1.81 TiB)
[ 7.499963] sdb: sdb1
[ 7.500430] sd 6:0:0:0: [sdb] 488378645 4096-byte logical blocks: (2.00 TB/1.81 TiB)
[ 7.503680] sd 6:0:0:0: [sdb] Attached SCSI disk
[ 9.061868] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem
[ 39.411469] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2b80 tag 0, inflight: CMD
[ 39.411598] sd 6:0:0:0: [sdb] abort completed
[ 39.411626] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3900 tag 1, inflight: CMD
[ 39.411957] sd 6:0:0:0: [sdb] abort completed
[ 39.411985] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3480 tag 2, inflight: CMD
[ 39.432830] sd 6:0:0:0: [sdb] abort completed
[ 39.432858] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3a80 tag 3, inflight: CMD
[ 39.433202] sd 6:0:0:0: [sdb] abort completed
[ 39.433230] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3c00 tag 4, inflight: CMD
[ 39.433575] sd 6:0:0:0: [sdb] abort completed
[ 39.433603] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3d80 tag 5, inflight: CMD
[ 39.433936] sd 6:0:0:0: [sdb] abort completed
[ 39.433964] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3780 tag 6, inflight: CMD
[ 39.434345] sd 6:0:0:0: [sdb] abort completed
[ 39.434373] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3000 tag 7, inflight: CMD
[ 39.434661] sd 6:0:0:0: [sdb] abort completed
[ 39.434674] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2e80 tag 8, inflight: CMD
[ 39.435037] sd 6:0:0:0: [sdb] abort completed
[ 39.435084] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3600 tag 9, inflight: CMD
[ 39.435411] sd 6:0:0:0: [sdb] abort completed
[ 39.435455] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2880 tag 10, inflight: CMD
[ 39.435662] sd 6:0:0:0: [sdb] abort completed
[ 39.435706] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2d00 tag 11, inflight: CMD
[ 39.436035] sd 6:0:0:0: [sdb] abort completed
[ 39.436078] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2700 tag 12, inflight: CMD
[ 39.436286] sd 6:0:0:0: [sdb] abort completed
[ 39.436329] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2580 tag 13, inflight: CMD
[ 39.436661] sd 6:0:0:0: [sdb] abort completed
[ 39.436704] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2400 tag 14, inflight: CMD
[ 39.437036] sd 6:0:0:0: [sdb] abort completed
[ 39.437079] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2280 tag 15, inflight: CMD
[ 39.437410] sd 6:0:0:0: [sdb] abort completed
[ 39.437454] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3300 tag 16, inflight: CMD
[ 39.437785] sd 6:0:0:0: [sdb] abort completed
[ 39.437828] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2a00 tag 17, inflight: CMD
[ 39.438160] sd 6:0:0:0: [sdb] abort completed
[ 39.438205] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1f80 tag 18, inflight: CMD
[ 39.438535] sd 6:0:0:0: [sdb] abort completed
[ 39.438578] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1380 tag 19, inflight: CMD
[ 39.438909] sd 6:0:0:0: [sdb] abort completed
[ 39.438954] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1c80 tag 20, inflight: CMD
[ 39.439284] sd 6:0:0:0: [sdb] abort completed
[ 39.439328] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1e00 tag 21, inflight: CMD
[ 39.439662] sd 6:0:0:0: [sdb] abort completed
[ 39.439676] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1b00 tag 22, inflight: CMD
[ 39.440076] sd 6:0:0:0: [sdb] abort completed
[ 39.440104] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1500 tag 23, inflight: CMD
[ 39.440434] sd 6:0:0:0: [sdb] abort completed
[ 39.440461] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3180 tag 24, inflight: CMD
[ 39.440829] sd 6:0:0:0: [sdb] abort completed
[ 39.440856] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1680 tag 25, inflight: CMD
[ 39.441160] sd 6:0:0:0: [sdb] abort completed
[ 39.441172] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1200 tag 26, inflight: CMD
[ 39.441536] sd 6:0:0:0: [sdb] abort completed
[ 39.441582] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf0f00 tag 27, inflight: CMD
[ 39.441909] sd 6:0:0:0: [sdb] abort completed
[ 39.441951] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2100 tag 28, inflight: CMD
[ 39.442284] sd 6:0:0:0: [sdb] abort completed
[ 39.442327] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf0d80 tag 29, inflight: CMD
[ 39.442659] sd 6:0:0:0: [sdb] abort completed
[ 39.442700] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1980 tag 30, inflight: CMD
[ 39.443033] sd 6:0:0:0: [sdb] abort completed
[ 39.443075] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf0a80 tag 31, inflight: CMD
[ 39.443284] sd 6:0:0:0: [sdb] abort completed
[ 73.430621] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2b80 tag 0, inflight: CMD
[ 73.430715] sd 6:0:0:0: [sdb] abort completed
[ 73.430744] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3900 tag 1, inflight: CMD
[ 73.431097] sd 6:0:0:0: [sdb] abort completed
[ 73.431126] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3480 tag 2, inflight: CMD
[ 73.645299] sd 6:0:0:0: [sdb] abort completed
[ 73.645358] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3a80 tag 3, inflight: CMD
[ 73.645801] sd 6:0:0:0: [sdb] abort completed
[ 73.645857] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3c00 tag 4, inflight: CMD
[ 73.646307] sd 6:0:0:0: [sdb] abort completed
[ 73.646363] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3d80 tag 5, inflight: CMD
[ 73.646790] sd 6:0:0:0: [sdb] abort completed
[ 73.646846] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3780 tag 6, inflight: CMD
[ 73.647135] sd 6:0:0:0: [sdb] abort completed
[ 73.647163] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3000 tag 7, inflight: CMD
[ 73.647513] sd 6:0:0:0: [sdb] abort completed
[ 73.647527] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2e80 tag 8, inflight: CMD
[ 73.647923] sd 6:0:0:0: [sdb] abort completed
[ 73.647952] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3600 tag 9, inflight: CMD
[ 73.648295] sd 6:0:0:0: [sdb] abort completed
[ 73.648323] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2880 tag 10, inflight: CMD
[ 73.648674] sd 6:0:0:0: [sdb] abort completed
[ 73.648702] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2d00 tag 11, inflight: CMD
[ 73.649031] sd 6:0:0:0: [sdb] abort completed
[ 73.649059] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2700 tag 12, inflight: CMD
[ 73.649382] sd 6:0:0:0: [sdb] abort completed
[ 73.649395] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2580 tag 13, inflight: CMD
[ 73.649754] sd 6:0:0:0: [sdb] abort completed
[ 73.649764] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2400 tag 14, inflight: CMD
[ 73.650130] sd 6:0:0:0: [sdb] abort completed
[ 73.650139] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2280 tag 15, inflight: CMD
[ 73.650505] sd 6:0:0:0: [sdb] abort completed
[ 73.650514] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3300 tag 16, inflight: CMD
[ 73.650880] sd 6:0:0:0: [sdb] abort completed
[ 73.650928] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2a00 tag 17, inflight: CMD
[ 73.651255] sd 6:0:0:0: [sdb] abort completed
[ 73.651299] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1f80 tag 18, inflight: CMD
[ 73.651630] sd 6:0:0:0: [sdb] abort completed
[ 73.651675] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1380 tag 19, inflight: CMD
[ 73.652006] sd 6:0:0:0: [sdb] abort completed
[ 73.652050] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1c80 tag 20, inflight: CMD
[ 73.652380] sd 6:0:0:0: [sdb] abort completed
[ 73.652424] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1e00 tag 21, inflight: CMD
[ 73.652755] sd 6:0:0:0: [sdb] abort completed
[ 73.652801] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1b00 tag 22, inflight: CMD
[ 73.653129] sd 6:0:0:0: [sdb] abort completed
[ 73.653155] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1500 tag 23, inflight: CMD
[ 73.653505] sd 6:0:0:0: [sdb] abort completed
[ 73.653550] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf3180 tag 24, inflight: CMD
[ 73.653880] sd 6:0:0:0: [sdb] abort completed
[ 73.653908] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1680 tag 25, inflight: CMD
[ 73.654254] sd 6:0:0:0: [sdb] abort completed
[ 73.654299] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1200 tag 26, inflight: CMD
[ 73.654630] sd 6:0:0:0: [sdb] abort completed
[ 73.654675] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf0f00 tag 27, inflight: CMD
[ 73.655005] sd 6:0:0:0: [sdb] abort completed
[ 73.655049] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2100 tag 28, inflight: CMD
[ 73.655380] sd 6:0:0:0: [sdb] abort completed
[ 73.655424] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf0d80 tag 29, inflight: CMD
[ 73.655754] sd 6:0:0:0: [sdb] abort completed
[ 73.655800] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1980 tag 30, inflight: CMD
[ 73.656129] sd 6:0:0:0: [sdb] abort completed
[ 73.656155] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf0a80 tag 31, inflight: CMD
[ 73.656504] sd 6:0:0:0: [sdb] abort completed
[ 107.343140] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf2100 tag 28, inflight: CMD
[ 107.343511] sd 6:0:0:0: [sdb] abort completed
[ 107.343540] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf0d80 tag 29, inflight: CMD
[ 107.343885] sd 6:0:0:0: [sdb] abort completed
[ 107.343913] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1980 tag 30, inflight: CMD
[ 107.344262] sd 6:0:0:0: [sdb] abort completed
[ 107.344290] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf0a80 tag 31, inflight: CMD
[ 107.344634] sd 6:0:0:0: [sdb] abort completed
[ 107.344663] sd 6:0:0:0: [sdb] uas_eh_abort_handler ffff880220cf1800 tag 0, inflight: CMD
[ 107.345009] sd 6:0:0:0: [sdb] abort completed
[ 110.508458] EXT4-fs (sdb1): error loading journalthanks, i too can confirm this worked https://bbs.archlinux.org/viewtopic.php … 2#p1428782
Last edited by wolfdogg (2014-07-08 23:15:37)
Offline