From owner-freebsd-usb@FreeBSD.ORG Tue Apr 22 21:52:30 2008 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B53511065673; Tue, 22 Apr 2008 21:52:30 +0000 (UTC) (envelope-from mainland@eecs.harvard.edu) Received: from mail.eecs.harvard.edu (bowser.eecs.harvard.edu [140.247.60.24]) by mx1.freebsd.org (Postfix) with ESMTP id 9BFC68FC19; Tue, 22 Apr 2008 21:52:30 +0000 (UTC) (envelope-from mainland@eecs.harvard.edu) Received: by mail.eecs.harvard.edu (Postfix, from userid 33141) id 43B6B1A5FD6; Tue, 22 Apr 2008 17:52:27 -0400 (EDT) Date: Tue, 22 Apr 2008 17:52:27 -0400 From: Geoffrey Mainland To: "M. Warner Losh" Message-ID: <20080422215227.GA79245@eecs.harvard.edu> References: <20080421171305.GA19840@eecs.harvard.edu> <20080421.122938.1943336925.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080421.122938.1943336925.imp@bsdimp.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-embedded@freebsd.org, freebsd-usb@freebsd.org Subject: Re: Soekris 4826 USB failure on FreeBSD 7.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2008 21:52:30 -0000 Wow, this turns out to be much worse than I thought...I've tracked down the problem to the commit of the new physical memory allocator at Sat Jun 16 04:57:05 2007 UTC. Before that, no kern/122380; after that, kern/122380 applies. Any ideas where to go from here? Thanks, Geoff On Mon, Apr 21, 2008 at 12:29:38PM -0600, M. Warner Losh wrote: > In message: <20080421171305.GA19840@eecs.harvard.edu> > Geoffrey Mainland writes: > : I have a number of Soekris 4826 boards with USB thumb drives attached > : that happily run FreeBSD 6.0. However, when I try to get them to run > : FreeBSD 7, the thumb drives stop working. A PR was recently filed by > : someone with a similar issue: kern/122380 (I see the same failure as in > : the PR). Looks like something changed in the USB stack from 6 to 7...any > : ideas where to look or how I can go about solving this? > > Lots of cosmetic changes, lots of other changes that were for the > better, lots and lots of quirks. I'm guessing something got quirked, > or there was a bug fix that caused us to die. > > As to tracking it down, I'd suggest a binary search between > 7.0-release and where RELENG_6 was branched. Not ideal, but that's > the likeliest way to cope. > > Warner