Subject: Re: NVIDIA ehci(4) USB problem
To: Izumi Tsutsui <firstname.lastname@example.org>
From: None <email@example.com>
Date: 12/26/2007 15:25:46
Content-Type: text/plain; charset=us-ascii
On Thu, Jun 21, 2007 at 11:26:22PM +0900, Izumi Tsutsui wrote:
> Does anyone use umass(4) devices on ehci(4) of NVIDIA chipset
> on -current?
I'd like to.
> I'm using ASRock AM2NF3-VSTA board which has NVIDIA nForce3 250
> chipset and its ehci is attached as the following:
> ehci0 at pci0 dev 2 function 2: NVIDIA nForce3 250 USB2 Host Controller (=
> LUS2: Picked IRQ 22 with weight 0
> ehci0: interrupting at ioapic0 pin 22 (irq 3)
> ehci0: BIOS has given up ownership
> ehci0: EHCI version 1.0
> ehci0: companion controllers, 4 ports each: ohci0 ohci1
> usb2 at ehci0: USB revision 2.0
> uhub2 at usb2
> uhub2: NVIDIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
> uhub2: 8 ports with 8 removable, self powered
> When I plug a USB flash memory to USB port, the device is properly
> attached and I can mount it. But after some file read/write accesses
> it just hangs in syscall and put the following errors:
> umass0 at uhub2 port 3 configuration 1 interface 0
> umass0: BUFFALO USB Flash Disk, rev 2.00/1.00, addr 2
> usb_transfer_complete: xfer=3D0xc2cbdd00 not busy 0x00000046
> uvm_fault(0xc06a7f40, 0, 1) -> 0xe
> The same device connected via a USB 1.1 hub (and NVIDIA's ohci(4))
> works fine. Also it works on NEC's ehci and VIA's ehci.
Yup, same. I see this on an ECS NFORCE3-A (nforce3 250) board
as well as a MSI MS-7135 (nforce4 4x).
FWIW, hard disk-based umass(4) devices do not present the same
issues, just the USB flash drives.
These boxes are both running NetBSD/amd64 -current.
> Should I send-pr about this?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
-----END PGP SIGNATURE-----