From: Philip Lawatsch <philip@lawatsch.at>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: JimD <Jim@keeliegirl.dyndns.org>, linux-kernel@vger.kernel.org
Subject: Re: AMD64 overclock issue with 2.6.16 but not with 2.6.15
Date: Thu, 30 Mar 2006 16:32:13 +0200 [thread overview]
Message-ID: <442BEBED.8080205@lawatsch.at> (raw)
In-Reply-To: <200603292054.09385.s0348365@sms.ed.ac.uk>
Alistair John Strachan wrote:
> On Wednesday 29 March 2006 20:35, JimD wrote:
>> Do any one know of any other issues with amd64 and the
>> 2.6.16 series? I have run into a weird issue.
> [snip]
>> The bogomips are showing the same though the kernel is not reporting
>> the correct MHz. If I reboot and check the BIOS, the correct MHz is
>> reported. I have not run any CPU benchmarks to see if performance is
>> really going back down to 2000 MHz.
>>
>> Does anyone have a clue what could be causing this?
>
> At a guess, it sounds like you're trying to use cpufreq on an overclocked CPU,
> a definitely no-no. Check your config for this option, remove it if desired.
Why is this a nono? I've been using that for quite a while without
problems. It seems that even though I overclocked it the system is
stable at all voltage / frequency steps. (I only modified the reference
clock and not the core voltages)
Also, 2.16 only shows a wrong value, the cpu is clocked at the "correct"
(overclocked) frequency, at least the bogomips value matches what I'm
expecting.
kind regards Philip
prev parent reply other threads:[~2006-03-30 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 19:35 JimD
2006-03-29 19:54 ` Alistair John Strachan
2006-03-29 20:12 ` JimD
2006-03-30 14:32 ` Philip Lawatsch [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=442BEBED.8080205@lawatsch.at \
--to=philip@lawatsch.at \
--cc=Jim@keeliegirl.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.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
all inboxes | Powered by JetHome®