From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 18:04:43 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE47816A40E for ; Wed, 19 Apr 2006 18:04:43 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6646543D66 for ; Wed, 19 Apr 2006 18:04:43 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.13.6/8.13.6) with ESMTP id k3JI4g4V047049; Wed, 19 Apr 2006 11:04:42 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.6/8.13.6/Submit) id k3JI4gAm047048; Wed, 19 Apr 2006 11:04:42 -0700 (PDT) (envelope-from sgk) Date: Wed, 19 Apr 2006 11:04:42 -0700 From: Steve Kargl To: Thomas SOETE Message-ID: <20060419180442.GA46936@troutmask.apl.washington.edu> References: <44467768.2080809@soete.info> <20060419175651.GA71495@xor.obsecurity.org> <44467A6C.3070401@soete.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44467A6C.3070401@soete.info> User-Agent: Mutt/1.4.2.1i Cc: hackers@freebsd.org, Kris Kennaway Subject: Re: Kernel Fatal Trap 12 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 18:04:43 -0000 On Wed, Apr 19, 2006 at 07:59:08PM +0200, Thomas SOETE wrote: > Kris Kennaway a ?crit : > >On Wed, Apr 19, 2006 at 07:46:16PM +0200, Thomas SOETE wrote: > > > >>Hi everybody > >>Since a little time I began to have some kernel fatal trap 12 > >> > > > >Kernel panics that magically start for no reason after a long time of > >stability are usually because your hardware has begun to fail. > > > >Kris > > > > Hum, is there a way to have a little idea of which hardware begun to fail ? > (Top post fixed!) Start by checking memory. If you have x86 hardware, then look at memtest86+. http://www.memtest.org/ -- Steve