aborts in usb-storage in branch 2.6
Hi
I experience aborts with external usb hd, that also pause all disk operations for some seconds.
It doesn't happen with 2.4.21 kernel.
Please tell me if I can do anything useful to debug the problem. I can use kgdb or other techniques.
It's getting very annoying since the disk stays for more than 10 seconds without responding.
usb-storage: usb_stor_control_msg: rq=01 rqtype=02 value=0000 index=88 len=0
usb-storage: usb_stor_clear_halt: result = 0
usb-storage: Attempting to get CSW (2nd try)...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code -32; transferred 0/13
usb-storage: clearing endpoint halt for pipe 0xc0040280
usb-storage: usb_stor_control_msg: rq=01 rqtype=02 value=0000 index=88 len=0
usb-storage: usb_stor_clear_halt: result = 0
usb-storage: Bulk status result = 2
usb-storage: -- transport indicates error, resetting
usb-storage: usb_stor_Bulk_reset called
usb-storage: usb_stor_control_msg: rq=ff rqtype=21 value=0000 index=00 len=0
[ACPI Debug] String: ==Battery1 _BST==
[ACPI Debug] String: ==Battery1 _BST==
b-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
usb-storage: Bulk Command S 0x43425355 T 0x1162 L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
Regards.
Signature · 4 lines
Pedro Larroy Tovar | piotr%member.fsf.org Software patents are a threat to innovation in Europe please check: http://www.eurolinux.org/
Quoted 6 lines · Pedro Larroy
Hi
I experience aborts with external usb hd, that also pause all disk operations for some seconds.
Quoted 7 lines
It doesn't happen with 2.4.21 kernel.
Please tell me if I can do anything useful to debug the problem. I can use kgdb or other techniques.
It's getting very annoying since the disk stays for more than 10 seconds without responding.
Can you send more of the debugging log? The portion you included didn't contain any context, making it hard to judge what the problem was.
Alan Stern