From owner-freebsd-usb@FreeBSD.ORG Mon Apr 21 18:29:59 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 91A3D106566C; Mon, 21 Apr 2008 18:29:59 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 577738FC12; Mon, 21 Apr 2008 18:29:59 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m3LISZFF032517; Mon, 21 Apr 2008 12:28:35 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 21 Apr 2008 12:29:38 -0600 (MDT) Message-Id: <20080421.122938.1943336925.imp@bsdimp.com> To: mainland@eecs.harvard.edu From: "M. Warner Losh" In-Reply-To: <20080421171305.GA19840@eecs.harvard.edu> References: <20080421171305.GA19840@eecs.harvard.edu> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: Mon, 21 Apr 2008 18:29:59 -0000 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