From: Jarek Poplawski <jarkao2@o2.pl>
To: Krzysztof Oledzki <olel@ans.pl>
Cc: linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk
Subject: Re: 3.2GHz cpus with cpufreq become 2.8GHz
Date: Fri, 20 Oct 2006 09:37:52 +0200 [thread overview]
Message-ID: <20061020073752.GC1898@ff.dom.local> (raw)
In-Reply-To: <Pine.LNX.4.64.0610200022320.30089@bizon.gios.gov.pl>
On 20-10-2006 00:25, Krzysztof Oledzki wrote:
...
> I will check this, thank you. BTW: what wrong is with p4-clockmod? I was
> not able to find any information that it is broken and should not be used?
At least it is very suspected:
"Subject: Hardware bug or kernel bug?
On Mon, Oct 16, 2006 at 03:32:38PM +0100, David Johnson wrote:
..
> I've found the culprit - CPU Frequency Scaling.
> With it enabled I get the reboots, with it disabled I don't. That's the same
> with every kernel version I've tried (2.6.19-rc1+rc2, 2.6.17.13 & Centos'
> 2.6.9) The system was using the p4-clockmod driver and the ondemand governor.
> I'm still not sure exactly what the problem is - the reboots only happen in
> the circumstances I've mentioned and are not triggered by changes in clock
> speed alone - but disabling cpufreq seems to make it go away... "
Cheers,
Jarek P.
next prev parent reply other threads:[~2006-10-20 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 19:43 3.2GHz cpus with cpufreq become 2.8GHz Krzysztof Oledzki
[not found] ` <4537A582.4020406@felter.org>
2006-10-19 22:25 ` Krzysztof Oledzki
2006-10-20 7:37 ` Jarek Poplawski [this message]
[not found] ` <453800C1.8050409@felter.org>
2006-10-23 13:53 ` Krzysztof Oledzki
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=20061020073752.GC1898@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=cpufreq@lists.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=olel@ans.pl \
/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