From owner-freebsd-current@FreeBSD.ORG  Wed Feb 27 18:18:44 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 B7E3A396;
 Wed, 27 Feb 2013 18:18:44 +0000 (UTC)
 (envelope-from sendtomatt@gmail.com)
Received: from mail-pa0-f42.google.com (mail-pa0-f42.google.com
 [209.85.220.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8F85C3EA;
 Wed, 27 Feb 2013 18:18:44 +0000 (UTC)
Received: by mail-pa0-f42.google.com with SMTP id kq12so586271pab.29
 for <multiple recipients>; Wed, 27 Feb 2013 10:18:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=x-received:message-id:date:from:user-agent:mime-version:to:cc
 :subject:references:in-reply-to:content-type
 :content-transfer-encoding;
 bh=upWSxYYqK3oWoMK8SumUlNdfXHwUYr46MIb2sEfGOuE=;
 b=AdYrPDqIaF79OLhtbDaZqwZLOLUTyhsCjhLecuWYUPxk20ifo3ZxNheSXkr2VyW62r
 F7W11MMZers7Jhbo+Bbe+v+Nm5s8imgoS4Q43G/5cIp1fnUXg/fhT8Ao+kqk0DblNz7l
 8N8k+ygQ/kaaVp6H+kCNgpUdZTppfJQUqK1Juso4KiDJs48mYMk5AkeDaVPU0AhWGgQR
 DM3UYOLCw1deHY2er2mULYGKFV5yExEm5VqJz1OkwPYMcqqTG7XuG6Ztl3Z+TCDiJbTe
 DdkmNHPNoAZ4AiK7rdRZiRliYNOWGBJCo5jG6GpB+YxHhOkd8VnXbCfNTovpgfMbZU8J
 s7NA==
X-Received: by 10.66.163.104 with SMTP id yh8mr8842198pab.170.1361989124062;
 Wed, 27 Feb 2013 10:18:44 -0800 (PST)
Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net.
 [70.36.223.239])
 by mx.google.com with ESMTPS id u10sm6125928pax.14.2013.02.27.10.18.41
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 27 Feb 2013 10:18:43 -0800 (PST)
Message-ID: <512E4DC4.5070608@gmail.com>
Date: Wed, 27 Feb 2013 10:17:40 -0800
From: matt <sendtomatt@gmail.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130224 Thunderbird/17.0.3
MIME-Version: 1.0
To: John Baldwin <jhb@freebsd.org>
Subject: Re: CPU0: Local APIC error 0x80
References: <512A70AC.6050906@gmail.com> <201302271208.39119.jhb@freebsd.org>
In-Reply-To: <201302271208.39119.jhb@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
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 18:18:44 -0000

On 02/27/13 09:08, John Baldwin wrote:
> 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.
>
Not surprising, is there any potential damage from allowing it to continue?

Thanks,

Matt