public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Thomas Glomann <mailinglists-WoYc4IhrKEiELgA04lAiVw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: high pitch noise with kernel 2.6 and ACPI (Dell Inspiron 8200)
Date: Wed, 18 Feb 2004 14:11:32 -0800 (PST)	[thread overview]
Message-ID: <20040218140940.K36847@root.org> (raw)
In-Reply-To: <200402182017.47960.mailinglists-WoYc4IhrKEiELgA04lAiVw@public.gmane.org>

On Wed, 18 Feb 2004, Thomas Glomann wrote:
> On Wednesday 18 February 2004 14:32, Mads Paulin wrote:
> > Hi Thomas,
> >
> > funny you mention it, I thought I was going crazy.
> >
> > I experienced the same thing, and discovered it to be the hard drive.
> >
> > Try to spind the drive down using hdparm and see if that helps.
> >
> nope, putting the drive to sleep doesn't do the trick. the sound remains.
> Moreover I don't see how this "solution" was meant to work? Does the sound
> reappear when you wake up your disk or does it keep silent after a nice
> "onetime" sleep?
> > Obviously this is not a solution, but if it helps, kernel 2.6 could have
> > some other way of controlling the disk than 2.4.
> >
> Still it doesn't explain why that sound is gone when disabling the whole
> acpi-system.
> > The noise disappears when my hdd is under heavy load.
> > - Maybe you just cant here it then, or it actually disappears because it
> > is no longer idle
> >
> well thats true. as long as the disk is Not idle, the noise is gone. But
> returns right after.

Disable cpu idling support or try various combinations of C1-C3.  The
noise is most likely capacitors (dis)charging as part of chipset-supported
clock stopping.  You can detect this case by changing the scheduling
quantum (HZ) to be something other than 1000.

-Nate


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

  parent reply	other threads:[~2004-02-18 22:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18 12:20 high pitch noise with kernel 2.6 and ACPI (Dell Inspiron 8200) Thomas Glomann
     [not found] ` <200402181320.29381.mailinglists-WoYc4IhrKEiELgA04lAiVw@public.gmane.org>
2004-02-18 13:32   ` Mads Paulin
     [not found]     ` <1077111155.2028.3.camel-LS+HbC+WUqy6wZ7Myly0Ql9iRXqZKEsZ@public.gmane.org>
2004-02-18 19:17       ` Thomas Glomann
     [not found]         ` <200402182017.47960.mailinglists-WoYc4IhrKEiELgA04lAiVw@public.gmane.org>
2004-02-18 20:45           ` Michael Guntsche
     [not found]             ` <20040218214542.58569565.mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
2004-02-19  9:02               ` Thomas Glomann
2004-02-18 20:49           ` Dominik Brodowski
2004-02-18 21:27           ` Jason Straight
2004-02-18 22:11           ` Nate Lawson [this message]
2004-02-18 23:37           ` Adam Lackorzynski
2004-02-18 23:57           ` Markus Wiesner

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=20040218140940.K36847@root.org \
    --to=nate-y6vguytwhu0@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=mailinglists-WoYc4IhrKEiELgA04lAiVw@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