mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: High pitch noise when ACPI processor module is loaded.
Date: Mon, 25 Jan 2010 07:41:25 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1001250738220.9341@p34.internal.lan> (raw)
In-Reply-To: <20100125123311.GC3182@khazad-dum.debian.net>



On Mon, 25 Jan 2010, Henrique de Moraes Holschuh wrote:

> On Mon, 25 Jan 2010, Justin Piszcz wrote:
>> So the question remains, is it possible to utilize turbo boost (in Linux)
>> without the high pitch noise from the ACPI processor module?
>
> Well, I am tempted to say you should consider getting a higher quality
> motherboard (or, if it is just yours that sing, get it replaced on warranty
> as that would mean you got one with bad components).
>
> That said, if Windows can get that motherboard to shut up, so should Linux.
> You just need to find the right knob to push that will make the power draw
> behaviour more like whatever Windows is doing.
>
> The first good bet is to limit core C-state depth, e.g, to C3 (instead of
> C5/C6), and if thet doesn't work, to C2.  After that, you can try limiting
> package C-states if your BIOS will let you (I don't know if we can do that
> distinction in Linux right now... do we?), play with cpufreq limiting the
> core frequency changes, etc.
>
> And of course, try all scheduler frequencies, with and without NO_HZ.
>
> What motherboard is this?
Intel's DP55KG Extreme motherboard, yes I will try changing the c-state 
later and hopefully that will fix the problem, thanks.  Again, the board 
never makes any noise in the BIOS or Windows or Linux, only when you load 
the cpufreq-processor module.

Justin.

      reply	other threads:[~2010-01-25 12:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-23 15:48 Justin Piszcz
2010-01-23 20:12 ` Rafael J. Wysocki
2010-01-23 20:42   ` Robert Hancock
2010-01-25  5:34 ` Valdis.Kletnieks
2010-01-25  9:26   ` Justin Piszcz
2010-01-25  9:56     ` Justin Piszcz
2010-01-25 10:10     ` Ian Campbell
2010-01-25 20:46       ` Justin Piszcz
2010-01-25 22:38         ` Sitsofe Wheeler
2010-01-25 12:33     ` Henrique de Moraes Holschuh
2010-01-25 12:41       ` Justin Piszcz [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=alpine.DEB.2.00.1001250738220.9341@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=hmh@hmh.eng.br \
    --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®