From owner-freebsd-stable@FreeBSD.ORG  Mon Dec 22 15:06:52 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@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 6D9C03FE
 for <freebsd-stable@freebsd.org>; Mon, 22 Dec 2014 15:06:52 +0000 (UTC)
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 4665A837
 for <freebsd-stable@freebsd.org>; Mon, 22 Dec 2014 15:06:52 +0000 (UTC)
Received: from jhbbsd.localnet (unknown [209.249.190.124])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id 3866EB9C7;
 Mon, 22 Dec 2014 10:06:51 -0500 (EST)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-stable@freebsd.org
Subject: Re: FreeBSD 10.1-amd64 -> booting on a HP DL380 Gen9 results in panic
Date: Mon, 22 Dec 2014 09:57:16 -0500
User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; )
References: <D6F4B783-67B8-4447-8618-E5C472178246@ultra-secure.de>
In-Reply-To: <D6F4B783-67B8-4447-8618-E5C472178246@ultra-secure.de>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201412220957.16974.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Mon, 22 Dec 2014 10:06:51 -0500 (EST)
Cc: Rainer Duffner <rainer@ultra-secure.de>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2014 15:06:52 -0000

On Thursday, December 18, 2014 7:27:13 pm Rainer Duffner wrote:
> Hi,
>=20
> we got one to test and it booted using the UEFI memory stick image.
>=20
> However, I get a panic after
> Event time =E2=80=9ELAPIC=E2=80=9C quality 600
> ACPI APIC Table: <HP     Proliant>
> panic: APIC: CPU with APIC ID 0 is not enabled
> cpuid =3D 0
>=20
> and then a stack backtrace
>=20
>=20
> What does that mean?
>=20
> AFAIK, I have a single E5-2620V3 CPU and 16 GB RAM in there.
>=20
>=20
> It=E2=80=99s primarily intended as a test-system - but earlier or later I=
 will have=20
to put one into production because we=E2=80=99ll likely stop procuring Gen8=
 systems=20
sometime next year (when they simply stop becoming available).
>=20
> I haven=E2=80=99t tried a snapshot of current.

Eh, the table that ACPI provides that lists the available CPUs in the syste=
m=20
claims that that the CPU that the kernel booted from is disabled.  We assum=
e=20
that the boot processor is valid and enabled (since it is running the kerne=
l=20
already!)  This is almost certainly a firmware bug.  Booting without UEFI=20
would be a good test as Mark suggested.  If you can capture a verbose dmesg=
,=20
that would also include enough details about what we found in the ACPI tabl=
e=20
to debug this further perhaps.

=2D-=20
John Baldwin