From owner-freebsd-current@FreeBSD.ORG Tue Oct 5 15:33:00 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 E415616A4CE for ; Tue, 5 Oct 2004 15:33:00 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5045643D45 for ; Tue, 5 Oct 2004 15:33:00 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CErJD-0000rA-00 for ; Tue, 05 Oct 2004 17:32:59 +0200 Received: from mulder.f5.com ([205.229.151.150]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Oct 2004 17:32:58 +0200 Received: from atkin901 by mulder.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Oct 2004 17:32:58 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: othermark Date: Tue, 05 Oct 2004 08:32:55 -0700 Lines: 21 Message-ID: References: <200410041354.03058.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: mulder.f5.com User-Agent: KNode/0.8.0 Sender: news 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: Tue, 05 Oct 2004 15:33:01 -0000 John Baldwin wrote: > 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? hmm. I did just change the memory out not too long ago. I'll try to find some new dimms for it. Good point, thanks. -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired);