From: Mike Perry <mikepery@fscked.org>
To: linux-acpi@vger.kernel.org
Subject: Re: Idle loop causes speaker whine/buzz (!)
Date: Tue, 23 Jan 2007 13:45:09 -0600 [thread overview]
Message-ID: <20070123194509.GA8644@fscked.org> (raw)
In-Reply-To: <20070123122925.GA27150@tangens.sinus.cz>
Thus spake Pavel Troller (patrol@sinus.cz):
> > For some reason, on 2.6.17-2.6.19(+others?) the acpi_processor_idle
> > loop enabled by CONFIG_ACPI_PROCESSOR is causing my laptop's speakers
> > to buzz.. If the option is disabled or built as a module (or if I run
> > both my CPUs' usage up to 100%), the speakers are silent.
>
> Your problem is related to hardware - poor filtering of power buses, causing
> current peaks to penetrate to the sound circuitry (or possibly causing some
> other hardware like a ferrite transformer) to emit sound.
> By entering deeper sleep states (especially C3), power consumption of the
> CPU substantially reduces. By returning to C0, it increases again. These
> events happen periodically, thus causing a continuous wave to be produced.
> When the system is not idle (working), the acpi CPU module is removed (so no
> sleeping) or USB is busy (so no C3, because of high BM activity), there is no
> reason for the sound.
Is there currently any way to disable busmastering or C3 transitions
(without recompilation)? Or better: is it possible to make the system
less eager to transition into C3 or otherwise reduce the frequency of
these transitions? If I could just get the frequency of transitions to
get out of the audible range, my life would be a lot better.
What governs the transition rate when the machine is mostly idle? Is
it the product of threshold.count and the latency, or am I misreading
this?
I'm sure I'm not the only person in the world who is going to
experience this problem, even if others haven't figured out what it is
yet. I'm willing to provide a patch for a proc or boot parameter-tuned
workaround if you can point me in the right direction.
Please understand it really is quite annoying, and I doubt the
manufacturer is going to have any mercy because their Windows install
doesn't have the problem..
--
Mike Perry
Mad Computer Scientist
fscked.org evil labs
next prev parent reply other threads:[~2007-01-23 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 10:40 Idle loop causes speaker whine/buzz (!) Mike Perry
2007-01-23 12:29 ` Pavel Troller
2007-01-23 19:45 ` Mike Perry [this message]
2007-01-23 21:00 ` Henrique de Moraes Holschuh
2007-01-23 21:25 ` Len Brown
2007-01-23 21:48 ` Henrique de Moraes Holschuh
2007-01-24 0:33 ` Mike Perry
2007-01-24 2:19 ` Len Brown
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=20070123194509.GA8644@fscked.org \
--to=mikepery@fscked.org \
--cc=linux-acpi@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;
as well as URLs for NNTP newsgroup(s).