From owner-freebsd-usb@FreeBSD.ORG Mon May 28 20:23:06 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AFEFE16A400 for ; Mon, 28 May 2007 20:23:06 +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 700DD13C480 for ; Mon, 28 May 2007 20:23:06 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l4SKMTum019296; Mon, 28 May 2007 14:22:29 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 28 May 2007 14:22:46 -0600 (MDT) Message-Id: <20070528.142246.-169060603.imp@bsdimp.com> To: julian@elischer.org From: "M. Warner Losh" In-Reply-To: <465B2D8C.6050301@elischer.org> References: <000001c7a158$29592310$0202a8c0@artemis> <465B2D8C.6050301@elischer.org> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 28 May 2007 14:22:29 -0600 (MDT) Cc: freebsd-usb@freebsd.org Subject: Re: RE : UMASS pbm at startup 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, 28 May 2007 20:23:06 -0000 In message: <465B2D8C.6050301@elischer.org> Julian Elischer writes: : Alexandre DELAY wrote: : > But why does it work with an other motherboard and not with an other one? It : > is the same usb mass storage and the same system. Is it possible that it is : > due to IRQ interruptions? Maybe that the first motherboard doesn't have IRQ : > on USB port!? : > : : try a different USB port.. some motherboards do wierd things with some ports. That also suggests another workaround: Adding a 2.0 hub can paper over some problems too. Warner