From owner-freebsd-stable Thu Jun 29 9: 7:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 81FC137BC14 for ; Thu, 29 Jun 2000 09:07:52 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e5TG7ne08925; Thu, 29 Jun 2000 09:07:49 -0700 (PDT) Date: Thu, 29 Jun 2000 09:07:49 -0700 From: Alfred Perlstein To: David Gilbert Cc: Freebsd-stable@FreeBSD.ORG Subject: Re: dc19 fructration. Message-ID: <20000629090749.J275@fw.wintelcom.net> References: <14683.24171.98558.24798@trooper.velocet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14683.24171.98558.24798@trooper.velocet.net>; from dgilbert@velocet.ca on Thu, Jun 29, 2000 at 10:34:19AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * David Gilbert [000629 07:37] wrote: > When I type 'ifconfig -a' or 'netstat -i' and I have 20 dc interfaces > (dc0 to dc19) ... what chunks of code are running in the kernel? > > Something is stack smashing, and my efforts at debugging are being > thwarted by the fact that whatever is going wrong is covering it's > tracks rather effectively. > > To update the people who havn't been following, ifconfig -a on a box > with 20 dc interfaces double-panics the machine. This is easily > repeatable. Using truss or gdb on ifconfig may help you find out which syscall is the culpret. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message