From: Hakan BAYINDIR <hakan@bayindir.org>
To: cpufreq@lists.linux.org.uk
Subject: Q6600 CPU Frequency Scaling Problem / Bug
Date: Mon, 30 Jun 2008 22:50:50 +0300 [thread overview]
Message-ID: <4869391A.9010006@bayindir.org> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1111 bytes --]
Hi,
I'm running Debian testing on an Intel Core2Quad Q6600 with 4GB DDR2 RAM
on a MSI P35 Platinum board since December 07. When I first migrated my
system on December (I've installed Debian as etch beta1 and upgrading
since), every core of the CPU was scaling their frequency independently.
After installing 2.6.22, The cores started to scale in a synchronized
way. I.e. when a core needs to speed-up, every core speeds up in sync.
The weird thing is, I have another clone of this OS at my office running
on a core 2 duo processor and that system scaled its processors
independently.
The ganged scaling behavior is also consistent with the
/sys/devices/system/cpuX/cpufreq/affected_cpus file and cpufreq-info
command. Both of them shows that all CPU's speeds are need to be in sync
while there's really no need. Also Ubuntu 8.04 Live CD exhibits the same
behavior and this behavior can be verified under sysfs again.
Is it a bug? Is it expected? I can provide more information if it's
needed. I'm attaching cpufreq-info's output as a reference.
Cheers and Regards,
-- Hakan.
[-- Attachment #1.1.2: cpufreq-info.out.txt --]
[-- Type: text/plain, Size: 2169 bytes --]
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to linux@brodo.de, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0 1 2 3
hardware limits: 1.60 GHz - 2.40 GHz
available frequency steps: 2.40 GHz, 2.14 GHz, 1.87 GHz, 1.60 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance
current policy: frequency should be within 1.60 GHz and 2.40 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0 1 2 3
hardware limits: 1.60 GHz - 2.40 GHz
available frequency steps: 2.40 GHz, 2.14 GHz, 1.87 GHz, 1.60 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance
current policy: frequency should be within 1.60 GHz and 2.40 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
analyzing CPU 2:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0 1 2 3
hardware limits: 1.60 GHz - 2.40 GHz
available frequency steps: 2.40 GHz, 2.14 GHz, 1.87 GHz, 1.60 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance
current policy: frequency should be within 1.60 GHz and 2.40 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
analyzing CPU 3:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0 1 2 3
hardware limits: 1.60 GHz - 2.40 GHz
available frequency steps: 2.40 GHz, 2.14 GHz, 1.87 GHz, 1.60 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance
current policy: frequency should be within 1.60 GHz and 2.40 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
[-- Attachment #2: Type: text/plain, Size: 147 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq
next reply other threads:[~2008-06-30 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 19:50 Hakan BAYINDIR [this message]
2008-06-30 20:21 ` Q6600 CPU Frequency Scaling Problem / Bug Pallipadi, Venkatesh
2008-06-30 20:33 ` Hakan BAYINDIR
2008-06-30 21:07 ` Pallipadi, Venkatesh
2008-06-30 21:19 ` Hakan BAYINDIR
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=4869391A.9010006@bayindir.org \
--to=hakan@bayindir.org \
--cc=cpufreq@lists.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;
as well as URLs for NNTP newsgroup(s).