From owner-freebsd-current@FreeBSD.ORG Sat Apr 10 13:24:06 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 8F77516A4CE for ; Sat, 10 Apr 2004 13:24:06 -0700 (PDT) Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D13643D2D for ; Sat, 10 Apr 2004 13:24:06 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.124]) by mta02-svc.ntlworld.comESMTP <20040410202317.UHVM3246.mta02-svc.ntlworld.com@llama.fishballoon.org>; Sat, 10 Apr 2004 21:23:17 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.30; FreeBSD) id 1BCP1J-00079y-1d; Sat, 10 Apr 2004 21:24:05 +0100 Date: Sat, 10 Apr 2004 21:24:05 +0100 From: Scott Mitchell To: Pete Carss Message-ID: <20040410202404.GB25661@llama.fishballoon.org> References: <4078026A.9070907@mac.com> <20040410162928.GA25661@llama.fishballoon.org> <4078277F.7050401@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4078277F.7050401@mac.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.9-RELEASE-p4 i386 Sender: Scott Mitchell cc: freebsd-current@freebsd.org Subject: Re: Cisco driver stopped working with -current 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: Sat, 10 Apr 2004 20:24:06 -0000 On Sat, Apr 10, 2004 at 05:57:35PM +0100, Pete Carss wrote: > Scott Mitchell wrote: > >On Sat, Apr 10, 2004 at 03:19:22PM +0100, Pete Carss wrote: > > > >Can you boot with hw.pccard.debug=1 and hw.pccard.cis_debug=1 (you'll need > >to break into the loader at boot time and set them there) and send me the > >resulting output (should end up in /var/run/dmesg.boot)? > > I think I've done what you asked....at the kernel prompt I "set" the > hw... values....here's the result: Hi Pete, That was exactly what I asked for, but not exactly what I wanted to see... Could you try booting again without the Aironet card plugged in, then: # sysctl hw.xe.debug=2 and plug in the Aironet? You should get a lot of new debug output from the xe driver that will hopefully tell us why it thinks it owns this card. Apologies for not asking for everything the first time around. Cheers, Scott -- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" scott at fishballoon.org | 0xAA775B8B | -- Anon