From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 20:28:39 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 62DA716A4CE for ; Mon, 4 Oct 2004 20:28:39 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B4C943D48 for ; Mon, 4 Oct 2004 20:28:39 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 16207 invoked from network); 4 Oct 2004 20:28:38 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 4 Oct 2004 20:28:38 -0000 Received: from [10.50.40.210] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i94KSU5m058953; Mon, 4 Oct 2004 16:28:35 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 4 Oct 2004 13:54:03 -0400 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200410041354.03058.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: othermark Subject: Re: 48hr panics: Fatal trap 19: non-maskable interrupt trap while in kernel mode 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: Mon, 04 Oct 2004 20:28:39 -0000 On Monday 04 October 2004 11:21 am, othermark wrote: > I get these about once every 48hrs for about 2 weeks on a box I build > -current once or twice a week. > > First panic here is from Wednesday, the panic at the end of this message > is from Friday morning's -current. Is there any problem currently > with dumpdev=auto and savecore? Note the silly lockheld panic when I call > doadump. I'm guessing you are getting an NMI due to an ECC error while it is zero'ing memory. Perhaps your memory is going bad or your box is overheating? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org