From owner-freebsd-questions@FreeBSD.ORG Wed Nov 9 00:55:44 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 E856A16A41F for ; Wed, 9 Nov 2005 00:55:44 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from S3.cableone.net (s3.cableone.net [24.116.0.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B12343D46 for ; Wed, 9 Nov 2005 00:55:44 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.vulpes (unverified [24.119.122.41]) by S3.cableone.net (CableOne SMTP Service S3) with ESMTP id 36552665 for multiple; Tue, 08 Nov 2005 18:07:26 -0700 Date: Tue, 8 Nov 2005 19:01:26 -0600 From: Vulpes Velox To: Roland Smith Message-ID: <20051108190126.424fc6d6@vixen42.vulpes> In-Reply-To: <20051025135801.GA66887@slackbox.xs4all.nl> References: <20051025135801.GA66887@slackbox.xs4all.nl> X-Mailer: Sylpheed-Claws 1.9.15 (GTK+ 2.6.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-NotAscii: charset=us-ascii X-IP-stats: Incoming Last 1, First 174, in=306, out=0, spam=0 X-External-IP: 24.119.122.41 X-Abuse-Info: Send abuse complaints to abuse@cableone.net Cc: Jayesh Jayan , freebsd-questions@freebsd.org Subject: Re: Installation problem with Freebsd 5.4 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2005 00:55:45 -0000 On Tue, 25 Oct 2005 15:58:01 +0200 Roland Smith wrote: > On Tue, Oct 25, 2005 at 07:09:05PM +0530, Jayesh Jayan wrote: > > an update to the issue. > > > > the error what i get is > > > > panic : page fault > > Cannnot Dump. No dump device defined. > > Automatic reboot in 15 seconds - press a key on the console to > > abort > > Without knowing which program produces the fault, it's hard to > diagnose the problem. > > One thing you could try is to burn a 6.0-RC1 CD and try that. Test > your memory with memtest86 (http://www.memtest86.com/). Memtest86 does not tell you if you have bad ram. It just indicates that something some where is wrong with that system there. I've seen it hit errors with bad motherboards as well.