From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9636] cpufreq reports too low max freq on Intel P4
Date: Wed, 26 Dec 2007 04:39:09 -0800 (PST) [thread overview]
Message-ID: <20071226123909.F2C38108010@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-9636-3570@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=9636
------- Comment #2 from peter.ganzhorn@googlemail.com 2007-12-26 04:39 -------
BTW: I'm using the ondemand-governor and acpi-cpufreq as driver:
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
acpi-cpufreq
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
ondemand
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-12-26 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-26 12:34 [Bug 9636] New: cpufreq reports too low max freq on Intel P4 bugme-daemon
2007-12-26 12:35 ` [Bug 9636] " bugme-daemon
2007-12-26 12:39 ` bugme-daemon [this message]
2008-01-01 18:15 ` bugme-daemon
2008-01-27 11:20 ` bugme-daemon
2008-01-27 11:21 ` bugme-daemon
2008-03-02 19:44 ` bugme-daemon
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=20071226123909.F2C38108010@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.kernel.org \
--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