From owner-freebsd-current@FreeBSD.ORG  Wed Nov 19 19:26:53 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from green.bikeshed.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1B34816A4CE; Wed, 19 Nov 2003 19:26:53 -0800 (PST)
Received: from green.bikeshed.org (green@localhost [127.0.0.1])
	by green.bikeshed.org (8.12.10/8.12.9) with ESMTP id hAK3Qq6V024655;
	Wed, 19 Nov 2003 22:26:52 -0500 (EST)
	(envelope-from green@green.bikeshed.org)
Received: from localhost (green@localhost)hAK3Qqvf024651;
	Wed, 19 Nov 2003 22:26:52 -0500 (EST)
Message-Id: <200311200326.hAK3Qqvf024651@green.bikeshed.org>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
To: Josef Karthauser <joe@FreeBSD.org>
In-Reply-To: Message from Josef Karthauser <joe@FreeBSD.org> 
	<20021117193722.GA35364@genius.tao.org.uk> 
From: "Brian F. Feldman" <green@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 19 Nov 2003 22:26:51 -0500
Sender: green@green.bikeshed.org
cc: current@FreeBSD.org
Subject: Re: kernel panic trying to utilize a da(4)/umass(4) device with
	ohci(4) 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2003 03:26:53 -0000

Josef Karthauser <joe@FreeBSD.org> wrote:
> On Sun, Nov 17, 2002 at 01:18:00PM -0500, Brian F. Feldman wrote:
> > 
> > > ohci_alloc_std_chain+0xf5 (calling a DMAADDR() function, I believe)
> > > ohci_device_bulk_start+0x0d
> > > ohci_device_bulk_transfer+0x27
> > > usbd_transfer+0xc0
> > > umass_setup_transfer+0x4f
> > > umass_bbb_state
> > > usb_transfer_complete
> > > ohci_softintr
> > > 
> > > Can anyone confirm if this is normal or I have an exceptional system?  I 
> > > have two completely unrelated OHCI-based controllers in my system and 
> > > neither works.
> > 
> > Anyone?  I kinda want to use my CF reader.
> > 
> 
> There are rumours that OHCI is borked in NetBSD too and this is a bug
> that we've inherited.  Me, I've not got an OHCI system to test just
> UHCI.
> 
> Did it used to work, and got broken, or has it never worked?

Jeez, it's been broken a year and it's almost 5.2-RELEASE now.  Does anyone 
have ANY leads on these problems?  I know precisely nothing about how my USB 
hardware is supposed to work, but this OHCI+EHCI stuff definitely doesn't, 
and it's really not uncommon at all.  Is it unbroken in NetBSD currently?

-- 
Brian Fundakowski Feldman                           \'[ FreeBSD ]''''''''''\
  <> green@FreeBSD.org                               \  The Power to Serve! \
 Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,,,,,\