From owner-freebsd-stable@FreeBSD.ORG Wed Feb 25 15:28:25 2015 Return-Path: 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 0044AD1; Wed, 25 Feb 2015 15:28:24 +0000 (UTC) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "people.fsn.hu", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 45CD17C3; Wed, 25 Feb 2015 15:28:23 +0000 (UTC) Received: by people.fsn.hu (Postfix, from userid 1001) id 631E71608397; Wed, 25 Feb 2015 16:22:07 +0100 (CET) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.3 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MF-ACE0E1EA [pR: 15.7826] X-CRM114-CacheID: sfid-20150225_16220_6B881C30 X-CRM114-Status: Good ( pR: 15.7826 ) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Wed Feb 25 16:22:07 2015 X-DSPAM-Confidence: 0.9966 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 54ede89f747381027321753 X-DSPAM-Factors: 27, From*"Nagy, Attila" , 0.00010, >+On, 0.00043, wrote+>>, 0.00103, kernel, 0.00150, kernel, 0.00150, wrote+>, 0.00180, >>+>, 0.00219, >+that, 0.00219, >+that, 0.00219, Subject*FreeBSD, 0.00251, debug, 0.00251, the+kernel, 0.00264, the+kernel, 0.00264, Received*(japan.t, 0.00418, stack, 0.00418, >>+Hi, 0.00418, >+>, 0.00432, Received*online.co.hu+[195.228.243.99]), 0.00456, Received*[195.228.243.99]), 0.00456, Received*online.co.hu, 0.00456, Received*(japan.t+online.co.hu, 0.00456, Subject*Re+FreeBSD, 0.00501, >>+>>, 0.00516, >>+>>, 0.00516, CPUs, 0.00557, Received*japan.t, 0.00557, X-Spambayes-Classification: ham; 0.00 Received: from japan.t-online.private (japan.t-online.co.hu [195.228.243.99]) by people.fsn.hu (Postfix) with ESMTPSA id 5A59A160838B; Wed, 25 Feb 2015 16:22:06 +0100 (CET) Message-ID: <54EDE89E.1070003@fsn.hu> Date: Wed, 25 Feb 2015 16:22:06 +0100 From: "Nagy, Attila" MIME-Version: 1.0 To: John Baldwin , freebsd-stable@freebsd.org Subject: Re: FreeBSD 10.1-amd64 -> booting on a HP DL380 Gen9 results in panic References: <201412220957.16974.jhb@freebsd.org> In-Reply-To: <201412220957.16974.jhb@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Rainer Duffner X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2015 15:28:25 -0000 Hi, On 12/22/14 15:57, John Baldwin wrote: > On Thursday, December 18, 2014 7:27:13 pm Rainer Duffner wrote: >> Hi, >> >> we got one to test and it booted using the UEFI memory stick image. >> >> However, I get a panic after >> Event time „LAPIC“ quality 600 >> ACPI APIC Table: >> panic: APIC: CPU with APIC ID 0 is not enabled >> cpuid = 0 >> >> and then a stack backtrace >> >> >> What does that mean? >> >> AFAIK, I have a single E5-2620V3 CPU and 16 GB RAM in there. >> >> > > Eh, the table that ACPI provides that lists the available CPUs in the system > claims that that the CPU that the kernel booted from is disabled. We assume > that the boot processor is valid and enabled (since it is running the kernel > already!) This is almost certainly a firmware bug. Booting without UEFI > would be a good test as Mark suggested. If you can capture a verbose dmesg, > that would also include enough details about what we found in the ACPI table > to debug this further perhaps. > One of my colleagues have captured a boot -v output for this machine. One line (where it prints the CPU) is missing, the others are intact: https://plus.google.com/photos/104147045962330059540/albums/6119801748474522833/6119801755965284786?banner=pwa&pid=6119801755965284786&oid=104147045962330059540 The machine is PXE-booted. I can try anything to help fixing this issue. UEFI and AFAIK the x2APIC support, which Rainer mentioned is disabled here.