From owner-freebsd-stable@FreeBSD.ORG Mon Jun 10 16:27:37 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BFB74F8 for ; Mon, 10 Jun 2013 16:27:37 +0000 (UTC) (envelope-from bryce@bryce.net) Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 8B1B71242 for ; Mon, 10 Jun 2013 16:27:37 +0000 (UTC) Received: by mail-ob0-f172.google.com with SMTP id wo10so10387471obc.17 for ; Mon, 10 Jun 2013 09:27:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=qa9llGqMPHlA2wWpPCKIkdg3u1+Be8quVtsKr2NyGTE=; b=ICNWWglC0alNzuGsrVQ/6NpIvzxrFgWjGmHKR2IoGqKvFdOs+7Q8RkjhGAJolFmrmT Ni/2k0UCK7IwCpeRgZYyZglkEppRm4UEzvKvIHarpjvDFOQjtp/0l6X/DRnsFZnwjL2r FnFSOCylektB7phFSYk0JqlPZ7hQsbpEnWJzIfut9oYDwUffqj+CkQjpqTInZ6WE8nsw VYyNAvbs8VqJ3lTEhP5SayrCjMP2UmKJ57ntuqZo47abDzYpWlsqyz02/zZqUCeQsl05 1er/bsbTDuErmOMxJsxJkjXlnpV54dnDFRcueXYsRiiL+Hxl/k4vFxnKl7bgHicF57zw 0G2A== MIME-Version: 1.0 X-Received: by 10.60.33.4 with SMTP id n4mr8525088oei.49.1370881657020; Mon, 10 Jun 2013 09:27:37 -0700 (PDT) Received: by 10.60.77.105 with HTTP; Mon, 10 Jun 2013 09:27:36 -0700 (PDT) In-Reply-To: <201306101219.01193.jhb@freebsd.org> References: <20130610143507.GA66619@icarus.home.lan> <201306101219.01193.jhb@freebsd.org> Date: Mon, 10 Jun 2013 11:27:36 -0500 Message-ID: Subject: Re: ACPI Warning, then hang From: Bryce Edwards To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQm8MTR9fXxC0t0Q4NjunDI73nFRP76Gco1CJ1azAW4wj1Pv3Pw/bjRBiI0XOiIULBANDpKb 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:27:37 -0000 On Mon, Jun 10, 2013 at 11:19 AM, John Baldwin wrote: > 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 Booting without ACPI did not work for me, although I might be able to hack away at lots of BIOS setting to make it work. It didn't assign IRQ's to things like the storage controller, etc. soI thought it was probably not worth the effort. I did contact SuperMicro support as well, so we'll see what they have to say. I'll get a verbose boot posted up in a bit. Bryce