public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: linux-kernel@vger.kernel.org
Subject: acpi_cpufreq on Intel(R) Core(TM)2 Quad CPU  Q6600  @ 2.40GHz problem (3.[4-9].X)
Date: Wed, 8 May 2013 15:21:25 +0200	[thread overview]
Message-ID: <20130508152125.f48b7b55.skraw@ithnet.com> (raw)

Hello all,

I see some kind of bug with acpi_cpufreq on Intels Q6600 cpus. If you load the
module you see this in proc:

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz
stepping        : 11
cpu MHz         : 600.000
cache size      : 4096 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 4
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor
ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm tpr_shadow vnmi
flexpriority bogomips        : 4800.22 clflush size    : 64 cache_alignment :
64 address sizes   : 36 bits physical, 48 bits virtual power management:

(repeated for other cores)

As you can see cpu MHz shows 600. Now take a look at cpufreq-info output and
see:

hardware limits: 600 MHz - 900 MHz

Obviously this is wrong, I don't know what the minimum should be, but the max
should be 2.40 GHz. If you stress the cpu you will notice MHz go up to 900,
but that's it. I have several such boxes, and all act the same with all
kernels I tried so far (3.4.X, 3.8.X, 3.9.X).
If you unload acpi_cpufreq you see the correct values. To me seems to be no
display problem. The box "feels" slower when the module is loaded.
With a cpu type Q9300 btw everything works as expected.
If there are ideas or patches to test how to remove this problem, feel free to
mail/cc me. I can check out whatever looks promising.

-- 
Regards,
Stephan

                 reply	other threads:[~2013-05-08 13:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20130508152125.f48b7b55.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=linux-kernel@vger.kernel.org \
    /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