[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200904301107.45753.trenn@suse.de>
Date: Thu, 30 Apr 2009 11:07:45 +0200
From: Thomas Renninger <trenn@...e.de>
To: djwong@...ibm.com, Ingo Molnar <mingo@...e.hu>
Cc: Len Brown <lenb@...nel.org>, Matthew Garrett <mjg59@...f.ucam.org>,
"linux-kernel" <linux-kernel@...r.kernel.org>,
cpufreq@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: [PATCH v2] acpi: Fix regression where _PPC is not read at boot even when ignore_ppc=0
On Wednesday 29 April 2009 11:43:12 pm Darrick J. Wong wrote:
> On Wed, Apr 29, 2009 at 03:19:28PM +0200, Thomas Renninger wrote:
> > Ingo, did you do a BIOS update in between?
> > The DSDT and SSDTs you added do not contain a _PPC function.
> > These ACPI tables definitely do not suffer from an initial _PPC
> > evaluation.
>
> P-state tables are probably loaded from separate SSDT tables "CPU0IST" and
> "CPU1IST". You can download 'em with something like this:
>
> # dmesg | grep IST
> ACPI: SSDT BFD30566, 01FB (r1 PmRef CPU0IST 3000 INTL 20030224)
> ^addr ^length
>
> # acpidump --addr 0xBFD30566 --length 0x1FB > cpu0ist
> # iasl -d cpu0ist
>
> Then paste cpu0ist.dsl somewhere.
Oops forgot about the tables loaded at runtime, I take back the definitely :)
Ingo, can you also do:
acpidump --addr 0x7F6E609E --length 0x1ED >cpu0ist
acpidump --addr 0x7F6E628B --length 0x94 >cpu1ist
acpidump --addr 0x7F6E5DE1 --length 0x238 >cpu0cst
acpidump --addr 0x7F6E6019 --length 0x85 >cpu1cst
Then we should finally have all ACPI bits of such an affected system together.
The addresses and table lengths should work for your T60 and can be found in
the SSDT2:
Name (SSDT, Package (0x0C)
{
"CPU0IST ",
0x7F6E609E,
0x000001ED,
"CPU1IST ",
0x7F6E628B,
0x00000094,
"CPU0CST ",
0x7F6E5DE1,
0x00000238,
"CPU1CST ",
0x7F6E6019,
0x00000085
})
Thanks,
Thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists