From owner-freebsd-stable@FreeBSD.ORG Sat Dec 25 00:03:57 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 27F7C106564A for ; Sat, 25 Dec 2010 00:03:57 +0000 (UTC) (envelope-from alan.l.cox@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id ABD848FC0C for ; Sat, 25 Dec 2010 00:03:56 +0000 (UTC) Received: by fxm16 with SMTP id 16so7859132fxm.13 for ; Fri, 24 Dec 2010 16:03:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=C8wStlooLdLfrjrtjhUMUiDZzWfDXdbDbZN9MdrBumQ=; b=VsYJMUZGebUhIxo6W4Mp3RIOrqW7IaFVmsk1qzUExCHh0W+duZHBaVFgMaFXnHPare jnXmJg/SfS6K09OdULk6zpNSniJR05sQZjB/DPL11w4E97C3JH/K9YrrymV7e3tLc6Ne r8AWnaQC7OnOykRH4gDSgvEFRsNmaMjpxAwU0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=iej0dXoS5+58TYta+17dDc8RILWBd182Mg09pvhMOeeZyXjrTpSC2aVFbxsI2VlBRP 9SET+Dt1NHf8zfJieACVNsMFxRYQkB6Lwrsxf8BGnKVhqlWhbNF9q+nTfin+vNnjS2iI 20go0jcxLucHxrfedSzZjqtQ3CCr24BLwucJ4= MIME-Version: 1.0 Received: by 10.223.89.143 with SMTP id e15mr1313721fam.100.1293235435605; Fri, 24 Dec 2010 16:03:55 -0800 (PST) Received: by 10.223.109.138 with HTTP; Fri, 24 Dec 2010 16:03:55 -0800 (PST) In-Reply-To: <87vd2iepkv.fsf@oak.localnet> References: <4D11F1F5.7050902@quip.cz> <201012220957.26854.jhb@freebsd.org> <4D13A579.8090004@langille.org> <87vd2iepkv.fsf@oak.localnet> Date: Fri, 24 Dec 2010 18:03:55 -0600 Message-ID: From: Alan Cox To: Carl Johnson Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: MCA messages after upgrade to 8.2-BEAT1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: alc@freebsd.org 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 00:03:57 -0000 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. Alan