From owner-freebsd-current@FreeBSD.ORG Sat Jan 17 17:43:33 2015 Return-Path: Delivered-To: freebsd-current@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 84CE38D9 for ; Sat, 17 Jan 2015 17:43:33 +0000 (UTC) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 44B40368 for ; Sat, 17 Jan 2015 17:43:32 +0000 (UTC) Received: from [93.104.2.22] (helo=c720-r276659) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1YCXPF-0005Pk-2U; Sat, 17 Jan 2015 18:43:29 +0100 Date: Sat, 17 Jan 2015 18:43:26 +0100 From: Matthias Apitz To: Eric van Gyzen Subject: Re: kernel: MCA: CPU 0 COR (1) internal parity error Message-ID: <20150117174326.GA40205@c720-r276659> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , Eric van Gyzen , freebsd-current@freebsd.org, jdc@koitsu.org References: <20150116194539.GA2230@c720-r276659> <54B96EE4.5090702@vangyzen.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <54B96EE4.5090702@vangyzen.net> X-Operating-System: FreeBSD 11.0-CURRENT r269739 (i386) User-Agent: Mutt/1.5.23 (2014-03-12) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 93.104.2.22 Cc: jdc@koitsu.org, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 17:43:33 -0000 El día Friday, January 16, 2015 a las 03:04:52PM -0500, Eric van Gyzen escribió: > On 01/16/2015 14:45, Matthias Apitz wrote: > > Jan 16 12:04:24 c720-r276659 kernel: MCA: Bank 0, Status 0x90000040000f0005 > > Jan 16 12:04:24 c720-r276659 kernel: MCA: Global Cap 0x0000000000000c07, Status 0x0000000000000000 > > Jan 16 12:04:24 c720-r276659 kernel: MCA: Vendor "GenuineIntel", ID 0x40651, APIC ID 0 > > Jan 16 12:04:24 c720-r276659 kernel: MCA: CPU 0 COR (1) internal parity error > > Try ports/sysutils/mcelog. I have installed that port and launched it as # mcelog > mcelog.txt ... mcelog: Unsupported new Family 6 Model 45 CPU: only decoding architectural errors mcelog: Unsupported new Family 6 Model 45 CPU: only decoding architectural errors mcelog: Unsupported new Family 6 Model 45 CPU: only decoding architectural errors ... (the messages are STDERR); in 'mcelog.txt' it has for the last event from /var/log/messages: Jan 17 18:23:54 c720-r276659 kernel: MCA: Bank 0, Status 0x90000040000f0005 Jan 17 18:23:54 c720-r276659 kernel: MCA: Global Cap 0x0000000000000c07, Status 0x0000000000000000 Jan 17 18:23:54 c720-r276659 kernel: MCA: Vendor "GenuineIntel", ID 0x40651, APIC ID 0 Jan 17 18:23:54 c720-r276659 kernel: MCA: CPU 0 COR (1) internal parity error the following lines (the uptime matches): ... HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor MCE 32 CPU 0 BANK 0 TSC 36eec80fd688 [at 1397 Mhz 0 days 12:0:41 uptime (unreliable)] MCG status: MCi status: Error enabled MCA: Unknown Error 5 STATUS 90000040000f0005 MCGSTATUS 0 MCGCAP c07 APICID 0 SOCKETID 0 CPUID Vendor Intel Family 6 Model 69 Questions: a) Is the output of mcelog valid (regardless of the msg on STDERR of 'unsupported model')? b) Is it worth to contact the dealer or wait until it is broken completely? Thanks matthias -- Matthias Apitz, guru@unixarea.de, http://www.unixarea.de/ +49-170-4527211 1989-2014: The Wall was torn down so that we go to war together again. El Muro ha sido derribado para que nos unimos en ir a la guerra otra vez. Diese Grenze wurde aufgehoben damit wir gemeinsam wieder in den Krieg ziehen.