From owner-freebsd-current@FreeBSD.ORG Wed Sep 22 23:37:01 2004 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 D24FF16A4CE; Wed, 22 Sep 2004 23:37:01 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 810E043D2F; Wed, 22 Sep 2004 23:37:01 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-127-84-57.dsl.snfc21.pacbell.net [67.127.84.57]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i8MNauDl010578; Wed, 22 Sep 2004 16:36:57 -0700 Message-ID: <41520C80.3010007@root.org> Date: Wed, 22 Sep 2004 16:36:32 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <200409221620.SAA14914@marabu.marabu.ch> <20040922193406.GB18509@numeri.campus.luth.se> <4151DA08.6010602@root.org> <20040922.172120.29652264.imp@bsdimp.com> In-Reply-To: <20040922.172120.29652264.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: ast@marabu.ch cc: johan@freebsd.org Subject: Re: 5.3-BETA5 panics when inserting dc0 carbus card (only with ACPI enabled) enabled) 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: Wed, 22 Sep 2004 23:37:01 -0000 M. Warner Losh wrote: > In message: <4151DA08.6010602@root.org> > Nate Lawson writes: > : Um, what is the dc0 card doing mapping ports 0-0xff: > : > : Below the analogous output Johan Karlsson posted > : for his Xircom X3201 10/100BaseTX card for 5.3-BETA5: > : > : dc0: port 0-0xff mem 0x88000000-0x880003ff > : at device 0.0 on cardbus0 > : cbb alloc res fail > : dc0: couldn't map ports/memory > : > : Dmesg from boot with a working kernel for dc0 would help as well as > : devinfo -r from a non-working one. > > Is there a pci bridge involved? It is a well known problem for > cardbus systems that if there isn't, you get mappings like this. I don't know, but it looks like cbb0 is directly under pci0. Here's the devinfo -r results from his working boot: pcib0 pci0 pcib1 pci1 cbb0 Interrupt request lines: 0xb I/O memory addresses: 0x50000000-0x50000fff cardbus0 pccard0 cbb1 I/O memory addresses: 0x50100000-0x50100fff cardbus1 pccard1 I can't see how ACPI sysresources affect this since ACPI doesn't claim 0x1080-0x10ff IO which the card asks for. -- Nate