From owner-freebsd-current@FreeBSD.ORG Mon Dec 22 18:14:43 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B8EF16A4CE for ; Mon, 22 Dec 2003 18:14:43 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 412B543D58 for ; Mon, 22 Dec 2003 18:14:35 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id hBN2EQAS044015; Mon, 22 Dec 2003 19:14:29 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 22 Dec 2003 19:14:22 -0700 (MST) Message-Id: <20031222.191422.48530878.imp@bsdimp.com> To: james@icionline.ca From: "M. Warner Losh" In-Reply-To: <1072126978.76846.6.camel@work.ici> References: <1072116630.576.4.camel@chero> <20031222.112145.100424196.imp@bsdimp.com> <1072126978.76846.6.camel@work.ici> X-Mailer: Mew version 3.3 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-current@freebsd.org Subject: Re: Continued problems with Aironet device and 5.2-RC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Dec 2003 02:14:43 -0000 In message: <1072126978.76846.6.camel@work.ici> James Earl writes: : On Mon, 2003-12-22 at 11:21, M. Warner Losh wrote: : > In message: <1072116630.576.4.camel@chero> : > James Earl writes: : > : On Mon, 2003-12-22 at 02:30, M. Warner Losh wrote: : > : > In message: <20031222092127.GA2355@cactus.homeunix.org> : > : > jqdkf@army.com writes: : > : > : On Mon, Dec 22, 2003 at 01:20:14AM -0700, M. Warner Losh wrote: : > : > : > In message: <20031222053002.GA872@cactus.homeunix.org> : > : > : > jqdkf@army.com writes: : > : > : > : cbb0: Unsupported card type detected : > : > : > : > : > : > This is typically a symptom of the resource allocation bugs I've been : > : > : > fighting... : > : > : > : > : > : : > : > : So are you suggesting that I should adjust the resource by myself, like : > : > : irq numbers, for now? : > : > : > : > I have the unhelpful advice "make sure two devices aren't using the : > : > same address." You'll likely have to decode all the BARs to make sure : > : > that this is the case. : > : : > : So, would this be the reason why I haven't been able to get my an0 : > : device to appear on it's own in the vmstat -i output? It seems the : > : uhci2 device follows the an0 device to whatever irq I assign to it (an0) : > : in the bios setup. : > : > an0 will share interrupts with the CardBus bridge and whatever it : > shares with. : : Do you know if my fxp0 device would also share interrupts with the : cardbus bridge also? Yes. All cards always share the interrupts with the bridge. : Would you say my Aironet problems sound related to the resource : allocation bugs that you're fighting? Not sure. Warner