public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Tim Phipps <tim@phipps-hutton.freeserve.co.uk>
Cc: linux-kernel@vger.kernel.org, Edgar Toernig <froese@gmx.de>,
	Dave Jones <davej@redhat.com>
Subject: Re: p4-clockmod not working in 2.6.16
Date: Wed, 05 Apr 2006 15:59:36 +0200	[thread overview]
Message-ID: <1144245577.7571.16.camel@homer> (raw)
In-Reply-To: <1144245205.7571.11.camel@homer>

On Wed, 2006-04-05 at 13:02 +0100, Tim Phipps wrote:
> On Tuesday 04 Apr 2006 11:47, Tim Phipps wrote:
> > On Wed, 2006-03-22 at 06:20, Mike Galbraith wrote:
> > > On Wed, 2006-03-22 at 06:57 +0100, Edgar Toernig wrote:
> > > > | 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.
> >
> Here's a patch to 2.6.17-rc1 that disables the 12.5% DC on any CPU that has 
> N60. The frequencies in the errata are a bit vague so this is the safe bet 
> and it only disables one of the eight frequencies rather than the current 
> behaviour which disables all of mine!

Works for me.  Perhaps you should update...
dprintk("has errata -- disabling frequencies lower than 2ghz\n");
...,slap a Signed-off-by: on it and see if it flys.

	-Mike

P.S.  server can't find computer.systems.pipex.net: NXDOMAIN


  parent reply	other threads:[~2006-04-05 13:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21 20:55 p4-clockmod not working in 2.6.16 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
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 [this message]
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=1144245577.7571.16.camel@homer \
    --to=efault@gmx.de \
    --cc=davej@redhat.com \
    --cc=froese@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim@phipps-hutton.freeserve.co.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