Re: Fwd: Re: portable usb drive problem

On Thursday 05 July 2007, Steve Calfee wrote:
>>     Date: Thu, 05 Jul 2007 18:14:38 -0400
>>
>>On Thursday 05 July 2007, Alan Stern wrote:
>>>On Thu, 5 Jul 2007, Gene Heskett wrote:
>>>>Greetings;
>>>>
>>>>I have a 40GB drive in a usb enclosure that when plugged in, signs on
>>>>like
>>>>this in the dmesg output:
>>>>
>>>>usb 3-3.4.2: uevent
>>>>hub 3-3.4:1.0: debounce: port 2: total 100ms stable 100ms status 0x100
>>>>hub 3-3.4:1.0: state 7 ports 4 chg 0000 evt 0004
>>>>hub 3-3.4:1.0: port 2, status 0101, change 0001, 12 Mb/s
>>>>hub 3-3.4:1.0: debounce: port 2: total 100ms stable 100ms status 0x101
>>>>hub 3-3.4:1.0: port 2 not reset yet, waiting 10ms
>>>>usb 3-3.4.2: new high speed USB device using ehci_hcd and address 12
>>>>hub 3-3.4:1.0: port 2 not reset yet, waiting 10ms
>>>>usb 3-3.4.2: default language 0x0409
>>>>usb 3-3.4.2: new device strings: Mfr=1, Product=2, SerialNumber=3
>>>>usb 3-3.4.2: Product: Maxtor OneTouch III
>>>>usb 3-3.4.2: Manufacturer: Maxtor
>>>>usb 3-3.4.2: SerialNumber: RA01ZFQC
>>>>usb 3-3.4.2: uevent
>>>>usb 3-3.4.2: usb_probe_device
>>>>usb 3-3.4.2: configuration #1 chosen from 1 choice
>>>>usb 3-3.4.2: adding 3-3.4.2:1.0 (config #1, interface 0)
>>>>usb 3-3.4.2:1.0: uevent
>>>>usb 3-3.4.2:1.0: uevent
>>>>libusual 3-3.4.2:1.0: usb_probe_interface
>>>>libusual 3-3.4.2:1.0: usb_probe_interface - got id
>>>>usb-storage 3-3.4.2:1.0: usb_probe_interface
>>>>usb-storage 3-3.4.2:1.0: usb_probe_interface - got id
>>>>scsi2 : SCSI emulation for USB Mass Storage devices
>>>>drivers/usb/core/inode.c: creating file '012'
>>>>usb-storage: device found at 12
>>>>usb-storage: waiting for device to settle before scanning
>>>>usb-storage: device scan complete
>>>>hub 3-3.4:1.0: port 2 not reset yet, waiting 10ms
>>>>usb 3-3.4.2: reset high speed USB device using ehci_hcd and address 12
>>>>usb 3-3.4.2: usb-storage timed out on ep0in len=0/64
>>>>ehci_hcd 0000:00:02.2: devpath 3.4.2 ep0in 3strikes
>>>>ehci_hcd 0000:00:02.2: devpath 3.4.2 ep0in 3strikes
>>>>hub 3-3.4:1.0: port 2 not reset yet, waiting 10ms
>>>>usb 3-3.4.2: device descriptor read/64, error -71
>>>>hub 3-3.4:1.0: port 2 not reset yet, waiting 10ms
>>>>usb_endpoint usbdev3.12_ep01: ep_device_release called for
>>>>usbdev3.12_ep01
>>>>usb_endpoint usbdev3.12_ep82: ep_device_release called for
>>>>usbdev3.12_ep82
>>>>hub 3-3.4:1.0: port 2 not reset yet, waiting 10ms
>>>>usb 3-3.4.2: reset high speed USB device using ehci_hcd and address 12
>>>>hub 3-3.4:1.0: port 2 not reset yet, waiting 10ms
>>>>
>>>>The power led on the case lights up just fine, but the drive doesn't spin
>>>>up. Plugged into my HP lappy (FC5), it spins up and automounts just fine
>>>>but does so at 1.1 speeds.
>>>>
>>>>My config.gz is attached.  What am I missing?
>>>
>>>Does the case use external power or does it run off USB bus power?  If
>>>it is bus-powered, perhaps it isn't getting enough juice.
>>>
>>>>From the looks of the rear of the case, it could use a wall wart, there is
>>>a
>>
>>plugin that says 5 [email protected] amps next to it, but it didn't come with one.
>>
>>When on the lappy, it spins up and works just fine with only one of the
>>dual
>>connector cables plugged in.  The led in the front of the case is just as
>>bright when plugged into a port on this box as it is when plugged into the
>>lappy, hence my reticence to blame the power gods.
>>
>>Since its only a 4 wire connection, I'm not sure how it could effect a
>>non-spinup and still have a nice bright white led which blinks when theres
>>traffic.  As a C.E.T. and electron chaser for at least 55 years now, that
>>doesn't grok, so it stands to reason there may be some sort of an enabling
>>command sent from the lappy that is not being sent when its plugged into
>>this
>>box due to a missing module.  This is 2.6.22-rc7-cfs-v18, whereas the lappy
>>is running a stock, fairly recent FC5 issued kernel.
>>
>>Or at least that's the current theory.
>>
>>>Try turning on CONFIG_USB_STORAGE_DEBUG and see what shows up in the
>>>debugging log.
>>
>>Done, and the build is underway, or maybe even finished.  Yup, done, so
>>I'll
>>save this and reboot, brb.
>>
>>Humm, interesting, when I rebooted it was still plugged into the front
>>panel
>>hub, a 1.1 hub.  And it would not complete the bus scan in post!  I tried
>>to
>>get its attention from the keyboard via the usual vulcan nerve pinch etc,
>>finally got up and walked around to unplug it.  I was going to hit the
>>reset
>>button, but the floppies started seeking the instant I unplugged it and
>>before I could hit the button and the post completed normally.
>>
>>Now, to plug it in after unplugging something else and tail the log.
>>
>>It still takes about 1 minute to give up, and the log is no more verbose
>>than
>>it was.
>>
>>Jul  5 18:06:22 coyote kernel: usb 3-3.4.2: new high speed USB device using
>>ehci_hcd and address 12
>>Jul  5 18:06:22 coyote kernel: usb 3-3.4.2: Product: Maxtor OneTouch III
>>Jul  5 18:06:22 coyote kernel: usb 3-3.4.2: Manufacturer: Maxtor
>>Jul  5 18:06:22 coyote kernel: usb 3-3.4.2: SerialNumber: RA01ZFQC
>>Jul  5 18:06:22 coyote kernel: usb 3-3.4.2: configuration #1 chosen from 1
>>choice
>>Jul  5 18:06:22 coyote kernel: scsi2 : SCSI emulation for USB Mass Storage
>>devices
>>Jul  5 18:06:33 coyote kernel: usb 3-3.4.2: reset high speed USB device
>>using
>>ehci_hcd and address 12
>>Jul  5 18:06:38 coyote kernel: usb 3-3.4.2: device descriptor read/64,
>>error -71
>>Jul  5 18:06:48 coyote kernel: usb 3-3.4.2: reset high speed USB device
>>using
>>ehci_hcd and address 12
>>Jul  5 18:07:15 coyote last message repeated 3 times
>>Jul  5 18:07:15 coyote kernel: scsi 2:0:0:0: scsi: Device offlined - not
>>ready
>>after error recovery
>>
>>And a snip from a grep of my fresh .config:
>>[root@coyote linux-2.6.22-rc7-cfs-v18]# grep USB_STORAGE .config
>># NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
>># may also be needed; see USB_STORAGE Help for more information
>>CONFIG_USB_STORAGE=m
>>CONFIG_USB_STORAGE_DEBUG=y
>># CONFIG_USB_STORAGE_DATAFAB is not set
>># CONFIG_USB_STORAGE_FREECOM is not set
>># CONFIG_USB_STORAGE_ISD200 is not set
>>CONFIG_USB_STORAGE_DPCM=y
>># CONFIG_USB_STORAGE_USBAT is not set
>>CONFIG_USB_STORAGE_SDDR09=y
>>CONFIG_USB_STORAGE_SDDR55=y
>># CONFIG_USB_STORAGE_JUMPSHOT is not set
>># CONFIG_USB_STORAGE_ALAUDA is not set
>># CONFIG_USB_STORAGE_KARMA is not set
>>
>>Any other ideas other than lack of power?  Its plugged into an Alps 7 port
>>USB2.0 hub, which is itself powered from the USB cable plugged into a 2.0
>>port on the rear of the mobo, and everything else plugged into it is
>>working
>>with no obvious problems.
>
>It could still be power. If it is on a root hub - like on a laptop, it can
>get 500ma. When it is on the port of an unpowered hub it can only draw
>100ma.
>
>cat /proc/bus/usb/devices give lots of hard to figure out topology info.
>Also lsusb -v will show you the configuration for your drive and how much
>current (maxpower) that it says it needs. Try comparing the working system
>results with the problem one.
>
>Good Luck, Steve
>
Thanks Steve.  I crawled under the desk and found a root port that was empty, 
one right on the back panel of the mobo.  From messages:

Jul  5 21:32:01 coyote kernel: usb 3-3.4.2: USB disconnect, address 12
Jul  5 21:32:14 coyote kernel: usb 3-3.4.2: new high speed USB device using 
ehci_hcd and address 13
Jul  5 21:32:14 coyote kernel: usb 3-3.4.2: Product: USB Storage
Jul  5 21:32:14 coyote kernel: usb 3-3.4.2: SerialNumber: 000000009317
Jul  5 21:32:14 coyote kernel: usb 3-3.4.2: configuration #1 chosen from 1 
choice
Jul  5 21:32:14 coyote kernel: scsi3 : SCSI emulation for USB Mass Storage 
devices
Jul  5 21:32:19 coyote kernel: scsi 3:0:0:0: Direct-Access     Generic  
STORAGE DEVICE   9317 PQ: 0 ANSI: 0
Jul  5 21:32:19 coyote kernel: scsi 3:0:0:1: Direct-Access     Generic  
STORAGE DEVICE   9317 PQ: 0 ANSI: 0
Jul  5 21:32:19 coyote kernel: scsi 3:0:0:2: Direct-Access     Generic  
STORAGE DEVICE   9317 PQ: 0 ANSI: 0
Jul  5 21:32:19 coyote kernel: scsi 3:0:0:3: Direct-Access     Generic  
STORAGE DEVICE   9317 PQ: 0 ANSI: 0
Jul  5 21:32:19 coyote kernel: sd 3:0:0:0: [sda] Attached SCSI removable disk
Jul  5 21:32:19 coyote kernel: sd 3:0:0:0: Attached scsi generic sg0 type 0
Jul  5 21:32:19 coyote kernel: sd 3:0:0:1: [sdb] Attached SCSI removable disk
Jul  5 21:32:19 coyote kernel: sd 3:0:0:1: Attached scsi generic sg1 type 0
Jul  5 21:32:19 coyote kernel: sd 3:0:0:2: [sdc] Attached SCSI removable disk
Jul  5 21:32:19 coyote kernel: sd 3:0:0:2: Attached scsi generic sg2 type 0
Jul  5 21:32:19 coyote kernel: sd 3:0:0:3: [sdd] Attached SCSI removable disk
Jul  5 21:32:19 coyote kernel: sd 3:0:0:3: Attached scsi generic sg3 type 0
Jul  5 21:43:44 coyote kernel: usb 3-2: new high speed USB device using 
ehci_hcd and address 14
Jul  5 21:43:44 coyote kernel: usb 3-2: Product: Maxtor OneTouch III
Jul  5 21:43:44 coyote kernel: usb 3-2: Manufacturer: Maxtor
Jul  5 21:43:44 coyote kernel: usb 3-2: SerialNumber: RA01ZFQC
Jul  5 21:43:44 coyote kernel: usb 3-2: configuration #1 chosen from 1 choice
Jul  5 21:43:44 coyote kernel: scsi4 : SCSI emulation for USB Mass Storage 
devices
Jul  5 21:43:54 coyote kernel: usb 3-2: reset high speed USB device using 
ehci_hcd and address 14
Jul  5 21:43:59 coyote kernel: usb 3-2: device descriptor read/64, error -71
Jul  5 21:44:10 coyote kernel: usb 3-2: reset high speed USB device using 
ehci_hcd and address 14
Jul  5 21:44:36 coyote last message repeated 3 times
Jul  5 21:44:37 coyote kernel: scsi 4:0:0:0: scsi: Device offlined - not ready 
after error recovery

So its still fubar for some reason.  Firing up the lappy, its fine.

On this box, an lsmod shows this:
usb_storage            50368  0
scsi_mod               77448  3 sg,sd_mod,usb_storage

All as a group.

But on the lappy where it works, clear at the top of the lsmod output is

usb_storage            66049  0
And down in the lower portion of that list is:
scsi_mod              137549  5 usb_storage, sr_mod, sg, libata, sd_mod

So there's a bunch of stuff on the FC5 box that's missing on the FC6 box.  
Starting with libata and sr_mod.  Go look at my .config again I guess.

Also the lsusb -v for that device shows a MaxPower of 100ma, exactly the same 
as it says on the big box.  Maybe I'll find something in the .config...

But I'm not, sr_mod and libata seem to have fallen into a black hole between 
FC5 and FC6.

Thanks Steve.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Always think of something new; this helps you forget your last rotten idea.
		-- Seth Frankel

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel