From owner-freebsd-current@FreeBSD.ORG Mon Nov 8 17:29:11 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 4B1B716A4CE for ; Mon, 8 Nov 2004 17:29:11 +0000 (GMT) Received: from moya.lambermont.dyndns.org (j226018.upc-j.chello.nl [24.132.226.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id B221443D2D for ; Mon, 8 Nov 2004 17:29:10 +0000 (GMT) (envelope-from hans@lambermont.dyndns.org) Received: from localhost (localhost [127.0.0.1]) by moya.lambermont.dyndns.org (Postfix) with ESMTP id 79DD636402; Sat, 6 Nov 2004 17:51:47 +0100 (CET) Received: from moya.lambermont.dyndns.org ([127.0.0.1])port 10024) with ESMTP id 21081-08; Sat, 6 Nov 2004 17:51:47 +0100 (CET) Received: by moya.lambermont.dyndns.org (Postfix, from userid 1001) id 1891A36401; Sat, 6 Nov 2004 17:51:47 +0100 (CET) Date: Sat, 6 Nov 2004 17:51:47 +0100 To: Gabor MICSKO Message-ID: <20041106165147.GF79763@moya.lambermont.dyndns.org> References: <1099672914.7059.13.camel@alderaan.trey.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1099672914.7059.13.camel@alderaan.trey.hu> User-Agent: Mutt/1.4.2.1i From: hans@lambermont.dyndns.org (Hans Lambermont) X-Virus-Scanned: by amavisd-new-20030616.p5 at lambermont.dyndns.org cc: freebsd-current@freebsd.org Subject: Re: 5.3-RC2: 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, 08 Nov 2004 17:29:11 -0000 Gabor MICSKO wrote: > I've tried to install FreeBSD 5.3-RC2, FreeBSD 5.3-RC*, FreeBSD > 5.2.1-RELEASE, FreeBSD 5.2-RELEASE on my amd64 based laptop, but at > boot kernel is paniced. Just to be clear about the obvious: > NMI ISA a1, EISA ff > RAM parity error, likely hardware failure. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I'm not surprised you get a kernel panic with this system. Your RAM has faults. Unless you're absolutely sure this is not the case and the NMI complaint is bogus (I see you've tested with various other OSes, and even then it might be true) I suggest swapping RAM and trying again. regards, Hans Lambermont -- http://lambermont.webhop.org/ () ASCII-ribbon campaign against vCards, /\ HTML-mail and proprietary formats.