The first question would be, what does Windows do with this?
To answer your question:
ACPICA does not support forward references within control methods, it never has. There is good reason for this:
Return (CS01)
If (ABCD)
{
Name (CS01, 1)
}
Else
{
Name (CS01, 2)
}
What should be returned?
Lin Ming, here is a simplified version of the code example, please run it on Windows:
DefinitionBlock ("gr.aml", "DSDT", 1, "TEST", "CPU0CST", 1)
{
Name (ABCD, 1)
Method (_CST, 0, NotSerialized)
{
If (LAnd (ABCD, 0x10))
{
Return (CS03)
}
Return (CS01)
Name (CS01, 1)
Name (CS03, 3)
}
}
>-----Original Message-----
>From: Zhang, Rui
>Sent: Sunday, November 09, 2008 10:47 PM
>To: Moore, Robert; Lin, Ming M
>Cc: bubak@xxxxxxxxxxxxxxxxx; Zhang, Rui; linux-acpi; Len Brown
>Subject: Re: Namespace lookup failure error on QuadCore E5420
>
>Hi, Bob and Ming,
>
>Please look at this piece of AML code in the cpu0cst (a dynamic SSDT
>table).
>Method (_CST, 0, NotSerialized)
> {
> If (LAnd (PDC1, 0x10))
> {
> Return (CS03)
> }
>
> Return (CS01)
> Name (CS01, Package (0x02)
> {
> ...
> })
> Name (CS03, Package (0x04)
> {
> ...
> })
>}
>
>CS01/CS03 is evaluated before it's defined, causing an AE_NOT_FOUND
>error.
>Should we fix it in ACPICA?
>
>thanks,
>rui
>
>On Mon, 2008-11-10 at 13:26 +0800, Peter Strazovec wrote:
>> On Mon, Nov 10, 2008 at 09:32:49AM +0800, Zhang Rui wrote:
>> > On Sun, 2008-11-09 at 21:48 +0800, Peter Strazovec wrote:
>> > > I have problem with Namespace lookup failure error on E5420.
>> > > ( ACPI Error (psargs-0358): [CS03] Namespace lookup failure,
>AE_NOT_FOUND )
>> > > Thus acpi not functional (cpufrequ via p-states, etc...).
>> > >
>> > ACPI is enabled on your system, except the cpu c-state.
>> >
>> > First please download the latest pmtools at
>> > http://www.lesswatts.org/projects/acpi/utilities.php
>> >
>> > and then please run
>> > "./acpidump > acpidump.log"
>> > "./acpidump --addr 0xcfe5f800 --length 0xd8 > cpu0cst"
>> > ???"./acpidump --addr 0xcfe5f900 --length 0xd8 > cpu1cst"
>> > ???"./acpidump --addr 0xcfe5fa00 --length 0xd8 > cpu2cst"
>> > ???"./acpidump --addr 0xcfe5fb00 --length 0xd8 > cpu3cst"
>> > and attach all these files.
>> >
>> > Btw, how do you know p-state is not functional?
>> > the p-state sysfs I/F (/sys/devices/system/cpu/cpuX/cpufreq/)doesn't
>> > work for you?
>> >
>> > thanks,
>> > rui
>> >
>> > > Does anyone know about some patch or some hint?
>> > >
>> > > CONFIG_ACPI_DEBUG=y, CONFIG_ACPI_DEBUG_FUNC_TRACE=y,
>> > > dmesg, interrupts and cpuinfo attached.
>> > >
>> > > thanks
>> > > Pete
>> >
>> > --
>> > To unsubscribe from this list: send the line "unsubscribe linux-acpi"
>in
>> > the body of a message to majordomo@xxxxxxxxxxxxxxx
>> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>> I though, that 'namespace' error is like 'not working'.... anyhow:
>>
>> @cpu c-state
>> mhmm, I've been talking about p-state ( CONFIG_X86_ACPI_CPUFREQ ) and
>not
>> working because:
>> #cpufreq-set -g performance
>> wrong, unknown or unhandled CPU?
>> #ls /sys/devices/system/cpu/cpu0/
>> cache thermal_throttle topology
>> -> no cpufreq dir there
>> #cat /proc/acpi/processor/CPU0/throttling
>> <not supported>
>>
>> acpidumps attached
>>
>>
>> Thanks
>> Pete
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
