From owner-freebsd-stable@FreeBSD.ORG Sat Dec 25 04:48:10 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 740951065673 for ; Sat, 25 Dec 2010 04:48:10 +0000 (UTC) (envelope-from carlj@peak.org) Received: from redcondor2.peak.org (redcondor2.peak.org [69.59.192.56]) by mx1.freebsd.org (Postfix) with ESMTP id 3FD818FC12 for ; Sat, 25 Dec 2010 04:48:10 +0000 (UTC) Received: from peak-mail-gateway.peak.org ([69.59.192.42]) by redcondor2.peak.org ({6c724cae-de34-4c5f-b615-3072b86419fa}) via TCP (outbound) with ESMTP id 20101225044809316 for ; Sat, 25 Dec 2010 04:48:09 +0000 X-RC-FROM: X-RC-RCPT: Received: from oak.localnet (207.55.91.159.peak.org [207.55.91.159] (may be forged)) by peak-mail-gateway.peak.org (8.12.10/8.12.8) with ESMTP id oBP4m8W7023045 for ; Fri, 24 Dec 2010 20:48:09 -0800 (PST) Received: from oak.localnet (localhost [127.0.0.1]) by oak.localnet (Postfix) with ESMTP id 7E300CCAC for ; Fri, 24 Dec 2010 20:48:08 -0800 (PST) Received: (from carlj@localhost) by oak.localnet (8.14.4/8.14.4/Submit) id oBP4m8B6017688; Fri, 24 Dec 2010 20:48:08 -0800 (PST) (envelope-from carlj@peak.org) X-Authentication-Warning: oak.localnet: carlj set sender to carlj@peak.org using -f From: Carl Johnson To: freebsd-stable@freebsd.org References: <4D11F1F5.7050902@quip.cz> <201012220957.26854.jhb@freebsd.org> <4D13A579.8090004@langille.org> <87vd2iepkv.fsf@oak.localnet> Date: Fri, 24 Dec 2010 20:48:08 -0800 In-Reply-To: (Alan Cox's message of "Fri, 24 Dec 2010 18:03:55 -0600") Message-ID: <87r5d6e9vb.fsf@oak.localnet> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: MCA messages after upgrade to 8.2-BEAT1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Dec 2010 04:48:10 -0000 Alan Cox writes: > On Fri, Dec 24, 2010 at 5:08 PM, Carl Johnson wrote: > >> Alan Cox writes: >> >> > 2010/12/23 Dan Langille >> > >> >> On 12/22/2010 9:57 AM, John Baldwin wrote: >> >> >> >>> On Wednesday, December 22, 2010 7:41:25 am Miroslav Lachman wrote: >> >>> >> >>>> Dec 21 12:42:26 kavkaz kernel: MCA: Bank 0, Status 0xd40e400000000833 >> >>>> Dec 21 12:42:26 kavkaz kernel: MCA: Global Cap 0x0000000000000105, >> >>>> Status 0x0000000000000000 >> >>>> Dec 21 12:42:26 kavkaz kernel: MCA: Vendor "AuthenticAMD", ID 0x40f33, >> >>>> APIC ID 0 >> >>>> Dec 21 12:42:26 kavkaz kernel: MCA: CPU 0 COR OVER BUSLG Source DRD >> >>>> Memory >> >>>> Dec 21 12:42:26 kavkaz kernel: MCA: Address 0x236493c0 >> >>>> >> >>> >> >>> You are getting corrected ECC errors in your RAM. You see them once an >> >>> hour >> >>> because we poll the machine check registers once an hour. If this >> happens >> >>> constantly you might have a DIMM that is dying? >> >>> >> >> >> >> John: >> >> >> >> I take it these ECC errors *may* have been happening for some time. What >> >> has changed is the OS now polls for the errors and reports them. >> >> >> >> >> > Yes, we enabled MCA by default in 8.1-RELEASE. >> >> Is there some reason that it is only available for i386 and not for >> amd64? Linux has something called mcelog, for machine check errors, >> which sounds similar and is available for amd64. >> >> > Perhaps I'm misunderstanding your question, but our MCA driver is supported > and enabled by default on both i386 and amd64. Thanks, it appears that I misunderstood. I ran whereis and found /usr/src/sbin/mca and didn't find it on my amd64 system. I do see it in my sysctl listing now that I look there. -- Carl Johnson carlj@peak.org