From: Thomas Renninger <trenn@suse.de>
To: djwong@us.ibm.com, Ingo Molnar <mingo@elte.hu>
Cc: Len Brown <lenb@kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
cpufreq@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2] acpi: Fix regression where _PPC is not read at boot even when ignore_ppc=0
Date: Thu, 30 Apr 2009 11:07:45 +0200 [thread overview]
Message-ID: <200904301107.45753.trenn@suse.de> (raw)
In-Reply-To: <20090429214312.GX7917@plum>
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
next prev parent reply other threads:[~2009-04-30 9:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 22:53 [PATCH] acpi: Fix regression where _PPC is not read at boot even when ignore_ppc=0 Darrick J. Wong
2009-04-16 0:27 ` [PATCH v2] " Darrick J. Wong
2009-04-16 10:01 ` Thomas Renninger
2009-04-16 10:32 ` Ingo Molnar
2009-04-16 17:42 ` Darrick J. Wong
2009-04-16 18:49 ` Thomas Renninger
2009-04-16 22:45 ` Matthew Garrett
2009-04-20 5:13 ` Len Brown
2009-04-20 9:13 ` Thomas Renninger
2009-04-20 10:45 ` Ingo Molnar
2009-04-29 13:19 ` Thomas Renninger
2009-04-29 14:48 ` Ingo Molnar
2009-04-29 21:43 ` Darrick J. Wong
2009-04-30 9:07 ` Thomas Renninger [this message]
2009-04-30 9:17 ` Ingo Molnar
2009-04-20 22:18 ` Henrique de Moraes Holschuh
2009-04-28 19:33 ` Darrick J. Wong
2009-04-28 19:53 ` Matthew Garrett
2009-04-28 20:24 ` Darrick J. Wong
2009-04-29 21:39 ` Darrick J. Wong
2009-04-29 22:00 ` Matthew Garrett
2009-04-30 7:25 ` Ingo Molnar
2009-04-30 9:54 ` Matthew Garrett
2009-04-30 11:10 ` Ingo Molnar
2009-04-30 11:13 ` Matthew Garrett
2009-05-15 19:12 ` Darrick J. Wong
2009-06-02 23:21 ` Darrick J. Wong
2009-06-07 10:05 ` Ingo Molnar
2009-07-15 0:32 ` Darrick J. Wong
2010-02-16 22:07 ` Matthew Garrett
2010-02-16 22:26 ` Darrick J. Wong
2010-02-18 9:02 ` Len Brown
2010-02-18 18:28 ` Darrick J. Wong
2010-02-19 6:12 ` Len Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200904301107.45753.trenn@suse.de \
--to=trenn@suse.de \
--cc=cpufreq@vger.kernel.org \
--cc=djwong@us.ibm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).