From: Edgar Toernig <froese@gmx.de>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: p4-clockmod not working in 2.6.16
Date: Wed, 22 Mar 2006 06:57:14 +0100 [thread overview]
Message-ID: <20060322065714.169ce224.froese@gmx.de> (raw)
In-Reply-To: <20060321220115.GA8583@redhat.com>
Dave Jones wrote:
>
> Fix the code to disable freqs less than 2GHz in N60 errata.
>
> - else if (has_N60_errata[policy->cpu] && p4clockmod_table[i].frequency < 2000000)
> + else if (has_N60_errata[policy->cpu] && ((stock_freq * i)/8) < 2000000)
Doesn't change anything here - I still get _all_ frequencies where I think
I shouldn't:
| processor : 0
| vendor_id : GenuineIntel
| cpu family : 15
| model : 2
| model name : Intel(R) Pentium(R) 4 CPU 3.00GHz
| stepping : 9
| cpu MHz : 3000.000
[same for cpu 1, it's a single P4 with HT]
Looks like the f29 cpu that should have the errata.
| > cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_available_frequencies
| 375000 750000 1125000 1500000 1875000 2250000 2625000 3000000
| > dmesg|fgrep clockmod
| p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available
Further: the directory cpufreq in /sys is there only for cpu1 - not for cpu0:
| > ls /sys/devices/system/cpu/cpu?
| /sys/devices/system/cpu/cpu0:
| topology
|
| /sys/devices/system/cpu/cpu1:
| cpufreq topology
And at last: reading Intel's errata it should be good enough to not go
below 25% instead limiting all below 2GHz. I'm not even sure whether
the 2GHz mentioned there is the reduced or the nominal clock. Running
2GHz on 12.5% would be a really fast CPU.
| N60. Processor May Hang under Certain Frequencies and 12.5%
| STPCLK# Duty Cycle
|
| Problem: If a system de-asserts STPCLK# at a 12.5% duty cycle, the
| processor is running below 2 GHz, and the processor thermal
| control circuit (TCC) on-demand clock modulation is active,
| the processor may hang. This erratum does not occur under
| the automatic mode of the TCC.
|
| Implication: When this erratum occurs, the processor will hang.
|
| Workaround: If use of the on-demand mode of the processor's TCC is desired
| in conjunction with STPCLK# modulation, then assure that STPCLK#
| is not asserted at a 12.5% duty cycle.
Ciao, ET.
next prev parent reply other threads:[~2006-03-22 5:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 20:55 Sasa Ostrouska
2006-03-21 21:01 ` Dave Jones
2006-03-21 21:57 ` Sasa Ostrouska
2006-03-21 21:59 ` Arjan van de Ven
2006-03-21 22:52 ` Sasa Ostrouska
2006-03-21 22:01 ` Dave Jones
2006-03-21 22:08 ` Sasa Ostrouska
2006-03-21 22:13 ` Sasa Ostrouska
2006-03-21 22:20 ` Dave Jones
2006-03-21 22:51 ` Sasa Ostrouska
2006-03-22 5:57 ` Edgar Toernig [this message]
2006-03-22 6:20 ` Mike Galbraith
[not found] ` <1144147663.2588.247.camel@elsdt-scarecrow.arc.com>
2006-04-05 12:02 ` Tim Phipps
[not found] ` <1144245205.7571.11.camel@homer>
2006-04-05 13:59 ` Mike Galbraith
2006-04-13 12:20 ` Tim Phipps
2006-04-13 12:42 ` Jesper Juhl
2006-04-13 13:59 ` [PATCH 001/001] cpufreq: p4_clockmod errata N60 handling is over zealous Tim Phipps
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=20060322065714.169ce224.froese@gmx.de \
--to=froese@gmx.de \
--cc=davej@redhat.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
Powered by JetHome