From owner-freebsd-questions@FreeBSD.ORG Sat Jun 18 21:01:55 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69375106564A for ; Sat, 18 Jun 2011 21:01:55 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 384F48FC0C for ; Sat, 18 Jun 2011 21:01:55 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p5IL1pPn078784 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 18 Jun 2011 14:01:51 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p5IL1pSL078783; Sat, 18 Jun 2011 14:01:51 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA10527; Sat, 18 Jun 11 13:52:49 PDT Date: Sat, 18 Jun 2011 13:52:28 -0700 From: perryh@pluto.rain.com To: fred@resel.fr Message-Id: <4dfd100c.ZEvfAI/AN/67EPHi%perryh@pluto.rain.com> References: In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Messages from MCA in the kernel log X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Jun 2011 21:01:55 -0000 Frederic Perrin wrote: > ... I don't know what MCA, DRD, SNOOP and {D,G}CACHE stand for... MCA = Machine Check Architecture. DRD here probably refers to a data read cycle. SNOOP has to do with hardware-maintained cache coherency. DCACHE = data cache. Google and/or Wikipedia may help with the details. > Is it a transient error? I _think_ the COR refers to a corrected error, but that could be either transient (a random bit-flip, possibly due to a cosmic ray hit) or permanent (a bit in the cache has gone bad). In the latter case I'd expect ongoing error messages, rather than just two isolated occurrences. > Should I start screaming at my hosting provider so he changes my > CPU? I would say not, unless the errors become frequent or uncorrectable. > +MCA: Bank 0, Status 0xcc00000120040189 > +MCA: Global Cap 0x0000000000180204, Status 0x0000000000000000 > +MCA: Vendor "GenuineIntel", ID 0xf49, APIC ID 0 > +MCA: CPU 0 COR OVER GCACHE L1 SNOOP error > +MCA: Address 0x1015b00 > +MCA: Misc 0x140002d800aa0 > +MCA: Bank 1, Status 0x8000002000000135 > +MCA: Global Cap 0x0000000000180204, Status 0x0000000000000000 > +MCA: Vendor "GenuineIntel", ID 0xf49, APIC ID 0 > +MCA: CPU 0 COR DCACHE L1 DRD error