From owner-freebsd-current@FreeBSD.ORG Thu Dec 18 21:49:20 2014 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4316E490; Thu, 18 Dec 2014 21:49:20 +0000 (UTC) Received: from frv25.fwdcdn.com (frv25.fwdcdn.com [212.42.77.25]) by mx1.freebsd.org (Postfix) with ESMTP id 005B32BB1; Thu, 18 Dec 2014 21:49:19 +0000 (UTC) Received: from [10.10.14.27] (helo=frv27.fwdcdn.com) by frv25.fwdcdn.com QID:1Y1iwa-0009Da-6F/RC:2; Thu, 18 Dec 2014 23:49:12 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=lGm6hzsgPH/QRQrldG1lRRHuwhjn6uyqGYekzcOagPE=; b=XL3SJdRZ++JKD/JAOuCkEkk9WM7jVsCGNOd+o1VOjv0PDvGkDFH3cIB2NMV8T2N5lf7llI38zVIDuKDyWX1aCk/RaciyU3QZU4YcDBrmm9b+UnJenWjIQcwu96Fm1+DkLRxlBF+TumcxWlaRfvUkYD0wepWVc1eA8KXNebVytcw=; Received: from [178.137.224.146] (helo=nonamehost.local) by frv27.fwdcdn.com with esmtpsa ID 1Y1ifG-000GiH-Kk ; Thu, 18 Dec 2014 23:31:18 +0200 Date: Thu, 18 Dec 2014 23:31:17 +0200 From: Ivan Klymenko To: "Rang, Anton" Subject: Re: 11-CURRENT r275641 panic: Unrecoverable machine check exception Message-ID: <20141218233117.045a8ed9@nonamehost.local> In-Reply-To: References: <20141212214653.41cec479@nonamehost.local> <548B85E7.7000102@FreeBSD.org> <20141213113823.660a1e05@nonamehost.local> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Authentication-Result: IP=178.137.224.146; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-Ukrnet-Yellow: 0 Cc: "freebsd-current@FreeBSD.org" , Andriy Gapon 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: Thu, 18 Dec 2014 21:49:20 -0000 =D0=92 Mon, 15 Dec 2014 17:49:54 +0000 "Rang, Anton" =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > I certainly could be wrong - but how to know for sure the cause of > > the panic? >=20 > > MCA: CPU 0 UNCOR PCC OVER DCACHE L2 DRD error > > MCA: Address 0xbd8d4cc0 > > MCA: Misc 0x30e3000086 >=20 > The "root cause" may be hard to determine, but the immediate cause > was helpfully decoded by the kernel. (Though I don't know whether all > of the model-specific fields were decoded.) >=20 > UNCOR =3D uncorrected error > PCC =3D processor context corrupted (can't safely continue to execute, > thus the panic) OVER =3D error overflow (hmmm, multiple errors occurred) > DCACHE L2 DRD =3D data being read from L2 data cache >=20 > The miscellaneous register indicates that 0xbd8d4cc0 is a physical > address. >=20 > So this looks like a processor failure. If it is repeatable, though, > it may indicate either failed hardware or some problem in configuring > the processor (though I'm not sure how that could lead to a cache > error). >=20 > Anton Thank you.