linux-kernel - Re: [PATCH v2] acpi: Fix regression where _PPC is not read at boot even when ignore

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 29 Apr 2009 14:43:12 -0700
From:	"Darrick J. Wong" <djwong@...ibm.com>
To:	Thomas Renninger <trenn@...e.de>
Cc:	Ingo Molnar <mingo@...e.hu>, 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 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.

--D
--
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/