From owner-freebsd-questions@FreeBSD.ORG Sat Mar 22 23:15:58 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 271C51065670 for ; Sat, 22 Mar 2008 23:15:58 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7F0D88FC12; Sat, 22 Mar 2008 23:15:57 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47E59330.3060508@FreeBSD.org> Date: Sun, 23 Mar 2008 00:16:00 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Frank Solensky References: <1206206674.5811.22.camel@frank-laptop> <47E54B16.2070405@FreeBSD.org> <1206214985.5737.2.camel@frank-laptop> In-Reply-To: <1206214985.5737.2.camel@frank-laptop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: "Fatal Trap 19" on initial install 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: Sat, 22 Mar 2008 23:15:58 -0000 Frank Solensky wrote: > On Sat, 2008-03-22 at 19:08 +0100, Kris Kennaway wrote: >> Frank Solensky wrote: >>> .. I believe the "RAM parity error" is a red herring: I haven't >>> had any problems running Linux or Vista on this machine and running >>> Memtest86+ overnight didn't turn up any problems. >>> >>> http://updraft3.jp.freebsd.org/cgi/query-pr.cgi?pr=i386/107564 appears >>> to be similar but unresolved. >>> ... >>> Any suggestions? Thanks in advance.. >> The other OSes may be recovering (with performance penalty) from your >> RAM errors due to additional code not present in FreeBSD. In my >> experience this error is not a red herring, it indicates a real problem >> with your memory. > > What form of memory testing does the install process use? Or is there > some way to get more specific info about where the failure is occuring? > It'll be easier for me to work with the manufacturer if I can give them > more info about the failure. No testing is done by the OS, these errors are being reported to it by the hardware as they occur. Your BIOS may keep a log of ECC errors it detects. Kris