From: Len Brown <len.brown@intel.com>
To: paul.devriendt@amd.com, Marc Singer <elf@buici.com>
Cc: linux@dominikbrodowski.de,
"cpufreq@www.linux.org.uk" <cpufreq@www.linux.org.uk>
Subject: RE: Athlon 64 complains of frequency mismatch
Date: 23 Jun 2004 13:52:55 -0400 [thread overview]
Message-ID: <1088013174.4319.302.camel@dhcppc4> (raw)
In-Reply-To: <84EA05E2CA77634C82730353CBE3A8432698C4@SAUSEXMB1.amd.com>
On Wed, 2004-06-23 at 03:43, paul.devriendt@amd.com wrote:
> I am of the opinion that this is a bug in the ACPI subsystem.
> The BIOS developers find it easy to always have the space
> allocated for their tables. They "hide" them by tricks
> such as changing _PSS to XPSS.
Feel free to file an ACPI bug here and I'll be happy to look into it:
http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
Component: power-processor
It should describe the behaviour of the two configurations
A. Cool&Quiet enabled in BIOS
B. Cool & Quiet disabled in BIOS
and what is unexpected.
It should include the output from acpidmp taken in each configuration.
acpidmp is available in /usr/sbin/, or in pmtools:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
Only with this can we tell what curve ball the BIOS is throwing.
thanks,
-Len
next prev parent reply other threads:[~2004-06-23 17:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 7:43 Athlon 64 complains of frequency mismatch paul.devriendt
2004-06-23 17:52 ` Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 8:07 paul.devriendt
2004-06-23 7:43 paul.devriendt
2004-06-23 7:54 ` Marc Singer
2004-06-22 15:28 paul.devriendt
2004-06-22 15:26 paul.devriendt
2004-06-22 16:07 ` Marc Singer
2004-06-22 17:07 ` Dominik Brodowski
2004-06-22 6:02 paul.devriendt
2004-06-22 7:30 ` Arjan van de Ven
2004-06-22 10:28 ` Andi Kleen
2004-06-22 15:16 ` Marc Singer
2004-06-18 18:51 Marc Singer
2004-06-19 10:44 ` Dominik Brodowski
2004-06-19 15:55 ` Marc Singer
2004-06-19 16:36 ` Marc Singer
2004-06-21 20:26 ` Dominik Brodowski
2004-06-21 21:42 ` Marc Singer
2004-06-22 17:11 ` Dominik Brodowski
2004-06-22 17:59 ` Marc Singer
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=1088013174.4319.302.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=cpufreq@www.linux.org.uk \
--cc=elf@buici.com \
--cc=linux@dominikbrodowski.de \
--cc=paul.devriendt@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.