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 08:55:54 -0700 [thread overview]
Message-ID: <20040619155554.GA32432@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?
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.
next prev parent reply other threads:[~2004-06-19 15:55 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 [this message]
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
-- 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=20040619155554.GA32432@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 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.