public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
To: Jeremy Moles <jeremy-9vekgGPT+OA7YuNMryXyOw@public.gmane.org>
Cc: acpi-devel-TtF/mJH4Jtrk1uMJSBkQmQ@public.gmane.org
Subject: Re: strange buzzing sound after the 2.6.10 patch
Date: Fri, 25 Feb 2005 11:47:58 +0100	[thread overview]
Message-ID: <421F025E.7000706@suse.de> (raw)
In-Reply-To: <1109280107.12887.30.camel@localhost>

Jeremy Moles wrote:
> Try this:
> 
> edit /usr/src/linux/include/asm/param.h and change HZ to 100 (instead of
> 1000). Other folks here can perhaps comment on the side-effects, though
> I've noticed few I couldn't handle. Perhaps a divide by 0 warning with
> some programs that "guess" at the HZ, but other than that...
> 
> You'll find it only happens when the processor ACPI module is loaded. Go
> figure.
> 
> On Wed, 2005-02-23 at 21:31 -0500, Jing Su wrote:
> 
>>Hello,
>>
>>I vaguely remember someone else mentioning this problem on the list
>>before, but I don't recall if there were any answers to the solution.
>>
>>I'm running a vanilla 2.6.10 kernel patched with the acpi-2005-01-25 patch.  
>>
>>When running the patched kernel, I noticed that my laptop makes a very
>>strange and faint buzzing sound.  I've determined that the buzzing
>>sound is somewhat related to CPU and HD load.  When the CPU load is
>>heavy, or when the HD is busy, the buzzing stops.  But when the system
>>idles, the buzzing continues.  I've also tried forcing the HD to go
>>into suspension using hdparm, but the buzzing continues.
>>
>>Any hints or clues?
>>If this problem hasn't been encountered before, I'd appreciate it if
>>someone could give hints for how I can best go about isolating the
>>problem.

I heard it is because of switching C-states 1000 times a second.
Loading the processor module with max_cstates=1 or 2 should work.


      Thomas


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-25 10:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24  2:31 strange buzzing sound after the 2.6.10 patch Jing Su
     [not found] ` <f11de95f050223183134a74bda-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-02-24 21:21   ` Jeremy Moles
2005-02-25 10:47     ` Thomas Renninger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-25 11:03 Jos Delbar

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=421F025E.7000706@suse.de \
    --to=trenn-l3a5bk7wagm@public.gmane.org \
    --cc=acpi-devel-TtF/mJH4Jtrk1uMJSBkQmQ@public.gmane.org \
    --cc=jeremy-9vekgGPT+OA7YuNMryXyOw@public.gmane.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