From: Daniel Drake <dsd@gentoo.org>
To: cpufreq@lists.linux.org.uk
Cc: zwane@commfireservices.com
Subject: p4-clockmod reports frequencies faster than CPU
Date: Mon, 21 Aug 2006 17:11:11 +0100 [thread overview]
Message-ID: <44E9DB1F.2020405@gentoo.org> (raw)
Hi,
A Gentoo user at http://bugs.gentoo.org/141234 reports that the
p4-clockmod cpufreq driver reports bad frequencies for his 1300mhz
Pentium 4 processor:
# cat sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
525000 787500 1050000 1312500 1575000 1837500 2100000
The last 3 are obviously wrong.
Unfortunately as this is a production system it's not easy to test other
kernels, so this has only been reproduced on a Gentoo-patched 2.6.16.
However the Gentoo patches don't modify cpufreq at all and are generally
quite minimal.
/proc/cpuinfo output is here:
http://bugs.gentoo.org/attachment.cgi?id=92370&action=view
Does any more info need to be provided?
Thanks,
Daniel
next reply other threads:[~2006-08-21 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 16:11 Daniel Drake [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-22 1:58 p4-clockmod reports frequencies faster than CPU Pallipadi, Venkatesh
2006-10-02 1:45 ` Dominik Brodowski
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=44E9DB1F.2020405@gentoo.org \
--to=dsd@gentoo.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=zwane@commfireservices.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox