From owner-freebsd-current@freebsd.org Mon May 2 20:57:01 2016 Return-Path: Delivered-To: freebsd-current@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 E764EB2AFFC for ; Mon, 2 May 2016 20:57:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C99B01FD4 for ; Mon, 2 May 2016 20:57:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id DE0A1B977; Mon, 2 May 2016 16:57:00 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Cc: Bill O'Hanlon Subject: Re: Kernel panic from recent build Date: Mon, 02 May 2016 13:55:26 -0700 Message-ID: <1616736.1pUkklcWcu@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 02 May 2016 16:57:01 -0400 (EDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Mon, 02 May 2016 20:57:02 -0000 On Monday, May 02, 2016 01:35:54 PM Bill O'Hanlon wrote: > =E2=80=8B > IMG_20160502_130335.jpg > > =E2=80=8B > I'm getting the following panic from a recent (May 2, 2016) build. > panic: Duplicate local APIC ID 0 >=20 > The system is a Dell Precision T5500 with generic factory BIOS settin= gs. > It has run previous builds without event for several years. >=20 > I'm attaching a link to a photo of the screen for added details. Try setting 'hint.srat.0.disabled=3D1' at the loader prompt and then gr= ab the output of 'acpidump -t' on your next boot. The SRAT table used by the NUMA code appears to be corrupted by your BIOS. --=20 John Baldwin