WD My Book 500G external drive: error -110

Discussion:

seandarcy

2008-01-06 03:28:25 UTC

I'm running Fedora 8:

uname -r
2.6.23.8-63.fc8

I connected my new Western Digital My Book 500G external drive to the
usb port.

syslog:

Jan 5 21:53:35 testbox kernel: usb 1-4: new high speed USB device using
ehci_hcd and address 2
Jan 5 21:53:50 testbox kernel: usb 1-4: device descriptor read/64,
error -110
Jan 5 21:54:05 testbox kernel: usb 1-4: device descriptor read/64,
error -110
Jan 5 21:54:05 testbox kernel: usb 1-4: new high speed USB device using
ehci_hcd and address 3
Jan 5 21:54:20 testbox kernel: usb 1-4: device descriptor read/64,
error -110
Jan 5 21:54:36 testbox kernel: usb 1-4: device descriptor read/64,
error -110
Jan 5 21:54:36 testbox kernel: usb 1-4: new high speed USB device using
ehci_hcd and address 4
Jan 5 21:54:41 testbox kernel: usb 1-4: device descriptor read/8, error
-110
.................

Any help apprecoated.

sean

-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Alan Stern

2008-01-06 04:06:55 UTC

Permalink

Post by seandarcy
uname -r
2.6.23.8-63.fc8
I connected my new Western Digital My Book 500G external drive to the
usb port.
Jan 5 21:53:35 testbox kernel: usb 1-4: new high speed USB device using
ehci_hcd and address 2
Jan 5 21:53:50 testbox kernel: usb 1-4: device descriptor read/64,
error -110
Jan 5 21:54:05 testbox kernel: usb 1-4: device descriptor read/64,
error -110
Jan 5 21:54:05 testbox kernel: usb 1-4: new high speed USB device using
ehci_hcd and address 3
Jan 5 21:54:20 testbox kernel: usb 1-4: device descriptor read/64,
error -110
Jan 5 21:54:36 testbox kernel: usb 1-4: device descriptor read/64,
error -110
Jan 5 21:54:36 testbox kernel: usb 1-4: new high speed USB device using
ehci_hcd and address 4
Jan 5 21:54:41 testbox kernel: usb 1-4: device descriptor read/8, error
-110
.................
Any help apprecoated.

It certainly looks like either the disk drive's USB interface or your
computer's USB controller isn't working.

You can try attaching the drive to a different computer or attaching
different high-speed USB devices to your computer. That should
indicate which component is at fault.

Alan Stern

-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

sean darcy

2008-01-06 22:00:08 UTC

Permalink

Post by Alan Stern

It's a dual boot desktop. XP sees the usb hard drive, and I can run the
WD extended diagnostics on the drive.
googling did show some other reports, e.g.
http://forum.freespire.org/archive/index.php/t-6479.html, but no solutions.

Any linux diagnostics that would be useful?

sean

-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Matthew Dharm

2008-01-06 22:20:38 UTC

Permalink

Post by sean darcy

Post by Alan Stern

Try rmmod'ing ehci_hcd.

Matt

--
Matthew Dharm Home: mdharm-***@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver

A: The most ironic oxymoron wins ...
DP: "Microsoft Works"
A: Uh, okay, you win.
-- A.J. & Dust Puppy
User Friendly, 1/18/1998

Matthew Dharm

2008-01-06 22:22:05 UTC

Permalink

This post might be inappropriate. Click to display it.

Alan Stern

2008-01-07 16:29:49 UTC

Permalink

Post by sean darcy

Post by Alan Stern

Like Matt said, it would help to see the complete system log starting
from the time you plugged in the drive. You could also get a usbmon
trace (see the instructions in the kernel source file
Documentation/usb/usbmon.txt).

Alan Stern

-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Sean Darcy

2008-01-08 23:56:03 UTC

rmmod'd and modprobe'd ehci_hcd, the pluged in the usb cable.

/var/log/messages:

Jan 8 18:19:44 testbox kernel: ehci_hcd 0000:00:1d.7: EHCI Host Controller
Jan 8 18:19:44 testbox kernel: ehci_hcd 0000:00:1d.7: new USB bus
registered, assigned bus number 1
Jan 8 18:19:44 testbox kernel: ehci_hcd 0000:00:1d.7: debug port 1
Jan 8 18:19:44 testbox kernel: ehci_hcd 0000:00:1d.7: irq 23, io mem
0x901c4400
Jan 8 18:19:44 testbox kernel: ehci_hcd 0000:00:1d.7: USB 2.0 started,
EHCI 1.00, driver 10 Dec 2004
Jan 8 18:19:44 testbox kernel: usb usb1: configuration #1 chosen from 1
choice
Jan 8 18:19:44 testbox kernel: hub 1-0:1.0: USB hub found
Jan 8 18:19:44 testbox kernel: hub 1-0:1.0: 8 ports detected
Jan 8 18:20:09 testbox kernel: usb 1-2: new high speed USB device using
ehci_hcd and address 2
Jan 8 18:20:24 testbox kernel: usb 1-2: device descriptor read/64,
error -110
Jan 8 18:20:39 testbox kernel: usb 1-2: device descriptor read/64,
error -110
Jan 8 18:20:39 testbox kernel: usb 1-2: new high speed USB device using
ehci_hcd and address 3
Jan 8 18:20:54 testbox kernel: usb 1-2: device descriptor read/64,
error -110
Jan 8 18:21:10 testbox kernel: usb 1-2: device descriptor read/64,
error -110
Jan 8 18:21:10 testbox kernel: usb 1-2: new high speed USB device using
ehci_hcd and address 4
Jan 8 18:21:15 testbox kernel: usb 1-2: device descriptor read/8, error
-110
Jan 8 18:21:20 testbox kernel: usb 1-2: device descriptor read/8, error
-110
Jan 8 18:21:20 testbox kernel: usb 1-2: new high speed USB device using
ehci_hcd and address 5
Jan 8 18:21:25 testbox kernel: usb 1-2: device descriptor read/8, error
-110
.........

Unplugged the cable, rmmod'd ehci_hcd and plugged the cable back in:

Jan 8 18:21:30 testbox kernel: usb 1-2: device descriptor read/8, error
-110
Jan 8 18:28:39 testbox kernel: ehci_hcd 0000:00:1d.7: remove, state 4
Jan 8 18:28:39 testbox kernel: usb usb1: USB disconnect, address 1
Jan 8 18:28:39 testbox kernel: ehci_hcd 0000:00:1d.7: USB bus 1
deregistered
Jan 8 18:28:39 testbox kernel: ACPI: PCI interrupt for device
0000:00:1d.7 disabled
Jan 8 18:29:01 testbox kernel: usb 2-2: new full speed USB device using
uhci_hcd and address 6
Jan 8 18:29:16 testbox kernel: usb 2-2: device descriptor read/64,
error -110
Jan 8 18:29:31 testbox kernel: usb 2-2: device descriptor read/64,
error -110
Jan 8 18:29:31 testbox kernel: usb 2-2: new full speed USB device using
uhci_hcd and address 7
Jan 8 18:29:46 testbox kernel: usb 2-2: device descriptor read/64,
error -110
Jan 8 18:30:02 testbox kernel: usb 2-2: device descriptor read/64,
error -110
Jan 8 18:30:02 testbox kernel: usb 2-2: new full speed USB device using
uhci_hcd and address 8
Jan 8 18:30:07 testbox kernel: usb 2-2: device descriptor read/8, error
-110
Jan 8 18:30:12 testbox kernel: usb 2-2: device descriptor read/8, error
-110
Jan 8 18:30:12 testbox kernel: usb 2-2: new full speed USB device using
uhci_hcd and address 9
Jan 8 18:30:17 testbox kernel: usb 2-2: device descriptor read/8, error
-110
Jan 8 18:30:22 testbox kernel: usb 2-2: device descriptor read/8, error
-110
Jan 8 18:31:47 testbox kernel: usb 2-2: new full speed USB device using
uhci_hcd and address 10
.................

Setting up usbmon was not a success:

[***@testbox 2.6.23.9-85.fc8-x86_64]# mount -t debugfs none_debugs
/sys/kernel/debug
[***@testbox 2.6.23.9-85.fc8-x86_64]# modprobe usbmon
FATAL: Module usbmon not found.

Maybe usbmon is compiled in for Fedora??

But I kept going:

ls /sys/kernel/debug/usbmon
0s 0u 2s 2t 2u 3s 3t 3u 4s 4t 4u 5s 5t 5u

cat /proc/bus/usb/devices

showed only the 4 host controllers.

But unplugged the cable, entered

cat /sys/kernel/debug/usbmon/2u > /tmp/1.mon.out

and plugged in the cable. head /tmp/1.mon.out:

head -20 /tmp/1.mon.out
ffff810037f38d80 3045534577 S Ii:2:001:1 -115:128 2 <
ffff81000fe64cc0 3045534596 S Ci:2:001:0 s a3 00 0000 0001 0004 4 <
ffff81000fe64cc0 3045534603 C Ci:2:001:0 0 4 = 00010000
ffff81000fe64cc0 3045534606 S Ci:2:001:0 s a3 00 0000 0002 0004 4 <
ffff81000fe64cc0 3045534612 C Ci:2:001:0 0 4 = 01010100
ffff81000fe64cc0 3045534614 S Co:2:001:0 s 23 01 0010 0002 0000 0
ffff81000fe64cc0 3045534618 C Co:2:001:0 0 0
ffff81000fe64cc0 3045534620 S Ci:2:001:0 s a3 00 0000 0002 0004 4 <
ffff81000fe64cc0 3045534626 C Ci:2:001:0 0 4 = 01010000
ffff81000fe64cc0 3045560573 S Ci:2:001:0 s a3 00 0000 0002 0004 4 <
ffff81000fe64cc0 3045560581 C Ci:2:001:0 0 4 = 01010000
ffff81000fe64cc0 3045586574 S Ci:2:001:0 s a3 00 0000 0002 0004 4 <
ffff81000fe64cc0 3045586581 C Ci:2:001:0 0 4 = 01010000
ffff81000fe64cc0 3045612576 S Ci:2:001:0 s a3 00 0000 0002 0004 4 <
ffff81000fe64cc0 3045612584 C Ci:2:001:0 0 4 = 01010000
ffff81000fe64cc0 3045638578 S Ci:2:001:0 s a3 00 0000 0002 0004 4 <
ffff81000fe64cc0 3045638587 C Ci:2:001:0 0 4 = 01010000
ffff81000fe64cc0 3045638597 S Co:2:001:0 s 23 03 0004 0002 0000 0
ffff81000fe64cc0 3045638603 C Co:2:001:0 0 0
ffff81000fe64cc0 3045689574 S Ci:2:001:0 s a3 00 0000 0002 0004 4 <

Thanks for all the time and attention.

sean

Pete Zaitcev

2008-01-09 05:21:43 UTC

Permalink

Post by Sean Darcy
head -20 /tmp/1.mon.out
ffff810037f38d80 3045534577 S Ii:2:001:1 -115:128 2 <
ffff81000fe64cc0 3045534596 S Ci:2:001:0 s a3 00 0000 0001 0004 4 <

20 lines is never sufficient with usbmon. It's more like 20 thousand.
But never mind that, I think the -110 you're getting is a clear
indication that interrupts are not routed for the device.

As such it has nothing to do with USB.

There are some command line options to work around such issues, like
pci=noacpi, pci=biosirq and so on. Please look it up in
Documentation/kernel-parameters.txt.

-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Matthew Dharm

2008-01-09 15:23:14 UTC

Permalink

Post by Pete Zaitcev

Post by Sean Darcy
head -20 /tmp/1.mon.out
ffff810037f38d80 3045534577 S Ii:2:001:1 -115:128 2 <
ffff81000fe64cc0 3045534596 S Ci:2:001:0 s a3 00 0000 0001 0004 4 <

I agree. The usb-storage driver isn't even getting bound to the device,
which is a different problem than was being reported in the URL Sean
provided. That URL showed a device enumerating at least somewhat
successfully and then failing during a SCSI reset.

Do other USB devices work on this machine?

Matt

--
Matthew Dharm Home: mdharm-***@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver

Would you mind not using our Web server? We're trying to have a game of
Quake here.
-- Greg
User Friendly, 5/11/1998

Sean Darcy

2008-01-10 19:16:48 UTC

Permalink

Post by Matthew Dharm

Post by Pete Zaitcev

Post by Sean Darcy
head -20 /tmp/1.mon.out
ffff810037f38d80 3045534577 S Ii:2:001:1 -115:128 2 <
ffff81000fe64cc0 3045534596 S Ci:2:001:0 s a3 00 0000 0001 0004 4 <

20 lines is never sufficient with usbmon. It's more like 20 thousand.

I attached the full file, head was just a courtesy to show the begining :)

Post by Matthew Dharm

Post by Pete Zaitcev
But never mind that, I think the -110 you're getting is a clear
indication that interrupts are not routed for the device.
As such it has nothing to do with USB.

Yes.

But it's all fixed - probably by sunspots.

I unplugged the MyBook and moved it over to a laptop. That worked under
Fedora. Then I took it back to the original desktop, and that worked!!

Jan 10 14:02:57 testbox kernel: usb 3-1: new full speed USB device using
uhci_hcd and address 2
Jan 10 14:03:10 testbox kernel: usb 3-1: new full speed USB device using
uhci_hcd and address 3
Jan 10 14:03:10 testbox kernel: usb 3-1: configuration #1 chosen from 1
choice
Jan 10 14:03:10 testbox kernel: Initializing USB Mass Storage driver...
Jan 10 14:03:10 testbox kernel: scsi6 : SCSI emulation for USB Mass
Storage devices
Jan 10 14:03:10 testbox kernel: usbcore: registered new interface driver
usb-storage
Jan 10 14:03:10 testbox kernel: USB Mass Storage support registered.
Jan 10 14:03:15 testbox kernel: scsi 6:0:0:0: Direct-Access WD
4000YS External 101a PQ: 0 ANSI: 4
..............

I think the key was unplugging the device. My bet is that when it's been
powered up for some period of time, it no longer makes whatever usb
noises it should make when the cable is connected.

So now it Works For Me. Note is always did work under Windows. Perhaps
there's some usb signal that restarts the handshake from a device like
this that goes to sleep?

In any event, thanks for all the attention and support.

sean

-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Alan Stern

2008-01-10 20:41:34 UTC

Permalink

Post by Sean Darcy
But it's all fixed - probably by sunspots.
I unplugged the MyBook and moved it over to a laptop. That worked under
Fedora. Then I took it back to the original desktop, and that worked!!
Jan 10 14:02:57 testbox kernel: usb 3-1: new full speed USB device using
uhci_hcd and address 2
Jan 10 14:03:10 testbox kernel: usb 3-1: new full speed USB device using
uhci_hcd and address 3
Jan 10 14:03:10 testbox kernel: usb 3-1: configuration #1 chosen from 1
choice
Jan 10 14:03:10 testbox kernel: Initializing USB Mass Storage driver...
Jan 10 14:03:10 testbox kernel: scsi6 : SCSI emulation for USB Mass
Storage devices
Jan 10 14:03:10 testbox kernel: usbcore: registered new interface driver
usb-storage
Jan 10 14:03:10 testbox kernel: USB Mass Storage support registered.
Jan 10 14:03:15 testbox kernel: scsi 6:0:0:0: Direct-Access WD
4000YS External 101a PQ: 0 ANSI: 4
..............
I think the key was unplugging the device. My bet is that when it's been
powered up for some period of time, it no longer makes whatever usb
noises it should make when the cable is connected.
So now it Works For Me. Note is always did work under Windows. Perhaps
there's some usb signal that restarts the handshake from a device like
this that goes to sleep?

I wouldn't be so quick to assume it's working right. Notice in the
messages above: "full speed". You don't want to operate a 500 GB drive
at full speed.

This doesn't explain why the drive failed to work at full speed in your
earlier test, though. Whatever the reason, you should verify that it
really does work at high speed.

Alan Stern

-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

sean darcy

2008-01-12 00:03:47 UTC

Permalink

Post by Alan Stern

I didn't have ehci_hcd loaded. Now it shows high speed:

............
Jan 11 18:53:22 testbox kernel: usb 1-3: new high speed USB device using
ehci_hcd and address 2
Jan 11 18:53:22 testbox kernel: usb 1-3: configuration #1 chosen from 1
choice
Jan 11 18:53:22 testbox kernel: scsi8 : SCSI emulation for USB Mass
Storage devices
Jan 11 18:53:27 testbox kernel: scsi 8:0:0:0: Direct-Access WD
4000YS External 101a PQ: 0 ANSI: 4
........

But how do you "verify" high speed? hdparm?

sean

-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Alan Stern

2008-01-12 03:07:09 UTC

Permalink

Post by seandarcy

Post by Alan Stern
I wouldn't be so quick to assume it's working right. Notice in the
messages above: "full speed". You don't want to operate a 500 GB drive
at full speed.
This doesn't explain why the drive failed to work at full speed in your
earlier test, though. Whatever the reason, you should verify that it
really does work at high speed.
Alan Stern

............
Jan 11 18:53:22 testbox kernel: usb 1-3: new high speed USB device using
ehci_hcd and address 2
Jan 11 18:53:22 testbox kernel: usb 1-3: configuration #1 chosen from 1
choice
Jan 11 18:53:22 testbox kernel: scsi8 : SCSI emulation for USB Mass
Storage devices
Jan 11 18:53:27 testbox kernel: scsi 8:0:0:0: Direct-Access WD
4000YS External 101a PQ: 0 ANSI: 4
........
But how do you "verify" high speed? hdparm?

You verify it by (1) making sure the log says "high speed" (which it
does; see above) and (2) checking that the drive really does work.

Alan Stern

-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html