From owner-freebsd-current@FreeBSD.ORG  Mon Dec 22 13:02:01 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 E41E516A4CE
	for <freebsd-current@freebsd.org>;
	Mon, 22 Dec 2003 13:02:01 -0800 (PST)
Received: from priv-edtnes04.telusplanet.net (outbound02.telus.net
	[199.185.220.221])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6C23A43D45
	for <freebsd-current@freebsd.org>;
	Mon, 22 Dec 2003 13:02:00 -0800 (PST)
	(envelope-from james@icionline.ca)
Received: from [192.168.19.4] (really [142.179.173.206])
	by priv-edtnes04.telusplanet.netESMTP
	<20031222210200.IPQP5353.priv-edtnes04.telusplanet.net@[192.168.19.4]>;
	Mon, 22 Dec 2003 14:02:00 -0700
From: James Earl <james@icionline.ca>
To: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20031222.112145.100424196.imp@bsdimp.com>
References: <20031222092127.GA2355@cactus.homeunix.org>
	<1072116630.576.4.camel@chero>
	<20031222.112145.100424196.imp@bsdimp.com>
Content-Type: text/plain
Message-Id: <1072126978.76846.6.camel@work.ici>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Mon, 22 Dec 2003 14:02:58 -0700
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
	<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: Mon, 22 Dec 2003 21:02:02 -0000

On Mon, 2003-12-22 at 11:21, M. Warner Losh wrote:
> In message: <1072116630.576.4.camel@chero>
>             James Earl <james@icionline.ca> 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?

Would you say my Aironet problems sound related to the resource
allocation bugs that you're fighting?

James