On Fri, 8 Apr 2005, Andrew Morton wrote: > I have a USB hard disk caddy which appears to be a hub in its own right. It > is > recognised as a ScanLogic USB hub, but the attached disk is never enumerated.
That's wrong. The disk _is_ enumerated and it is recognized as a USB mass storage device. For more information you should turn on the usb-storage verbose debugging option in the kernel configuration. (And by the way, there's nothing in your log to indicate that the disk caddy is recognized as a USB hub, ScanLogic or otherwise.) > The output from /var/log/messages is: > Apr 8 22:07:50 opc kernel: usb 1-1: new full speed USB device using uhci_hcd > and address 2 > Apr 8 22:07:50 opc kernel: scsi0 : SCSI emulation for USB Mass Storage > devices See the line above? It's present because the device was recognized as a disk and the usb-storage driver was loaded. > Apr 8 22:08:19 opc kernel: hub 1-0:1.0: port 1 disabled by hub (EMI?), re- > enabling... This line indicates that the device misbehaved somehow. There's a good chance the usb-storage debugging log will tell us why. > Apr 8 22:08:20 opc kernel: usb 1-1: reset full speed USB device using > uhci_hcd > and address 2 > Apr 8 22:08:20 opc kernel: usb 1-1: device not accepting address 2, error -22 > Apr 8 22:08:20 opc kernel: usb 1-1: reset full speed USB device using > uhci_hcd > and address 2 > Apr 8 22:08:21 opc kernel: usb 1-1: device not accepting address 2, error -22 > Apr 8 22:08:21 opc kernel: usb 1-1: reset full speed USB device using > uhci_hcd > and address 2 > Apr 8 22:08:21 opc kernel: usb 1-1: device descriptor read/64, error -19 > Apr 8 22:08:21 opc kernel: usb 1-1: device descriptor read/64, error -19 > Apr 8 22:08:21 opc kernel: usb 1-1: reset full speed USB device using > uhci_hcd > and address 2 > Apr 8 22:08:21 opc kernel: usb 1-1: device descriptor read/64, error -19 > Apr 8 22:08:22 opc kernel: usb 1-1: device descriptor read/64, error -19 > Apr 8 22:08:22 opc kernel: scsi: Device offlined - not ready after error > recovery: host 0 channel 0 id 0 lun 0 That shows usb-storage attempting to recover from the device's error. Unfortunately the recovery attempt failed. > The first 2 lines appear immediately, but the rest take some 20 seconds to > appear. That delay is due to usb-storage trying to do a class-specific device reset. Alan Stern ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel