From: "Inter filmati" <interfc@jumpy.it>
To: <linux-kernel@vger.kernel.org>
Subject: Re: cpufreq/powernowd limiting CPU frequency on kernels >=2.6.16
Date: Thu, 26 Oct 2006 19:59:41 +0200 [thread overview]
Message-ID: <001201c6f928$89c9a720$2b20ff27@flaviopc> (raw)
In-Reply-To: <20061026174153.GB18076@amd64.of.nowhere>
----- Original Message -----
From: <thunder7@xs4all.nl>
To: "Inter filmati" <interfc@jumpy.it>
Cc: <linux-kernel@vger.kernel.org>
Sent: Thursday, October 26, 2006 7:41 PM
Subject: Re: cpufreq/powernowd limiting CPU frequency on kernels >=2.6.16
> Which means that my X2 4600+ works just fine, but after overclocking
> cpufreq restores it to the FSB that it should run on.
>
> If you care about that changed, try to find out what patch caused this,
> but in general, there's no support for overclocking in the kernel, and
> bugreports from overclocked systems are frowned upon.
>
It would be kind to find out why the problem seems to show only from 2.6.16
and not before, unfortunately I ain't so skilled to investigate into cpufreq
source.
---
Flavio
www.flapane.com
next prev parent reply other threads:[~2006-10-26 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 17:08 Inter filmati
2006-10-26 17:41 ` thunder7
2006-10-26 17:59 ` Inter filmati [this message]
2006-10-26 19:01 ` thunder7
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='001201c6f928$89c9a720$2b20ff27@flaviopc' \
--to=interfc@jumpy.it \
--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
all inboxes | Powered by JetHome®