cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Singer <elf@buici.com>
To: cpufreq@www.linux.org.uk
Subject: Re: Athlon 64 complains of frequency mismatch
Date: Mon, 21 Jun 2004 14:42:36 -0700	[thread overview]
Message-ID: <20040621214236.GA3858@buici.com> (raw)
In-Reply-To: <20040621202601.GA8064@dominikbrodowski.de>

On Mon, Jun 21, 2004 at 10:26:01PM +0200, Dominik Brodowski wrote:
> > Is this really helpful?
> Partly. It shows the values received by the powernow-k8 driver are
> _completely_ bogus. A standard questions: have you tried a BIOS update?

I looked for one.  I downloaded a BIOS, though I'm not sure it is
newer than the one installed.  The release notes make no mention of
powernow or acpi.

> > On rumination, I came to a similar conclusion.  I can do as you ask.
> > Is this the same as grabbing the dsdt from the /proc/acpi interface
> > and running it through Intel's decompiler?  That's where I've started
> > to go.
> 
> Not really -- acpi_pdump dumps what's received by the powernow-k8 driver
> from the ACPI subsystem, while decompiling /proc/acpi/dsdt prints out what's
> really there in the ACPI tables. In your case, it might indeed be
> interesting whether a more appropriate P-States part of the DSDT is
> contained somewhere, which is not initialized properly. Could you
> disassemble the DSDT, please, and check for _PSS entries (grep -20 _PSS)?
> 

I did fetch it.  There are no entries for _PSS or even PSS.

> Thanks,
> 	Dominik

  reply	other threads:[~2004-06-21 21:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 18:51 Athlon 64 complains of frequency mismatch 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 [this message]
2004-06-22 17:11         ` Dominik Brodowski
2004-06-22 17:59           ` Marc Singer
  -- strict thread matches above, loose matches on Subject: below --
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-22 15:26 paul.devriendt
2004-06-22 16:07 ` Marc Singer
2004-06-22 17:07   ` Dominik Brodowski
2004-06-22 15:28 paul.devriendt
2004-06-23  7:43 paul.devriendt
2004-06-23 17:52 ` Len Brown
2004-06-23  7:43 paul.devriendt
2004-06-23  7:54 ` Marc Singer
2004-06-23  8:07 paul.devriendt

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=20040621214236.GA3858@buici.com \
    --to=elf@buici.com \
    --cc=cpufreq@www.linux.org.uk \
    /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