From owner-freebsd-questions@FreeBSD.ORG Mon Jan 19 09:52:21 2004 Return-Path: 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 62F5E16A4CE for ; Mon, 19 Jan 2004 09:52:21 -0800 (PST) Received: from smtp-out1.blueyonder.co.uk (smtp-out1.blueyonder.co.uk [195.188.213.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 693F243D46 for ; Mon, 19 Jan 2004 09:52:18 -0800 (PST) (envelope-from xfb52@dial.pipex.com) Received: from dial.pipex.com ([82.41.37.129]) by smtp-out1.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.5600); Mon, 19 Jan 2004 17:52:37 +0000 Message-ID: <400C1950.1000100@dial.pipex.com> Date: Mon, 19 Jan 2004 17:52:16 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20040105 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Daren Desjardins References: <1074525245.8385.5.camel@lithium.pythonvideo.com> In-Reply-To: <1074525245.8385.5.camel@lithium.pythonvideo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Jan 2004 17:52:37.0634 (UTC) FILETIME=[06851E20:01C3DEB5] cc: freebsd-questions@freebsd.org Subject: Re: Fatal trap 12 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2004 17:52:21 -0000 Daren Desjardins wrote: > Over the weekend my bsd 4.9 apparantly rebooted for kicks by itself, > reporting a fatal trap 12 in messages. I looked through the list history > and found some posts indicating it may be a memory issue. If you suspect a memory problem, then try getting your BIOS to find it. Reboot your machine then press whatever key you need to get into your BIOS. Look for an option which turns on extended memory checking on boot (or which turns off quick memory checking), turn on extended check, save the setting, reboot and watch the BIOS cycle through endless memory checks. If it finds a problem it'll tell you. If it does, then you'll have to try removing memory chips one-by-one to try to find the one at fault. (Note that motherboards often (always?) require the memory chips to be inserted sequentially. I.e. if you take out the first chip, you have to move all the others up -- you can't just leave the first slot empty). Make sure to use some kind of anti-static protection when handling memory chips, otherwise you really will have a memory problem. --Alex