From owner-freebsd-stable@FreeBSD.ORG Mon Jun 10 16:21:12 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 90D06912 for ; Mon, 10 Jun 2013 16:21:12 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) by mx1.freebsd.org (Postfix) with ESMTP id 6D9731186 for ; Mon, 10 Jun 2013 16:21:12 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id BA5CFB915; Mon, 10 Jun 2013 12:21:11 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Subject: Re: ACPI Warning, then hang Date: Mon, 10 Jun 2013 12:19:00 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <20130610143507.GA66619@icarus.home.lan> In-Reply-To: <20130610143507.GA66619@icarus.home.lan> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201306101219.01193.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 10 Jun 2013 12:21:11 -0400 (EDT) Cc: Jeremy Chadwick , Bryce Edwards X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jun 2013 16:21:12 -0000 On Monday, June 10, 2013 10:35:07 am Jeremy Chadwick wrote: > On Mon, Jun 10, 2013 at 09:18:14AM -0500, Bryce Edwards wrote: > > I'm getting the following warning, and then the system locks: > > > > ACPI Warning: Incorrect checksum in table [(bunch of spaces)] - 0x29, > > should be 0x48 > > > > Here's a pic: http://db.tt/O6dxONzI > > > > System is on a SuperMicro C7X58 motherboard that I just upgraded to > > BIOS 2.0a, which I would like to stay on if possible. I tried > > adjusting all the ACPI related BIOS settings without success. > > The message in question refers to hard-coded data in one of the many > ACPI tables (see acpidump(8) for the list -- there are many). ACPI > tables are stored within the BIOS -- the motherboard/BIOS vendor has > full control over all of them and is fully 100% responsible for their > content. > > It looks to me like they severely botched their BIOS, or somehow it got > flashed wrong. > > You need to contact Supermicro Technical Support and tell them of the > problem. They need to either fix their BIOS, or help figure out what's > become corrupted. You can point them to this thread if you'd like. > > I should note that the corruption/issue is major enough that you are > missing very key/important lines from your dmesg (after "avail memory" > but before "kdbX at kdbmuxX", which come from pure reliance upon ACPI. > Lines such as: > > Event timer "LAPIC" quality 400 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > FreeBSD/SMP: 1 package(s) x 4 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > > In the meantime, you can try booting without ACPI support (there should > be a boot-up menu option for that) and pray that works. If it doesn't, > then your workaround is to roll back to an older BIOS version and/or put > pressure on Supermicro. You will find their Technical Support folks are > quite helpful/responsive to technical issues. > > Good luck and keep us posted on what transpires. Actually, that message is mostly harmless. All sorts of vendors ship tables with busted checksums that are in fact fine. :( However, the table name looks very odd which is more worrying. Booting without ACPI enabled would be a good first step. Trying a verbose boot to capture the last message before the hang would also be useful. -- John Baldwin