public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randall Nortman <linuxkernellist@wonderclown.com>
To: linux-kernel@vger.kernel.org
Cc: Tony Lindgren <tony@atomide.com>
Subject: Re: MSI K8N Neo + powernow-k8: ACPI info is worse than BIOS PST
Date: Mon, 2 Aug 2004 06:46:56 -0500	[thread overview]
Message-ID: <20040802114655.GD18254@li2-47.members.linode.com> (raw)
In-Reply-To: <20040802100658.GC10412@atomide.com>

On Mon, Aug 02, 2004 at 03:07:01AM -0700, Tony Lindgren wrote:
> * Randall Nortman <linuxkernellist@wonderclown.com> [040731 07:01]:
> > 
> > If anybody qualified to hack this code is interested in creating a
> > real workaround for BIOSes like this, I offer my system (and my time,
> > as I cannot give remote access) for testing.  I would suggest adding a
> > compile-time or load-time option to prefer the BIOS over ACPI (as in
> > powernow-k7, I think), and maybe a compile-time option to use Tony's
> > hardcoded tables.
> 
> Just to clarify a bit, my patch only uses the 800MHz hardcoded, which
> should work on all AMD64 processors. The max value used is the current
> running value.


Actually, thanks to an off-list response from Anton Ertl (anton at
mips dot complang dot tuwien dot ac dot at), I have made an important
discovery that's relevant to my situation and your patch: newer amd64
cores (Newcastle cores) cannot clock down to 800MHz!  I apparently am
lucky enough to have gotten the CG stepping of my CPU, which supports
1000, 1800, and 2000MHz modes, exactly as reported by the BIOS.  I
have therefore backed out your patch, and the result is that my system
is actually snappier.  (I suspect that really weird things were
happening when cpufreq tried to clock down to 800MHz; I was getting
high CPU load, periodic temporary freezes, and audio glitches, all of
which went away when I set the minimum clock to 1000MHz.  I hope I
didn't do any permanent damage.)  These new cores actually consume
less power at 1000MHz than the old ones did at 800MHz, so it's a
win-win for the lucky ones like me.

Now that I see that my BIOS table was correct after all, I'm left
wondering why MSI would have gotten that right but the ACPI wrong,
since Windows uses the ACPI information afaik.  And that leads me to
suspect that perhaps the bug is in the powernow-k8 ACPI code rather
than my firmware.  Any thoughts?

Randall Nortman

  reply	other threads:[~2004-08-02 11:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-31 14:00 MSI K8N Neo + powernow-k8: ACPI info is worse than BIOS PST Randall Nortman
2004-08-02 10:07 ` Tony Lindgren
2004-08-02 11:46   ` Randall Nortman [this message]
2004-08-02 12:43     ` Tony Lindgren
     [not found] <2o2IK-8gu-7@gated-at.bofh.it>
     [not found] ` <2oI5h-3A8-7@gated-at.bofh.it>
2004-08-02 12:49   ` Andi Kleen
2004-08-02 17:34     ` Tony Lindgren

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=20040802114655.GD18254@li2-47.members.linode.com \
    --to=linuxkernellist@wonderclown.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony@atomide.com \
    /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