usb-starge not working in the latest kernel 2.4

usb-starge not working in the latest kernel 2.4

[Tomita, Haruo]

Dear Alan,

I've tested usb-storage with the 2.6.0-test2-bk2 kernel version,
It seems that 2.6 kernel version is stable. 
However, 2.4 version is unstable.

The host  controller mPD270100 of NEC and VT6202 of VIA.
When it tested in a high speed multihub, it operated about two weeks. 
However, it became the following errors when the number of devices was one.
I think that it is not failure of a device.
Is it the problem of error handling?

This error was generated in the latest kernel 2.4.22.

usb-storage: usb_stor_transfer_partial(): xfer 2048 bytes
usb-storage: usb_stor_bulk_msg() returned 0 xferred 2048/2048
usb-storage: usb_stor_transfer_partial(): transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: Bulk status result = 0
usb-storage: Bulk status Sig 0x53425355 T 0x7862f6 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Command READ_10 (10 bytes)
usb-storage: 28 00 00 02 e5 23 00 00 01 00 00 00
usb-storage: Bulk command S 0x43425355 T 0x7862f7 Trg 0 LUN 0 L 2048 F 128 CL 12
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_transfer_partial(): xfer 2048 bytes
usb-storage: usb_stor_bulk_msg() returned 0 xferred 2048/2048
usb-storage: usb_stor_transfer_partial(): transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: Bulk status result = 0
usb-storage: Bulk status Sig 0x53425355 T 0x7862f7 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Command READ_10 (10 bytes)
usb-storage: 28 00 00 02 e5 24 00 00 3f 00 00 00
usb-storage: Bulk command S 0x43425355 T 0x7862f8 Trg 0 LUN 0 L 129024 F 128 CL 12
usb-storage: command_abort() called
usb-storage: Bulk command transfer result=-104
usb-storage: -- transport indicates command was aborted
usb-storage: Bulk reset requested
usb_control/bulk_msg: timeout
usb-storage: Bulk soft reset failed -110
usb-storage: scsi command aborted
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage: 00 00 00 00 00 00 00 00 3f 00 00 00
usb-storage: Bulk command S 0x43425355 T 0x7862f9 Trg 0 LUN 0 L 0 F 0 CL 12
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: command_abort() called
usb-storage: -- transport indicates command was aborted
usb-storage: Bulk reset requested
usb_control/bulk_msg: timeout
usb-storage: Bulk soft reset failed -110
usb-storage: scsi command aborted
usb-storage: *** thread sleeping.
usb-storage: device_reset() called
usb-storage: Bulk reset requested
usb_control/bulk_msg: timeout
usb-storage: Bulk soft reset failed -110
usb-storage: bus_reset() called
hub.c: port 1, portstatus 511, change 0, 480 Mb/s
hub.c: port 1 of hub 1 not reset yet, waiting 10ms
hub.c: port 1, portstatus 511, change 0, 480 Mb/s
hub.c: port 1 of hub 1 not reset yet, waiting 10ms
ehci_hcd 00:0c.2: port 1 high speed
ehci_hcd 00:0c.2: GetStatus port 1 status 001005 POWER sig=se0  PE CONNECT
hub.c: port 1, portstatus 503, change 10, 480 Mb/s
ehci_hcd 00:0c.2: devpath 1 ep0out 3strikes
hub.c: USB device not accepting new address (error=-71)
ehci_hcd 00:0c.2: GetStatus port 1 status 001803 POWER sig=j  CSC CONNECT
hub.c: port 1, portstatus 501, change 1, 480 Mb/s
hub.c: port 1 connection change
hub.c: port 1, portstatus 501, change 1, 480 Mb/s
usb.c: USB disconnect on device 00:0c.2-1 address 2
usb-storage: storage_disconnect() called
usb-storage: -- releasing main URB
usb-storage: -- usb_unlink_urb() returned -19
usb.c: kusbd: /sbin/hotplug remove 2
ehci_hcd 00:0c.2: free_config 1 devnum 2
hub.c: port 1, portstatus 501, change 0, 480 Mb/s
hub.c: port 1, portstatus 501, change 0, 480 Mb/s
hub.c: port 1, portstatus 501, change 0, 480 Mb/s
hub.c: port 1, portstatus 501, change 0, 480 Mb/s
hub.c: port 1, portstatus 511, change 0, 480 Mb/s
hub.c: port 1 of hub 1 not reset yet, waiting 10ms
hub.c: port 1, portstatus 511, change 0, 480 Mb/s
hub.c: port 1 of hub 1 not reset yet, waiting 10ms
ehci_hcd 00:0c.2: port 1 high speed
ehci_hcd 00:0c.2: GetStatus port 1 status 001005 POWER sig=se0  PE CONNECT
hub.c: port 1, portstatus 503, change 10, 480 Mb/s
hub.c: new USB device 00:0c.2-1, assigned address 3
usb.c: kmalloc IF dfe6d960, numif 1
usb.c: new device strings: Mfr=73, Product=87, SerialNumber=107
usb.c: USB device number 3 default language ID 0x409
Manufacturer: Plextor Corp.
Product: USB Storage Adapter
SerialNumber: 11100E000052487C
usb-storage: act_altsettting is 0
usb-storage: id_index calculated to be: 92
usb-storage: Array length appears to be: 98
usb-storage: USB Mass Storage device detected
usb-storage: Endpoints: In: 0xdfe641f4 Out: 0xdfe641e0 Int: 0xdfe64208 (Period 9)
usb-storage: Found existing GUID 093b001211100e000052487c
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
usb.c: usb-storage driver claimed interface dfe6d960
usb.c: kusbd: /sbin/hotplug add 3
hub.c: port 2, portstatus 100, change 0, 12 Mb/s
hub.c: port 3, portstatus 100, change 0, 12 Mb/s
hub.c: port 4, portstatus 100, change 0, 12 Mb/s
usb-storage: host_reset() requested but not implemented
scsi: device set offline - command error recover failed: host 0 channel 0 id 0 lun 0
SCSI cdrom error : host 0 channel 0 id 0 lun 0 return code = 6050000
 I/O error: dev 0b:00, sector 758928
 I/O error: dev 0b:00, sector 758932
 I/O error: dev 0b:00, sector 759180
 I/O error: dev 0b:00, sector 758928
 
P.S.
Please teach me how to analyze the root cause of this isseu.

Regards,
Haruo

Re: usb-starge not working in the latest kernel 2.4

[Alan Stern]

On Fri, 29 Aug 2003, Tomita, Haruo wrote:

> Dear Alan,
> 
> I've tested usb-storage with the 2.6.0-test2-bk2 kernel version,
> It seems that 2.6 kernel version is stable. 
> However, 2.4 version is unstable.
> 
> The host  controller mPD270100 of NEC and VT6202 of VIA.
> When it tested in a high speed multihub, it operated about two weeks. 
> However, it became the following errors when the number of devices was one.
> I think that it is not failure of a device.
> Is it the problem of error handling?
> 
> This error was generated in the latest kernel 2.4.22.

> usb-storage: Attempting to get CSW...
> usb-storage: Bulk status result = 0
> usb-storage: Bulk status Sig 0x53425355 T 0x7862f7 R 0 Stat 0x0

The device worked here, reporting the status from the previous command.

> usb-storage: scsi cmd done, result=0x0
> usb-storage: *** thread sleeping.
> usb-storage: queuecommand() called
> usb-storage: *** thread awakened.
> usb-storage: Command READ_10 (10 bytes)
> usb-storage: 28 00 00 02 e5 24 00 00 3f 00 00 00
> usb-storage: Bulk command S 0x43425355 T 0x7862f8 Trg 0 LUN 0 L 129024 F 128 CL 12
> usb-storage: command_abort() called

It stopped working here.  The driver tried to send the next command but 
the drive never acknowledged receiving it.

> usb-storage: Bulk command transfer result=-104
> usb-storage: -- transport indicates command was aborted
> usb-storage: Bulk reset requested
> usb_control/bulk_msg: timeout
> usb-storage: Bulk soft reset failed -110

After this point, no communication with the drive worked.  Eventually a 
USB port reset was tried:

> usb-storage: bus_reset() called
> hub.c: port 1, portstatus 511, change 0, 480 Mb/s
> hub.c: port 1 of hub 1 not reset yet, waiting 10ms
> hub.c: port 1, portstatus 511, change 0, 480 Mb/s
> hub.c: port 1 of hub 1 not reset yet, waiting 10ms
> ehci_hcd 00:0c.2: port 1 high speed
> ehci_hcd 00:0c.2: GetStatus port 1 status 001005 POWER sig=se0  PE CONNECT
> hub.c: port 1, portstatus 503, change 10, 480 Mb/s
> ehci_hcd 00:0c.2: devpath 1 ep0out 3strikes
> hub.c: USB device not accepting new address (error=-71)

This "not accepting new address" problem for ECHI was recently addressed 
by a new patch.  See

http://sourceforge.net/mailarchive/message.php?msg_id=5927120

Maybe once that's fixed the error recovery will work better.

> Please teach me how to analyze the root cause of this isseu.

It's not easy to do.  Nothing special stands out.  One small possibility 
is the length of the READ command where the error occurred: 129024 bytes.  
Check through earlier parts of the log and see if it contains successful 
READs or WRITEs for that much data.  Some devices have an upper limit on 
how much they can transfer in a single command and don't like it when that 
limit is exceeded.

Did you said that the device works well when connected through a high
speed hub, but it fails when connected directly to the computer?  That's a 
big clue, but I don't know what it means.

Alan Stern

Re: usb-starge not working in the latest kernel 2.4

[David Brownell]

Alan Stern wrote:
> On Fri, 29 Aug 2003, Tomita, Haruo wrote:
> 
>>usb-storage: Command READ_10 (10 bytes)
>>usb-storage: 28 00 00 02 e5 24 00 00 3f 00 00 00
>>usb-storage: Bulk command S 0x43425355 T 0x7862f8 Trg 0 LUN 0 L 129024 F 128 CL 12
>>usb-storage: command_abort() called
> 
> 
> It stopped working here.  The driver tried to send the next command but 
> the drive never acknowledged receiving it.

It might also be useful to find just how many of those 126 KBytes
were successfully transferred before the abort.

Also:  is this one of those cases where 2.6 works and 2.4 doesn't?
The i/o patterns are very different ...


> Did you said that the device works well when connected through a high
> speed hub, but it fails when connected directly to the computer?  That's a 
> big clue, but I don't know what it means.

I don't either.

- Dave

Re: usb-starge not working in the latest kernel 2.4

[Alan Stern]

On Fri, 29 Aug 2003, David Brownell wrote:

> Alan Stern wrote:
> > It stopped working here.  The driver tried to send the next command but 
> > the drive never acknowledged receiving it.
> 
> It might also be useful to find just how many of those 126 KBytes
> were successfully transferred before the abort.

I think none of them were.  Or at least, no more than the first
scatter-gather block.  Under 2.4, usb-storage sends the s-g blocks one at
a time, by hand, and reports the completion of each one.  But the log 
didn't contain any such reports.

Alan Stern



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

RE: usb-starge not working in the latest kernel 2.4

[Tomita, Haruo]

Hi Alan,

Thank you for your replay.

A portion is omitted in the first half.

Haruo> usb-storage: bus_reset() called
Haruo> hub.c: port 1, portstatus 511, change 0, 480 Mb/s
Haruo> hub.c: port 1 of hub 1 not reset yet, waiting 10ms
Haruo> hub.c: port 1, portstatus 511, change 0, 480 Mb/s
Haruo> hub.c: port 1 of hub 1 not reset yet, waiting 10ms
Haruo> ehci_hcd 00:0c.2: port 1 high speed
Haruo> ehci_hcd 00:0c.2: GetStatus port 1 status 001005 POWER 
Haruo> sig=se0  PE CONNECT
Haruo> hub.c: port 1, portstatus 503, change 10, 480 Mb/s
Haruo> ehci_hcd 00:0c.2: devpath 1 ep0out 3strikes
Haruo> hub.c: USB device not accepting new address (error=-71)
 
Alan> This "not accepting new address" problem for ECHI was 
Alan> recently addressed  by a new patch.  See
Alan> http://sourceforge.net/mailarchive/message.php?msg_id=5927120
Alan> Maybe once that's fixed the error recovery will work better.

I think that this patch is related with usb reset.
If it goes through the transaction translator of a 2.0 hub, 
because after resetting the device, usb_reset_device() does a 
set_address(), but the ehci driver sends this to the device's previous 
address, when it's post-reset address is 0.
I will test using kernel 2.4.22-bk6.

Haruo> Please teach me how to analyze the root cause of this issue.
 
Alan> It's not easy to do.  Nothing special stands out.  
Alan> One small possibility 
Alan> is the length of the READ command where the error occurred: 
Alan> 129024 bytes.  
Alan> Check through earlier parts of the log and see if it contains 
Alan> successful 
Alan> READs or WRITEs for that much data.  Some devices have an 
Alan> upper limit on 
Alan> how much they can transfer in a single command and don't like 
Alan> it when that  limit is exceeded.

OK, I will think.

Alan> Did you said that the device works well when connected through a high
Alan> speed hub, but it fails when connected directly to the 
Alan> computer?

It seems that it stabilizes and operates 
when two devices are connected by high speed hub. 
However, it becomes an error in using only one device.
The high speed hub was used when using two devices.
In the case of one device, device connected the computer directly.

Thanks!!
Haruo

RE: usb-starge not working in the latest kernel 2.4

[Tomita, Haruo]

Hi Dave,

Thanks!!

Haruo>usb-storage: Command READ_10 (10 bytes)
Haruo>usb-storage: 28 00 00 02 e5 24 00 00 3f 00 00 00
Haruo>usb-storage: Bulk command S 0x43425355 T 0x7862f8 Trg 0 LUN 
Haruo> 0 L 129024 F 128 CL 12
Haruo>usb-storage: command_abort() called

Alan> It stopped working here.  The driver tried to send the next 
Alan> command but the drive never acknowledged receiving it.

Dave> It might also be useful to find just how many of those 126 KBytes
Dave> were successfully transferred before the abort.

How can it check?

Dave> Also:  is this one of those cases where 2.6 works and 2.4 doesn't?
Dave> The i/o patterns are very different ...
 
Is it the meaning that operation changes with  i/o patterns?
--
Haruo

RE: usb-starge not working in the latest kernel 2.4

[Tomita, Haruo]

Hi Alan,

Alan> This "not accepting new address" problem for ECHI was 
Alan> recently addressed  by a new patch.  See
Alan> http://sourceforge.net/mailarchive/message.php?msg_id=5927120
Alan> Maybe once that's fixed the error recovery will work better.
 
I tested using kernel 2.4.22-bk6. It failed by the following two patterns.
1. Bulk command transfer result=-104
2.  usb_stor_bulk_msg() returned -32

The detailed message is as follows.

1. Bulk command transfer result=-104

usb-storage: Bulk status Sig 0x53425355 T 0x93534d R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Command READ_10 (10 bytes)
usb-storage: 28 00 00 01 ce 21 00 00 01 00 00 00
usb-storage: Bulk command S 0x43425355 T 0x93534e Trg 0 LUN 0 L 2048 F 128 CL 12
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_transfer_partial(): xfer 2048 bytes
usb-storage: usb_stor_bulk_msg() returned 0 xferred 2048/2048
usb-storage: usb_stor_transfer_partial(): transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: Bulk status result = 0
usb-storage: Bulk status Sig 0x53425355 T 0x93534e R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Command READ_10 (10 bytes)
usb-storage: 28 00 00 01 ce 22 00 00 3f 00 00 00
usb-storage: Bulk command S 0x43425355 T 0x93534f Trg 0 LUN 0 L 129024 F 128 CL 12
usb-storage: command_abort() called
usb-storage: Bulk command transfer result=-104
usb-storage: -- transport indicates command was aborted
usb-storage: Bulk reset requested
usb_control/bulk_msg: timeout
usb-storage: Bulk soft reset failed -110
usb-storage: scsi command aborted
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage: 00 00 00 00 00 00 00 00 3f 00 00 00
usb-storage: Bulk command S 0x43425355 T 0x935350 Trg 0 LUN 0 L 0 F 0 CL 12
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: command_abort() called
usb-storage: -- transport indicates command was aborted
usb-storage: Bulk reset requested
usb_control/bulk_msg: timeout
usb-storage: Bulk soft reset failed -110
usb-storage: scsi command aborted
usb-storage: *** thread sleeping.
usb-storage: device_reset() called
usb-storage: Bulk reset requested
usb_control/bulk_msg: timeout
usb-storage: Bulk soft reset failed -110
usb-storage: bus_reset() called
hub.c: port 1, portstatus 511, change 0, 480 Mb/s
hub.c: port 1 of hub 1 not reset yet, waiting 10ms
hub.c: port 1, portstatus 511, change 0, 480 Mb/s
hub.c: port 1 of hub 1 not reset yet, waiting 10ms
ehci_hcd 00:0c.2: port 1 high speed
ehci_hcd 00:0c.2: GetStatus port 1 status 001005 POWER sig=se0  PE CONNECT
hub.c: port 1, portstatus 503, change 10, 480 Mb/s
usb.c: ignoring set_interface for dev 3, iface 0, alt 0
usb-storage: Examinging driver usb-storage...skipping ourselves.
usb-storage: bus_reset() complete
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage: 00 00 00 00 00 00 00 00 3f 00 00 00
usb-storage: Bulk command S 0x43425355 T 0x935351 Trg 0 LUN 0 L 0 F 0 CL 12
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: command_abort() called
usb-storage: -- transport indicates command was aborted
usb-storage: Bulk reset requested
usb_control/bulk_msg: timeout
usb-storage: Bulk soft reset failed -110
usb-storage: scsi command aborted
usb-storage: *** thread sleeping.
scsi: device set offline - not ready or command retry failed after bus reset: host 0 channel 0 id 0 lun 0
SCSI cdrom error : host 0 channel 0 id 0 lun 0 return code = 50000
 I/O error: dev 0b:00, sector 473224
 I/O error: dev 0b:00, sector 473228
 I/O error: dev 0b:00, sector 473476
 I/O error: dev 0b:00, sector 473224

2.  usb_stor_bulk_msg() returned -32

usb-storage: usb_stor_transfer_partial(): xfer 2048 bytes
usb-storage: usb_stor_bulk_msg() returned -32 xferred 0/2048
usb-storage: clearing endpoint halt for pipe 0xc0008280
usb-storage: usb_stor_clear_halt: result=0
usb-storage: usb_stor_transfer_partial(): unknown error
usb-storage: Bulk data transfer result 0x2
usb-storage: Attempting to get CSW...
usb-storage: Bulk status result = 0
usb-storage: Bulk status Sig 0x53425355 T 0x528063 R 2048 Stat 0x1
usb-storage: -- transport indicates command failure
usb-storage: Issuing auto-REQUEST_SENSE
usb-storage: Bulk command S 0x43425355 T 0x528064 Trg 0 LUN 0 L 18 F 128 CL 12
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_transfer_partial(): xfer 18 bytes
usb-storage: usb_stor_bulk_msg() returned 0 xferred 18/18
usb-storage: usb_stor_transfer_partial(): transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: Bulk status result = 0
usb-storage: Bulk status Sig 0x53425355 T 0x528064 R 0 Stat 0x0
usb-storage: -- Result from auto-sense is 0
usb-storage: -- code: 0x70, key: 0x2, ASC: 0x4, ASCQ: 0x1
usb-storage: Not Ready: LUN in process of becoming ready
usb-storage: scsi cmd done, result=0x2
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Command READ_10 (12 bytes)
usb-storage: 28 00 00 03 11 63 00 00 01 00 00 00
usb-storage: Bulk command S 0x43425355 T 0x528065 Trg 0 LUN 0 L 2048 F 128 CL 12
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_transfer_partial(): xfer 2048 bytes
usb-storage: usb_stor_bulk_msg() returned -32 xferred 0/2048
usb-storage: clearing endpoint halt for pipe 0xc0008280
usb-storage: usb_stor_clear_halt: result=0
usb-storage: usb_stor_transfer_partial(): unknown error
usb-storage: Bulk data transfer result 0x2
usb-storage: Attempting to get CSW...
usb-storage: Bulk status result = 0
usb-storage: Bulk status Sig 0x53425355 T 0x528065 R 2048 Stat 0x1
usb-storage: -- transport indicates command failure
usb-storage: Issuing auto-REQUEST_SENSE
usb-storage: Bulk command S 0x43425355 T 0x528066 Trg 0 LUN 0 L 18 F 128 CL 12
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_transfer_partial(): xfer 18 bytes
usb-storage: usb_stor_bulk_msg() returned 0 xferred 18/18
usb-storage: usb_stor_transfer_partial(): transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: Bulk status result = 0
usb-storage: Bulk status Sig 0x53425355 T 0x528066 R 0 Stat 0x0
usb-storage: -- Result from auto-sense is 0
usb-storage: -- code: 0x70, key: 0x6, ASC: 0x28, ASCQ: 0x0
usb-storage: Unit Attention: not ready to ready transition
usb-storage: scsi cmd done, result=0x2
usb-storage: *** thread sleeping.
 I/O error: dev 0b:00, sector 804236
 I/O error: dev 0b:00, sector 804240
 I/O error: dev 0b:00, sector 804492
 I/O error: dev 0b:00, sector 804236

Regards,
Haruo 

RE: usb-starge not working in the latest kernel 2.4

[Alan Stern]

On Fri, 5 Sep 2003, Tomita, Haruo wrote:

> I tested using kernel 2.4.22-bk6. It failed by the following two patterns.
> 1. Bulk command transfer result=-104
> 2.  usb_stor_bulk_msg() returned -32

This was two different failures on two separate runs?

> The detailed message is as follows.
> 
> 1. Bulk command transfer result=-104

> usb-storage: Command READ_10 (10 bytes)
> usb-storage: 28 00 00 01 ce 22 00 00 3f 00 00 00
> usb-storage: Bulk command S 0x43425355 T 0x93534f Trg 0 LUN 0 L 129024 F 128 CL 12
> usb-storage: command_abort() called
> usb-storage: Bulk command transfer result=-104
> usb-storage: -- transport indicates command was aborted

This was the same sort of pattern we saw before.  No data was transferred
from the drive, and the command timed out and was aborted.

> usb-storage: bus_reset() called
> hub.c: port 1, portstatus 511, change 0, 480 Mb/s
> hub.c: port 1 of hub 1 not reset yet, waiting 10ms
> hub.c: port 1, portstatus 511, change 0, 480 Mb/s
> hub.c: port 1 of hub 1 not reset yet, waiting 10ms
> ehci_hcd 00:0c.2: port 1 high speed
> ehci_hcd 00:0c.2: GetStatus port 1 status 001005 POWER sig=se0  PE CONNECT
> hub.c: port 1, portstatus 503, change 10, 480 Mb/s
> usb.c: ignoring set_interface for dev 3, iface 0, alt 0
> usb-storage: Examinging driver usb-storage...skipping ourselves.
> usb-storage: bus_reset() complete

This time the bus_reset() routine worked, which is an improvement over 
what you were seeing before.  But the device still didn't respond:

> usb-storage: queuecommand() called
> usb-storage: *** thread awakened.
> usb-storage: Command TEST_UNIT_READY (6 bytes)
> usb-storage: 00 00 00 00 00 00 00 00 3f 00 00 00
> usb-storage: Bulk command S 0x43425355 T 0x935351 Trg 0 LUN 0 L 0 F 0 CL 12
> usb-storage: Bulk command transfer result=0
> usb-storage: Attempting to get CSW...
> usb-storage: command_abort() called
> usb-storage: -- transport indicates command was aborted
> usb-storage: Bulk reset requested
> usb_control/bulk_msg: timeout
> usb-storage: Bulk soft reset failed -110
> usb-storage: scsi command aborted
> usb-storage: *** thread sleeping.
> scsi: device set offline - not ready or command retry failed after bus reset: host 0 channel 0 id 0 lun 0
> SCSI cdrom error : host 0 channel 0 id 0 lun 0 return code = 50000
>  I/O error: dev 0b:00, sector 473224
>  I/O error: dev 0b:00, sector 473228
>  I/O error: dev 0b:00, sector 473476
>  I/O error: dev 0b:00, sector 473224

Once that happened there were no error recovery procedures left to try, so 
the driver gave up and marked the device offline.

There's something a little strange I just noticed in the log.  It's
probably not related to your problem, but we should check it out anyway.  
Please send a copy of /proc/bus/usb/devices, with the drive plugged in.


> 2.  usb_stor_bulk_msg() returned -32

Under what circumstances did this error occur?  It must have been quite 
different from the other error.

> usb-storage: usb_stor_transfer_partial(): xfer 2048 bytes
> usb-storage: usb_stor_bulk_msg() returned -32 xferred 0/2048

> usb-storage: -- code: 0x70, key: 0x2, ASC: 0x4, ASCQ: 0x1
> usb-storage: Not Ready: LUN in process of becoming ready

That's normal.  It means that the drive was just turned on or reset, and 
it's not yet ready to execute commands.

> usb-storage: Unit Attention: not ready to ready transition

More of the same.  This means that the drive just finished its 
initialization and now it's ready to operate.

> usb-storage: scsi cmd done, result=0x2
> usb-storage: *** thread sleeping.
>  I/O error: dev 0b:00, sector 804236
>  I/O error: dev 0b:00, sector 804240
>  I/O error: dev 0b:00, sector 804492
>  I/O error: dev 0b:00, sector 804236

But apparently at this point the SCSI driver got tired of waiting and set 
the drive offline.  This should be fixed in the SCSI driver.  That's why 
it's important to know what you were doing when the error occurred.

Alan Stern



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel