From owner-freebsd-questions@FreeBSD.ORG Sat May 23 21:39:06 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D7E978AE for ; Sat, 23 May 2015 21:39:06 +0000 (UTC) Received: from know-smtprelay-omc-7.server.virginmedia.net (know-smtprelay-omc-7.server.virginmedia.net [80.0.253.71]) by mx1.freebsd.org (Postfix) with ESMTP id 51EDC10C5 for ; Sat, 23 May 2015 21:39:05 +0000 (UTC) Received: from localhost.localdomain ([81.106.150.188]) by know-smtprelay-7-imp with bizsmtp id XZdv1q00L4481jl01ZdvZ0; Sat, 23 May 2015 22:37:55 +0100 X-Originating-IP: [81.106.150.188] X-Spam: 0 X-Authority: v=2.1 cv=JuUM15MC c=1 sm=1 tr=0 a=DGj713NdaxKrsjjgQne7PA==:117 a=DGj713NdaxKrsjjgQne7PA==:17 a=J0QyKEt1u0cA:10 a=IkcTkHD0fZMA:10 a=NLZqzBF-AAAA:8 a=h1PgugrvaO0A:10 a=hb8eiC_dZrjDKqt6VAYA:9 a=QEXdDO2ut3YA:10 Received: by localhost.localdomain (Postfix, from userid 500) id 4F6AA8887A; Sat, 23 May 2015 22:37:55 +0100 (BST) Date: Sat, 23 May 2015 22:37:55 +0100 From: Ken Moffat To: jd1008 Cc: FreeBSD Users Subject: Re: Replacing cpu Message-ID: <20150523213755.GB9728@milliways> References: <5560B408.4000601@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Clacks-Overhead: GNU Terry Pratchett Content-Transfer-Encoding: 8bit In-Reply-To: <5560B408.4000601@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 21:39:06 -0000 On Sat, May 23, 2015 at 11:08:24AM -0600, jd1008 wrote: > > I am wondering why the memtest does not freeze???? > could it be that only one core is causing the problem? > If you use current memtest86+ (notthe original memtest86), there is an option to use all cores (F2, I think) but you need to be quick to take advantage of that or the message about it will disappear from the screen. It is off by default because on many machines (including all of those on which I tried it) the box will lock up hard after not very many minutes in one of the tests (around test number 7, if my memory serves). While it runs you will see a |/-\ sequence spinning on each CPU, instead of just on the first. It might also be that memtest does not exercise whatever part of the machine is failing. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m.