All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Unger <chakkerz@gmail.com>
To: cpufreq@lists.linux.org.uk
Subject: Re: [Bug 7866] New: cpufreq fails to correctly identify Intel Conroe	operating frequencies
Date: Sun, 11 Feb 2007 01:59:10 +0000 (UTC)	[thread overview]
Message-ID: <loom.20070211T025410-718@post.gmane.org> (raw)
In-Reply-To: 200701230813.l0N8Dtuj027723@fire-2.osdl.org

>            Summary: cpufreq fails to correctly identify Intel Conroe
>                     operating frequencies
> Intel Conroe E6660  <at>  2.4ghz
> 
> cat /proc/cpuinfo 
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 15
> model name      : Intel(R) Core(TM)2 CPU          6600   <at>  2.40GHz
> stepping        : 6
> cpu MHz         : 600.000
> cache size      : 4096 KB
> physical id     : 0
> siblings        : 2
> core id         : 0
> cpu cores       : 2
> 


Hello there

different hardware here:
MOBO GA-965P-DS3
uname -a :
Linux swamp-monkey 2.6.19-gentoo-r4 #1 SMP Sat Dec 30 10:42:07 UTC 2006 x86_64
Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz GenuineIntel GNU/Linux

chakkerz@swamp-monkey ~ $ cat /etc/sabayon-release
Sabayon Linux x86-64 3.25


Exactly the same symptom:

Workaround: Disable EIST in the BIOS - causes CPU to run at full speed.
Testing in Windows XP with Intel Thermal Analysis Tool indicates that although
the CPU Frequency remains up, power is still cut to the CPU, causing the CPU
temperature to drop.

NOTE: my CPU is overclocked. (which makes this a really ironic bug)

Also: Although my kernel is an older revision, it contains 2.6.20 backports.

      reply	other threads:[~2007-02-11  1:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23  8:13 [Bug 7866] New: cpufreq fails to correctly identify Intel Conroe operating frequencies bugme-daemon
2007-02-11  1:59 ` Christian Unger [this message]

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=loom.20070211T025410-718@post.gmane.org \
    --to=chakkerz@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.