From owner-freebsd-wireless@freebsd.org Tue May 23 17:45:31 2017 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7228D7AE65 for ; Tue, 23 May 2017 17:45:31 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AE8E6145E; Tue, 23 May 2017 17:45:31 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [10.44.135.177] (nat-192-187-90-116.nat.tribpub.com [192.187.90.116]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 3477e886 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 23 May 2017 10:45:30 -0700 (PDT) Subject: Re: Panic On Restarting netif To: Andriy Gapon , "freebsd-wireless@freebsd.org" References: <98a7a7a7-0227-385f-4cee-87f352490345@nomadlogic.org> From: Pete Wright Message-ID: <1f7f1692-12be-451e-d9f6-995a70476651@nomadlogic.org> Date: Tue, 23 May 2017 10:45:30 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2017 17:45:31 -0000 On 05/23/2017 10:42, Andriy Gapon wrote: > On 23/05/2017 20:28, Pete Wright wrote: >> MCA: Bank 6, Status 0xfe00000000801136 >> MCA: Global Cap 0x0000000000000c08, Status 0x0000000000000005 >> MCA: Vendor "GenuineIntel", ID 0x806e9, APIC ID 2 >> MCA: CPU 2 UNCOR PCC OVER DCACHE L2 DRD error > This looks like an uncorrectable [hardware] error in the CPU2 L2 cache. > The CPU might have started dying. > I hope that's not the case, this is a new Kabylake system :( Time to run extended BIOS diagnostics over lunch. cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA