From owner-freebsd-hardware@FreeBSD.ORG  Wed Sep 22 16:43:14 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E5F1B16A4CF
	for <freebsd-hardware@freebsd.org>;
	Wed, 22 Sep 2004 16:43:14 +0000 (GMT)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CF15A43D1F
	for <freebsd-hardware@freebsd.org>;
	Wed, 22 Sep 2004 16:43:10 +0000 (GMT)	(envelope-from avg@icyb.net.ua)
Received: from [212.40.38.87] (oddity.topspin.kiev.ua [212.40.38.87])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA01576
	for <freebsd-hardware@freebsd.org>;
	Wed, 22 Sep 2004 19:43:09 +0300 (EEST)
	(envelope-from avg@icyb.net.ua)
Message-ID: <4151AB9C.5070301@icyb.net.ua>
Date: Wed, 22 Sep 2004 19:43:08 +0300
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040831)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-hardware@freebsd.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: nf7 and ehci
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Sep 2004 16:43:15 -0000


Has anybody had a successful experience with ehci and nf7 (or nforce2 in
general) on 5.2.1 or later ?
I compiled ehci into a kernel and everything was pretty fine (i.e
probing, attachment of devices) until I actually tried to copy a large
file from a compact flash card - cp froze, I couldn't kill it and the
following message started to run on console:

umass0: BBB reset failed, TIMEOUT
umass0: BBB bulk-in clear stall failed, TIMEOUT
umass0: BBB bulk-out clear stall failed, TIMEOUT
umass0: BBB reset failed, TIMEOUT
umass0: BBB bulk-in clear stall failed, TIMEOUT
umass0: BBB bulk-out clear stall failed, TIMEOUT
...


Here's ehci boot message:
Sep 20 20:23:46 oddity kernel: ehci0: <EHCI (generic) USB 2.0
controller> mem 0xee000000-0xee0000ff irq 11 at device 2.2 on pci0
Sep 20 20:23:46 oddity kernel: ehci_pci_attach: companion usb0
Sep 20 20:23:46 oddity kernel: ehci_pci_attach: companion usb1
Sep 20 20:23:46 oddity kernel: usb2: EHCI version 1.0
Sep 20 20:23:46 oddity kernel: usb2: <EHCI (generic) USB 2.0 controller>
on ehci0
Sep 20 20:23:46 oddity kernel: uhub2: (0x10de) EHCI root hub, class 9/0,
rev 2.00/1.00, addr 1

Here's EHCI device pciconf (without ehci driver):
none6@pci0:2:2: class=0x0c0320 card=0x1c02147b chip=0x006810de rev=0xa4
hdr=0x00
    vendor   = 'NVIDIA Corporation'
    device   = 'nForce MCP2 EHCI USB 2.0 Controller'
    class    = serial bus
    subclass = USB

Umass device I used is 6-in-1 TravelFlash from PQI, detected as:
Sep 20 21:11:09 oddity kernel: umass0: GENERIC Flash Reader, rev
2.00/1.19, addr 2
Sep 20 21:11:10 oddity kernel: GEOM: create disk da0 dp=0xc6d96c50
Sep 20 21:11:10 oddity kernel: da0 at umass-sim0 bus 0 target 0 lun 0
Sep 20 21:11:10 oddity kernel: da0: <Generic STORAGE DEVICE 0119>
Removable Direct Access SCSI-0 device
Sep 20 21:11:10 oddity kernel: da0: 1.000MB/s transfers
Sep 20 21:11:10 oddity kernel: da0: 245MB (501760 512 byte sectors: 64H
32S/T 245C)


-- 
Andriy Gapon