From owner-freebsd-hackers@FreeBSD.ORG Thu May 6 08:56:57 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EFA661065670 for ; Thu, 6 May 2010 08:56:57 +0000 (UTC) (envelope-from atom@smasher.org) Received: from atom.smasher.org (atom.smasher.org [69.55.237.145]) by mx1.freebsd.org (Postfix) with SMTP id BDFAA8FC17 for ; Thu, 6 May 2010 08:56:57 +0000 (UTC) Received: (qmail 80211 invoked by uid 1000); 6 May 2010 08:56:54 -0000 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Date: Thu, 6 May 2010 20:57:05 +1200 (NZST) From: Atom Smasher Message-ID: <1005062053260.2629@smasher> MIME-Version: 1.0 OpenPGP: id=0xB88D52E4D9F57808; algo=1 (RSA); size=4096; url=http://atom.smasher.org/pgp.txt To: freebsd-hackers@freebsd.org X-POM: The Moon is Waning Crescent (49% of Full) X-Hashcash: 1:20:1005060857:freebsd-hackers@freebsd.org::8gwbgf2z/YC+dpwO:000000 0000000000000000000000004rWF Subject: bad RAM? prove it with a crash dump? 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: Thu, 06 May 2010 08:56:58 -0000 i suspect i've got bad RAM but memtest has run through several dozen iterations without a problem. my (3 year old) laptop will run for a few days or weeks and then crash/freeze/hang. i've enabled crash dumps and i'm wondering if/how the dump might be able to (dis)prove that the RAM is bad. any ideas? thanks... -- ...atom ________________________ http://atom.smasher.org/ 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808 ------------------------------------------------- "What luck for rulers, that men do not think." -- Adolf Hitler