From owner-freebsd-acpi@FreeBSD.ORG  Sun Nov  6 22:45:03 2005
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
X-Original-To: freebsd-acpi@FreeBSD.org
Delivered-To: freebsd-acpi@FreeBSD.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C351E16A41F;
	Sun,  6 Nov 2005 22:45:03 +0000 (GMT) (envelope-from nate@root.org)
Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C231E43D6A;
	Sun,  6 Nov 2005 22:44:58 +0000 (GMT) (envelope-from nate@root.org)
Received: from [10.0.5.50] (ppp-71-139-0-107.dsl.snfc21.pacbell.net
	[71.139.0.107])
	by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jA6MiUxq018172
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Sun, 6 Nov 2005 14:44:31 -0800
Message-ID: <436E874E.4010305@root.org>
Date: Sun, 06 Nov 2005 14:44:30 -0800
From: Nate Lawson <nate@root.org>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vaibhave Agarwal <vaibhave@cs.utah.edu>
References: <20051027233636.GA39380@dmw.hopto.org>	<Pine.LNX.4.61.0510281621120.19263@trust.cs.utah.edu>	<Pine.LNX.4.61.0511060450130.4600@trust.cs.utah.edu>	<200511061012.57212.jhb@FreeBSD.org>
	<Pine.LNX.4.61.0511061525330.16649@trust.cs.utah.edu>
In-Reply-To: <Pine.LNX.4.61.0511061525330.16649@trust.cs.utah.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-net@FreeBSD.org, freebsd-acpi@FreeBSD.org, chris@gnome.co.uk,
	current@FreeBSD.org, John Baldwin <jhb@FreeBSD.org>
Subject: Re: Freebsd 6.0 doesnt detect local APIC on a Pentium 3 machine
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Nov 2005 22:45:04 -0000

Vaibhave Agarwal wrote:
> On Sun, 6 Nov 2005, John Baldwin wrote:
> 
> 
>>We don't detect the local APIC via MSR's or the APIC bit in cpu_features, but 
>>rely on a working MP Table or MADT table to setup both the local APIC(s) and 
>>I/O APIC(s).  Does your machine have a valid MP Table or an APIC table in its 
>>acpidump?  Many UP machine BIOSes don't include those tables.
>>
> 
> 
> I think you are right.
> There is no valid APIC table in the acpidump.
> The only place where APIC is mentioned in the acpidump(8) is in following:
> 
> Scope (\_SB)
> {
> 	Name (APIC, 0x00)
>         Method (_PIC, 1, NotSerialized)
>         {
>             Store (Arg0, APIC)
>         }
> }
> 
> 
> And I suppose APIC is disabled in the BIOS too.
> Is there a way to enable APIC using software, without changing the BIOS, 
> since I dont have access to the BIOS, as it is a remote machine (with 
> root access) ?

The above references to APIC just store a value in a convenience 
variable.  If there's nothing else in the AML that references the 
\_SB.APIC variable, then it has no effect on the system.  In that case, 
the only way to get APIC support on that machine is to implement another 
way of enumerating it.

-- 
Nate