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: Sat, 19 Jun 2004 09:36:31 -0700	[thread overview]
Message-ID: <20040619163631.GA1369@buici.com> (raw)
In-Reply-To: <20040619104456.GA7689@dominikbrodowski.de>

On Sat, Jun 19, 2004 at 12:44:56PM +0200, Dominik Brodowski wrote:
> Hi,
> 
> It looks like there's either a problem in the ACPI tables. So I'd like to
> dump the relevant parts of the ACPI tables -- so, please, 
> could you put this file
> 
> http://www.brodo.de/patches/2004-04-06/cpufreq-acpi_pdump.c
> 
> into the directory [assuming you're running a 64bit kernel]
> 
> arch/x86_64/kernel/cpufreq/ in the linux kernel sources,
> add the line
> 
> obj-m += cpufreq-acpi_pdump.o
> 
> to the file "Makefile" in this directory,
> 
> re-build the kernel and modules, and then 
> 
> modprobe cpufreq-acpi_pdump
> 
> and send the dmesg to me?
> 
> Thanks,
> 	Dominik

It complains of a device not being present and leaves this in the
dmesg log:


number of states: 10
acpi_pdump: P0: 161061273 MHz, 629145 mW, 10066329 uS s:0x99999999 c:0x99999999
acpi_pdump: P1: 161061273 MHz, 629145 mW, 10066329 uS s:0x99999999 c:0x99999999
acpi_pdump: P2: 161061273 MHz, 629145 mW, 10066329 uS s:0x99999999 c:0x99999999
acpi_pdump: P3: 161061273 MHz, 629145 mW, 10066329 uS s:0x99999999 c:0x99999999
acpi_pdump: P4: 161061273 MHz, 629145 mW, 10066329 uS s:0x99999999 c:0x99999999
acpi_pdump: P5: 161061273 MHz, 629145 mW, 10066329 uS s:0x99999999 c:0x99999999
acpi_pdump: P6: 161061273 MHz, 629145 mW, 10066329 uS s:0x99999999 c:0x99999999
acpi_pdump: P7: 161061273 MHz, 629145 mW, 10066329 uS s:0x99999999 c:0x99999999
acpi_pdump: P8: 161061273 MHz, 629145 mW, 10066329 uS s:0x99999999 c:0x99999999
acpi_pdump: P9: 161061273 MHz, 629145 mW, 10066329 uS s:0x99999999 c:0x99999999
control_register:
130 12 127 0 0 0 0
status_register:
130 12 127 0 0 0 0

Is this really helpful?

  parent reply	other threads:[~2004-06-19 16:36 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 [this message]
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
  -- 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=20040619163631.GA1369@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