Subject: Re: USB CF Reader causes: "uhub1: device problem, disabling port 1"
To: Tom Nakamura <imifumei@imap.cc>
From: Michael <macallan18@earthlink.net>
List: port-i386
Date: 04/24/2005 17:49:12
--Signature_Sun__24_Apr_2005_17_49_12_-0400_+0V2gaAEU3HqPSS3
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

> I'm running 2.0 on a D845GBV intel board. Regular USB mass storage
> devices seem to work just fine on it. I have a "mediagear"-brand USB CF
> reader that works fine on linux on the same hardware. But when I plug in
> the reader under netbsd2.0, i get:
> "uhub1: device problem, disabling port 1"
> and nothing else. At this point my other USB mass storage device ceases
> to work. I have no other USB devices attached to the machine. Whats
> going on?
No idea what's going on, but I'm getting similar errors with other devices =
( like one flash memory stick - works fine with Windows but nothing else. M=
acOS X ignores it, NetBSD complains so I guess the thing isn't really confo=
rming to USB mass storage specs )
USB 2.0 ( high speed ) devices are a different thing - the EHCI driver seem=
s to have issues with certain chipsets, it works fine with my iBook G4, but=
 not with this:
ehci0 at pci1 dev 0 function 3: Acer Labs M5239 USB 2.0 Host Controller (re=
v. 0x01)
ehci0: interrupting at irq 25
ehci0: EHCI version 1.0
ehci0: companion controllers, 2 ports each: ohci0 ohci1 ohci2
( that's a macppc box, hence the 'unnatural' IRQ :) )
Low- and full speed devices work fine ( well, besides this flash drive... )

Anyway, your device seems to be different since I can't find anything about=
 the card reader. Mine:
umass0 at uhub3 port 4 configuration 1 interface 0
umass0: Ltd Winter Ver1.3, rev 2.00/0.05, addr 2
umass0: using SCSI over Bulk-Only
usbd_setup_pipe: failed to start endpoint, IOERROR
umass0: could not open 129-in pipe (bulk)
works fine on a USB 1.1 port but not on an ehci.

So - do you have another NetBSD box with different USB hardware ( preferrab=
ly a non-Intel USB controller ) to test with? I'd suspect an issue with the=
 uhci driver...

have fun
Michael

--Signature_Sun__24_Apr_2005_17_49_12_-0400_+0V2gaAEU3HqPSS3
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)

iQEVAwUBQmwUWMpnzkX8Yg2nAQLIYgf9FQQzutabdLAddIF4FgkJt/Y++Imr5ZSo
ChmsXFDduYeIsxqsExG6zpGzVBBa5l4f0/DrvQGREJakT58vFl/bRyTeKmuP4dHu
mw24E+IUszlr0bfg8VYzqln94UtG4eC5uaDB49JohCjJ+q5TjedWb6Vue8cd8eaL
ttzuqruo7l3nby/lnl+kY2DLbUmj2FmKbPPEA0VubjvLVhcwzmdMjqLpQP4oZXDe
KuKO/Xmb/g5b589dQh7dl7rmHlfF+9w9/rXiz9TF/jHg2ToXYhnitn8lDDSTxby0
0vygZmho04FDQUtap32t7MJZ2Nmje7a5AFxUVNI3LT/Qzae/NEUZAA==
=Q9uC
-----END PGP SIGNATURE-----

--Signature_Sun__24_Apr_2005_17_49_12_-0400_+0V2gaAEU3HqPSS3--