From owner-freebsd-current@FreeBSD.ORG  Wed Feb 27 17:12:52 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 46F3B9B4
 for <freebsd-current@freebsd.org>; Wed, 27 Feb 2013 17:12:52 +0000 (UTC)
 (envelope-from jhb@freebsd.org)
Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net
 [IPv6:2001:470:1f10:75::2])
 by mx1.freebsd.org (Postfix) with ESMTP id 22139F79
 for <freebsd-current@freebsd.org>; Wed, 27 Feb 2013 17:12:52 +0000 (UTC)
Received: from jhbbsd.localnet (unknown [209.249.190.124])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id 7932DB91E;
 Wed, 27 Feb 2013 12:12:51 -0500 (EST)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-current@freebsd.org
Subject: Re: CPU0: Local APIC error 0x80
Date: Wed, 27 Feb 2013 12:08:39 -0500
User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; )
References: <512A70AC.6050906@gmail.com>
In-Reply-To: <512A70AC.6050906@gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201302271208.39119.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Wed, 27 Feb 2013 12:12:51 -0500 (EST)
Cc: matt <sendtomatt@gmail.com>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 17:12:52 -0000

On Sunday, February 24, 2013 2:57:32 pm matt wrote:
> What does this mean exactly?
> 
> Whenever I call/evaluate certain ACPI paths, this gets printed on console.
> 
> I assume it's a concurrent access issue or something, or perhaps just a
> bios/uefi problem?

#define	APIC_ESR_ILLEGAL_REGISTER	0x00000080

It means something wrote to an invalid lapic register.  It is probably a bug 
in your BIOS, yes.

-- 
John Baldwin