From owner-freebsd-current@FreeBSD.ORG Sat Dec 13 00:19:55 2014 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 C11FCE3D for ; Sat, 13 Dec 2014 00:19:55 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id EDE6D8AF for ; Sat, 13 Dec 2014 00:19:54 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id CAA08194; Sat, 13 Dec 2014 02:21:40 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1XzaQz-000Cbi-S1; Sat, 13 Dec 2014 02:19:45 +0200 Message-ID: <548B85E7.7000102@FreeBSD.org> Date: Sat, 13 Dec 2014 02:18:47 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Ivan Klymenko , freebsd-current@FreeBSD.org Subject: Re: 11-CURRENT r275641 panic: Unrecoverable machine check exception References: <20141212214653.41cec479@nonamehost.local> In-Reply-To: <20141212214653.41cec479@nonamehost.local> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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, 13 Dec 2014 00:19:55 -0000 On 12/12/2014 21:46, Ivan Klymenko wrote: > Hi. > > > I see such a panic the first time in 10 years. good > Fri Dec 12 21:35:11 EET 2014 > > FreeBSD nonamehost.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r275641: Tue Dec 9 17:03:43 EET 2014 ivan@nonamehost.local:/media/da0s1/obj/usr/src/sys/mk11 amd64 > > panic: Unrecoverable machine check exception Google for "machine check exception" if you haven't yet. -- Andriy Gapon