From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 10653] New: p4-clockmod gets a wrong max clock (1.2GHz insted 1.6GHz)
Date: Thu, 8 May 2008 18:10:17 -0700 (PDT) [thread overview]
Message-ID: <bug-10653-3570@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=10653
Summary: p4-clockmod gets a wrong max clock (1.2GHz insted
1.6GHz)
Product: Power Management
Version: 2.5
KernelVersion: 2.6.25
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@www.linux.org.uk
ReportedBy: andrea.cimitan@gmail.com
Latest working kernel version: I don't know
Hardware Environment: P4 1.6 GHz
Problem Description:
My p4 1.6GHz gets a wrong max speed using p4-clockmod.
Available frequencies taken from cpufreq-info (same output for cat
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies).
Using acpi-cpufreq:
1.20 GHz, 1.60GHz
using p4-clockmod:
150 MHz, 300 MHz, 450 MHz, 600 MHz, 750 MHz, 900 MHz, 1.05 GHz, 1.20 GHz
I'm forced to use acpi-cpufreq :).
Useful cpuinfo for model and stepping:
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Pentium(R) 4 Mobile CPU 1.60GHz
stepping : 4
cpu MHz : 1200.000
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm up pebs bts
bogomips : 2395.99
clflush size : 64
--
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 reply other threads:[~2008-05-09 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 1:10 bugme-daemon [this message]
2008-05-09 1:18 ` [Bug 10653] p4-clockmod gets a wrong max clock (1.2GHz insted 1.6GHz) bugme-daemon
2008-05-11 16:21 ` bugme-daemon
2008-05-11 17:21 ` bugme-daemon
2008-05-11 17:35 ` bugme-daemon
2008-05-11 19:30 ` bugme-daemon
2008-05-15 17:20 ` 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=bug-10653-3570@http.bugzilla.kernel.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