* Re: Weird USB errors on HD
[not found] ` <4s66H-2ai-19@gated-at.bofh.it>
@ 2005-07-27 2:34 ` Robert Hancock
2005-07-27 3:31 ` Grant Coady
0 siblings, 1 reply; 10+ messages in thread
From: Robert Hancock @ 2005-07-27 2:34 UTC (permalink / raw)
To: linux-kernel
Karim Yaghmour wrote:
> That being said, shouldn't there be a way for the kernel to refuse to
> use this hd if it's not getting enough power. I don't know enough about
> USB to say, but isn't there something more elegant that could be done in
> software?
Not really.. It seems like pretty much a matter of the controller saying
it can supply so much power, the drive says it uses so much power, but
one of them is lying and the drive ends up tripping the overcurrent.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Weird USB errors on HD
2005-07-27 2:34 ` Weird USB errors on HD Robert Hancock
@ 2005-07-27 3:31 ` Grant Coady
0 siblings, 0 replies; 10+ messages in thread
From: Grant Coady @ 2005-07-27 3:31 UTC (permalink / raw)
To: Robert Hancock; +Cc: linux-kernel
On Tue, 26 Jul 2005 20:34:10 -0600, Robert Hancock <hancockr@shaw.ca> wrote:
>Karim Yaghmour wrote:
>> That being said, shouldn't there be a way for the kernel to refuse to
>> use this hd if it's not getting enough power. I don't know enough about
>> USB to say, but isn't there something more elegant that could be done in
>> software?
>
>Not really.. It seems like pretty much a matter of the controller saying
> it can supply so much power, the drive says it uses so much power, but
>one of them is lying and the drive ends up tripping the overcurrent.
The drive itself may shutdown until power cycled. I sorted this issue
some months ago with a 2.5" 6GB drive in USB enclosure and the fix was
hardware, adding bypass capacitors to supply peak HDD current. Software
cannot fix that. No dataloss, just apparent lockup from OS point of view.
Drive fails to work on one laptop with a single USB port, but asking for
700mA from a 500mA USB port is too much, needs external 5V instead.
Grant.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Weird USB errors on HD
@ 2005-07-19 16:47 Karim Yaghmour
2005-07-19 19:29 ` Greg KH
2005-07-20 14:53 ` Alistair John Strachan
0 siblings, 2 replies; 10+ messages in thread
From: Karim Yaghmour @ 2005-07-19 16:47 UTC (permalink / raw)
To: linux-kernel
I have a usb-attached HD that I use from time to time. When it's connected
to my desktop through a hub it works flawlessly. When connected to my Dell
D600 Laptop, however, it sometimes randomly exhibits a loud click (as if the
heads went berzerk) and the device goes unrecognized (i.e. the USB layer drops
the device and then redetects it again; meanwhile there is FS corruption.)
The same behavior happens with 2.4.x and 2.6.x
In /var/log/messages I see something like:
hub 3-0:1.0: over-current change on port 1
hub 1-0:1.0: over-current change on port 3
...
usb 1-3: USB disconnect, address 2
usb 1-3: new high speed USB device using ehci_hcd and address 3
...
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
This doesn't seem too good.
Here's the complete passage from /var/log/messages:
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 384296
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 384296
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 384296
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 384296
EXT3-fs error (device sda): ext3_free_branches: Read failure, inode=1046532, block=48037
Aborting journal on device sda.
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 4176
printk: 813 messages suppressed.
Buffer I/O error on device sda, logical block 522
lost page write due to I/O error on sda
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT3-fs error (device sda) in ext3_reserve_inode_write: Journal has aborted
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT3-fs error (device sda) in ext3_reserve_inode_write: Journal has aborted
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT3-fs error (device sda) in ext3_orphan_del: Journal has aborted
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT3-fs error (device sda) in ext3_truncate: Journal has aborted
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
ext3_abort called.
EXT3-fs error (device sda): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 3254080
hub 3-0:1.0: over-current change on port 1
hub 1-0:1.0: over-current change on port 3
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 3254088
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 3254096
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 3254104
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 3254088
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 3254088
usb 1-3: USB disconnect, address 2
scsi0 (0:0): rejecting I/O to device being removed
Buffer I/O error on device sda, logical block 458754
lost page write due to I/O error on sda
scsi0 (0:0): rejecting I/O to device being removed
Buffer I/O error on device sda, logical block 517070
lost page write due to I/O error on sda
scsi0 (0:0): rejecting I/O to device being removed
Buffer I/O error on device sda, logical block 1
lost page write due to I/O error on sda
scsi0 (0:0): rejecting I/O to device being removed
Buffer I/O error on device sda, logical block 393218
lost page write due to I/O error on sda
scsi0 (0:0): rejecting I/O to device being removed
scsi0 (0:0): rejecting I/O to device being removed
scsi0 (0:0): rejecting I/O to device being removed
scsi0 (0:0): rejecting I/O to device being removed
scsi0 (0:0): rejecting I/O to device being removed
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
usb 1-3: new high speed USB device using ehci_hcd and address 3
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #196225 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #196225 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #277985 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #1046529 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #228929 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #196225 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #212577 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #212577 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #196225 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #163521 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #163521 offset 0
Vendor: FUJITSU Model: MHT2040AT Rev: 0022
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdb: 78140160 512-byte hdwr sectors (40008 MB)
sdb: assuming drive cache: write through
SCSI device sdb: 78140160 512-byte hdwr sectors (40008 MB)
sdb: assuming drive cache: write through
sdb: unknown partition table
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
usb-storage: device scan complete
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #163521 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_find_entry: reading directory #163521 offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_readdir: directory #2 contains a hole at offset 0
scsi0 (0:0): rejecting I/O to dead device
EXT3-fs error (device sda): ext3_readdir: directory #2 contains a hole at offset 0
scsi0 (0:0): rejecting I/O to dead device
printk: 5 messages suppressed.
Buffer I/O error on device sda, logical block 522
lost page write due to I/O error on sda
usb 1-3: USB disconnect, address 3
usb 1-3: new high speed USB device using ehci_hcd and address 4
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
Vendor: FUJITSU Model: MHT2040AT Rev: 0022
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sda: 78140160 512-byte hdwr sectors (40008 MB)
sda: assuming drive cache: write through
SCSI device sda: 78140160 512-byte hdwr sectors (40008 MB)
sda: assuming drive cache: write through
sda: unknown partition table
Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
usb-storage: device scan complete
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
usb 1-3: USB disconnect, address 4
Any chances someone has seen this before or if there's something I can do
to stop this from happening anymore?
Thanks,
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Weird USB errors on HD
2005-07-19 16:47 Karim Yaghmour
@ 2005-07-19 19:29 ` Greg KH
2005-07-19 19:27 ` Karim Yaghmour
2005-07-19 20:16 ` Lee Revell
2005-07-20 14:53 ` Alistair John Strachan
1 sibling, 2 replies; 10+ messages in thread
From: Greg KH @ 2005-07-19 19:29 UTC (permalink / raw)
To: Karim Yaghmour; +Cc: linux-kernel
On Tue, Jul 19, 2005 at 12:47:32PM -0400, Karim Yaghmour wrote:
>
> I have a usb-attached HD that I use from time to time. When it's connected
> to my desktop through a hub it works flawlessly. When connected to my Dell
> D600 Laptop, however, it sometimes randomly exhibits a loud click (as if the
> heads went berzerk) and the device goes unrecognized (i.e. the USB layer drops
> the device and then redetects it again; meanwhile there is FS corruption.)
>
> The same behavior happens with 2.4.x and 2.6.x
>
> In /var/log/messages I see something like:
> hub 3-0:1.0: over-current change on port 1
> hub 1-0:1.0: over-current change on port 3
> ...
> usb 1-3: USB disconnect, address 2
> usb 1-3: new high speed USB device using ehci_hcd and address 3
Ugh, you have a bad device or power supply, or aren't giving it enough
power to drive the thing. Nothing we can do in Linux for that, sorry.
Buy a wall-powered usb hub, that usually helps.
Good luck,
greg k-h
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Weird USB errors on HD
2005-07-19 19:29 ` Greg KH
@ 2005-07-19 19:27 ` Karim Yaghmour
2005-07-19 19:40 ` Greg KH
2005-07-19 20:16 ` Lee Revell
1 sibling, 1 reply; 10+ messages in thread
From: Karim Yaghmour @ 2005-07-19 19:27 UTC (permalink / raw)
To: Greg KH; +Cc: linux-kernel
Greg KH wrote:
> Ugh, you have a bad device or power supply, or aren't giving it enough
> power to drive the thing. Nothing we can do in Linux for that, sorry.
> Buy a wall-powered usb hub, that usually helps.
I have one. I naively thought I could just plug the drive directly to the
laptop without using the wall-powered hub. I'll try that instead. Thanks.
That being said, shouldn't there be a way for the kernel to refuse to
use this hd if it's not getting enough power. I don't know enough about
USB to say, but isn't there something more elegant that could be done in
software?
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Weird USB errors on HD
2005-07-19 19:27 ` Karim Yaghmour
@ 2005-07-19 19:40 ` Greg KH
0 siblings, 0 replies; 10+ messages in thread
From: Greg KH @ 2005-07-19 19:40 UTC (permalink / raw)
To: Karim Yaghmour; +Cc: linux-kernel
On Tue, Jul 19, 2005 at 03:27:18PM -0400, Karim Yaghmour wrote:
>
> That being said, shouldn't there be a way for the kernel to refuse to
> use this hd if it's not getting enough power. I don't know enough about
> USB to say, but isn't there something more elegant that could be done in
> software?
Nope, it's a hardware/electrical issue :)
thanks,
greg k-h
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Weird USB errors on HD
2005-07-19 19:29 ` Greg KH
2005-07-19 19:27 ` Karim Yaghmour
@ 2005-07-19 20:16 ` Lee Revell
2005-07-19 20:29 ` Greg KH
1 sibling, 1 reply; 10+ messages in thread
From: Lee Revell @ 2005-07-19 20:16 UTC (permalink / raw)
To: Greg KH; +Cc: Karim Yaghmour, linux-kernel
On Tue, 2005-07-19 at 15:29 -0400, Greg KH wrote:
> Ugh, you have a bad device or power supply, or aren't giving it enough
> power to drive the thing. Nothing we can do in Linux for that, sorry.
> Buy a wall-powered usb hub, that usually helps.
>
I get the same messages on boot from a bus with no devices connected to
it (hub 4). I have not connected the motherboard header because I don't
use that bus, could this be related?
PCI0 USB0 USB1 USB2 USB3 USB4 USB5 USB6 LAN0 AC97 MC97
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.2
uhci_hcd 0000:00:10.0: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:10.0: irq 11, io base 0x0000d400
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
uhci_hcd 0000:00:10.1: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2)
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.1: irq 10, io base 0x0000d800
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci_hcd 0000:00:10.2: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#3)
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.2: irq 12, io base 0x0000dc00
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ehci_hcd 0000:00:10.3: VIA Technologies, Inc. USB 2.0
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
ehci_hcd 0000:00:10.3: irq 14, io mem 0xea004000
ehci_hcd 0000:00:10.3: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 6 ports detected
hub 4-0:1.0: over-current change on port 5
hub 4-0:1.0: over-current change on port 6
usb 2-2: new low speed USB device using uhci_hcd and address 2
input: USB HID v1.00 Mouse [Microsoft Microsoft Trackball Optical®] on usb-0000:00:10.1-2
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
Lee
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Weird USB errors on HD
2005-07-19 20:16 ` Lee Revell
@ 2005-07-19 20:29 ` Greg KH
0 siblings, 0 replies; 10+ messages in thread
From: Greg KH @ 2005-07-19 20:29 UTC (permalink / raw)
To: Lee Revell; +Cc: Karim Yaghmour, linux-kernel
On Tue, Jul 19, 2005 at 04:16:55PM -0400, Lee Revell wrote:
> On Tue, 2005-07-19 at 15:29 -0400, Greg KH wrote:
> > Ugh, you have a bad device or power supply, or aren't giving it enough
> > power to drive the thing. Nothing we can do in Linux for that, sorry.
> > Buy a wall-powered usb hub, that usually helps.
> >
>
> I get the same messages on boot from a bus with no devices connected to
> it (hub 4). I have not connected the motherboard header because I don't
> use that bus, could this be related?
Yes, it's probably just not grounded properly because the header is not
connected. It's harmless and you can just ignore it.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Weird USB errors on HD
2005-07-19 16:47 Karim Yaghmour
2005-07-19 19:29 ` Greg KH
@ 2005-07-20 14:53 ` Alistair John Strachan
2005-07-26 2:16 ` Karim Yaghmour
1 sibling, 1 reply; 10+ messages in thread
From: Alistair John Strachan @ 2005-07-20 14:53 UTC (permalink / raw)
To: karim; +Cc: linux-kernel
On Tuesday 19 Jul 2005 17:47, Karim Yaghmour wrote:
> I have a usb-attached HD that I use from time to time. When it's connected
> to my desktop through a hub it works flawlessly. When connected to my Dell
> D600 Laptop, however, it sometimes randomly exhibits a loud click (as if
> the heads went berzerk) and the device goes unrecognized (i.e. the USB
> layer drops the device and then redetects it again; meanwhile there is FS
> corruption.)
I've noticed my laptop is less able to output the required current for my
portable HD than my desktop; either way it's probably not a good idea
exceeding the USB specifications for current output @ 5V, so I'd recommend
you use a powered hub or external PSU (if the HD supports one).
Also a (slightly) nasty but functional trick is to have the power in when the
HD initially spins up, then remove the power. Once the drive has spun up it
seems to use a lot less power.
You can get special USB cables that link two USB ports' 5Vs together in
parallel, which seems to help supply the necessary current; after the HD has
spun up you can remove the second "dummy" USB connector (my laptop only has
two USB ports and I require the second port).
--
Cheers,
Alistair.
personal: alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student: CS/CSim Undergraduate
contact: 1F2 55 South Clerk Street,
Edinburgh. EH8 9PP.
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Weird USB errors on HD
2005-07-20 14:53 ` Alistair John Strachan
@ 2005-07-26 2:16 ` Karim Yaghmour
0 siblings, 0 replies; 10+ messages in thread
From: Karim Yaghmour @ 2005-07-26 2:16 UTC (permalink / raw)
To: Alistair John Strachan; +Cc: linux-kernel
Alistair John Strachan wrote:
> You can get special USB cables that link two USB ports' 5Vs together in
> parallel, which seems to help supply the necessary current; after the HD has
> spun up you can remove the second "dummy" USB connector (my laptop only has
> two USB ports and I require the second port).
Yeah, there was one of these in the box with the drive, but the first time
I saw it I remember thinking: what the hell is this thing? Then when I
figured it out, I found myself wondering whether the USB interface was
ever planed for such a such and whether it wouldn't have been better to
just ship a real adapter with the thing ...
Anyhow, I will not be using the drive anymore without a powered hub.
Thanks for all those that helped,
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2005-07-27 3:31 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <4s3BX-8X-7@gated-at.bofh.it>
[not found] ` <4s66H-2ai-21@gated-at.bofh.it>
[not found] ` <4s66H-2ai-19@gated-at.bofh.it>
2005-07-27 2:34 ` Weird USB errors on HD Robert Hancock
2005-07-27 3:31 ` Grant Coady
2005-07-19 16:47 Karim Yaghmour
2005-07-19 19:29 ` Greg KH
2005-07-19 19:27 ` Karim Yaghmour
2005-07-19 19:40 ` Greg KH
2005-07-19 20:16 ` Lee Revell
2005-07-19 20:29 ` Greg KH
2005-07-20 14:53 ` Alistair John Strachan
2005-07-26 2:16 ` Karim Yaghmour
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox