From owner-freebsd-current@FreeBSD.ORG Tue Aug 16 17:50:15 2005 Return-Path: X-Original-To: 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 CD00916A422; Tue, 16 Aug 2005 17:50:15 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B47E43D53; Tue, 16 Aug 2005 17:50:14 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from [10.50.40.201] (Not Verified[10.50.40.201]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Tue, 16 Aug 2005 14:05:12 -0400 From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 16 Aug 2005 13:48:08 -0400 User-Agent: KMail/1.8 References: <20050816124525.GA31411@flame.pc> <20050816.092235.16452975.imp@bsdimp.com> <20050816154750.GB93756@flame.pc> In-Reply-To: <20050816154750.GB93756@flame.pc> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508161348.09643.jhb@FreeBSD.org> Cc: Giorgos Keramidas , "M. Warner Losh" Subject: Re: if_dc panics with 3Com OfficeConnect 10/100B PCI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 17:50:16 -0000 On Tuesday 16 August 2005 11:47 am, Giorgos Keramidas wrote: > On 2005-08-16 09:22, "M. Warner Losh" wrote: > > In message: <20050816124525.GA31411@flame.pc> > > Giorgos Keramidas writes: > > : I've recently acquired a 3Com 3CSOHO100B-TX NIC, which seems to be supported > > : by the ``dc'' driver. The output of pciconf is: > > : > > : % none0@pci0:10:0: class=0x020000 card=0x930010b7 chip=0x930010b7 rev=0x31 hdr=0x00 > > : % vendor = '3COM Corp, Networking Division' > > : % device = '3C910 Integrated Fast Ethernet Controller (3CSOHO100B-TX Compatible)' > > : % class = network > > : % subclass = ethernet > > : > > : When I compile the ``dc'' driver into my kernel or load it as a module > > : though, a relatively recent CURRENT (updated yesterday, 14 Aug 2005) > > : panics after a port mapping failure. > > : > > : The same panic happens when the device is configured into the kernel or > > : when I kldload if_dc. Is anyone else using ``dc'' interfaces on CURRENT > > : and seeing similar problems? > > > > Trace? > > It's a bit tricky, since I have to either copy it manually from the > console or find out how I can boot the machine with the NIC in serial > console mode. > > Booting with 'dc' compiled into the kernel doens't quite work, since the > panic happens too early for dumpdev to be set. If there a way to set > dumpdev earlier than /etc/rc.conf (i.e. from the boot loader)? > > Using a module doesn't really help with obtaining a trace, because the > symbols of the module are printed as ??? in kgdb. > > I'll try to obtain a trace later tonight though. Thanks for the reply :) Compile in DDB and get a stack trace over the serial console using 't' in DDB instead of worrying about getting a dump. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org