From owner-freebsd-questions@FreeBSD.ORG Thu Mar 31 14:43:38 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F1A816A4F4 for ; Thu, 31 Mar 2005 14:43:38 +0000 (GMT) Received: from mail24.sea5.speakeasy.net (mail24.sea5.speakeasy.net [69.17.117.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C0C843D46 for ; Thu, 31 Mar 2005 14:43:38 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 563 invoked from network); 31 Mar 2005 14:43:37 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail24.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 31 Mar 2005 14:43:37 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 94AA630; Thu, 31 Mar 2005 09:43:36 -0500 (EST) Sender: lowell@be-well.ilk.org To: "James Nelson" References: <06EF07780A906F49B4D3AE1503AC5FA6A2D2C2@emag09.emaglink.com> From: Lowell Gilbert Date: 31 Mar 2005 09:43:36 -0500 In-Reply-To: <06EF07780A906F49B4D3AE1503AC5FA6A2D2C2@emag09.emaglink.com> Message-ID: <44fyyb510n.fsf@be-well.ilk.org> Lines: 15 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: System Panic (Trap 12) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 14:43:38 -0000 "James Nelson" writes: > I have posted this message to hackers but have not gotten a response. I think this is networking related, but I don't know how to solve it? Any ideas? > > I am getting numerous panics. It seems to be totally random with no bearing on load. This is a dual proc. AMD 2600, 2 GB Ram. > > > I have included the where results of three seperate core files. > > Please advise. Those aren't debugging kernels, are they? If they are, you're getting serious stack corruption. If not, you really need to follow the Handbook and FAQ instructions for kernel debugging, because those traces aren't showing much that's useful.