From owner-freebsd-current@FreeBSD.ORG Sun May 9 10:25:56 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 EACE316A4CE for ; Sun, 9 May 2004 10:25:56 -0700 (PDT) Received: from smtp30.hccnet.nl (smtp30.hccnet.nl [62.251.0.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id EED0D43D3F for ; Sun, 9 May 2004 10:25:55 -0700 (PDT) (envelope-from d.wylie@hccnet.nl) Received: from smp by smtp30.hccnet.nl via fia142-13-100.dsl.hccnet.nl [80.100.13.142] with ESMTP id i49HPkZR028696 (8.12.10/2.04); Sun, 9 May 2004 19:25:47 +0200 (MEST) From: "Dylan Wylie" To: "M. Warner Losh" , freebsd-current@freebsd.org, stu@ipng.org.uk Date: Sun, 09 May 2004 19:22:31 +0200 MIME-Version: 1.0 Message-ID: <409E84F7.20847.72D0C2E@localhost> Priority: normal In-reply-to: <20040509.080600.122620289.imp@bsdimp.com> References: <409E0D5A.19164.559D04D@localhost> X-mailer: Pegasus Mail for Windows (v4.11) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: Re: cardbus trouble 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: Sun, 09 May 2004 17:25:57 -0000 Yep, its 'a work'n :-) cbb0: Secondary bus is 0 cbb0: Secondary bus set to 2 subbus 3 ath0 cardbus card up and running. Thanks. Thanks, Stuart as well for you response. Let me know if I can do anything else. bye bye Dylan On 9 May 2004 at 8:06, M. Warner Losh wrote: > In message: <409E0D5A.19164.559D04D@localhost> > "Dylan Wylie" writes: > : Yes, it used to work perfectly. > > I was afraid that you were going to say that :-(. > > : The dmesg with both cardbus and cbb debuging enabled is included below. > : Again, it shows insertion of the cardbus card which fails, followed by the pccard > : card, which succeedes. > : I also don't remember any 'lazy allocation' with the working builds. > > The lazy allocation is fine, I'm pretty sure. Let's look at things in > more detail, and I think the debug shows where we go off the rails: > > : pcib0: port 0xcf8-0xcff on acpi0 > > host bridge. > > : pci0: on pcib0 > > pci bus 0. > > : agp0: mem 0xf8000000-0xfbffffff at device 0.0 on pci0 > : agp0: Reserved 0x4000000 bytes for rid 0x10 type 3 at 0xf8000000 > > agp0 at pci0.0.0. > > > : pcib1: at device 1.0 on pci0 > : pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.AGP_ - > : AE_NOT_FOUND > : pci1: on pcib1 > : pci1: at device 0.0 (no driver attached) > > VGA at pci1.0.0. > > : cbb0: at device 10.0 on pci0 > > cbb is at pci0.10.0. > > : cbb0: Secondary bus is 0 > : cbb0: Secondary bus set to 1 subbus 2 > > DANGER WILL ROBINSON. Secondary bus is now being set to 1. Before I > think we kludged it to 2 always, but I might be mistaken. However, > this is clearly the problem reguardless of what we used to do. > > : cardbus0: at device 0.0 (no driver attached) > > Hmmm, odd that it is now being probed just like the device at > pci1.0.0, don't you think? > > So, give the following patch a spin. Try 3 and 4 if this fails. > Clearly this is a bogus patch from a generic point of view, but it is > good for testing. > > Warner >