From owner-freebsd-stable@FreeBSD.ORG Thu Sep 30 14:13:03 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 988F51065675 for ; Thu, 30 Sep 2010 14:13:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 68D688FC1B for ; Thu, 30 Sep 2010 14:13:03 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 1C7EE46B6C; Thu, 30 Sep 2010 10:13:03 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 70FA48A04F; Thu, 30 Sep 2010 10:13:01 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Thu, 30 Sep 2010 09:40:43 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20100819; KDE/4.4.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201009300940.43136.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 30 Sep 2010 10:13:02 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Adam Vande More Subject: Re: MCA messages in dmesg 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: Thu, 30 Sep 2010 14:13:03 -0000 On Thursday, September 30, 2010 2:49:24 am Adam Vande More wrote: > For awhile now, my home server has been acting up. Actually it had a bad > set of RAM long ago, replaced and it and worked fine. It's been weird again > now, and I've found this in dmesg: > > MCA: Bank 0, Status 0xf200000000000800 > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6fb, APIC ID 2 > MCA: CPU 2 UNCOR PCC OVER BUSL0 Source ERR Memory > MCA: Bank 0, Status 0xf200000000000800 > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6fb, APIC ID 3 > MCA: CPU 3 UNCOR PCC OVER BUSL0 Source ERR Memory Are you getting a panic when this happens? -- John Baldwin