From: Janosch Machowinski <jmachowinski-Mmb7MZpHnFY@public.gmane.org>
To: Stefan Baums <baums@u.washington.edu>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Fw: ACPI and the idle loop - possible bug
Date: Sun, 26 Jun 2005 02:05:03 +0200 [thread overview]
Message-ID: <1119744303.14822.9.camel@localhost> (raw)
In-Reply-To: <20050625151923.738504b1.akpm-3NddpPZAyC0@public.gmane.org>
> Some Lenove (IBM) ThinkPad models (in my case the ThinkPad X41
> 2528-6NU) produce irritating high-pitch crackling noises under
> Linux in certain conditions
This Problem also occures on a lot of ASUS Laptops,
sounds a bit like the morse alpabet ;-)
> This noise only occurs when the processor is not busy (with, e.g.,
> compiling or video playback), so it seems to be related to the
> idle loop (see also below about 'idle=halt'). Furthermore, it
> seems to be caused by something that ACPI is doing to the
> processor: if the 'processor' module (and its dependants:
> 'speedstep_centrino'/'acpi_cpufreq' and 'thermal') are not loaded,
> the high-pitch noise does not occur.
>
My suggestion is that this sounds are created by the powerconverters.
And it only occurs on my ASUS M6 when the processor is in C3.
So the described behaviour is clear, cause if you unload the processor
ACPI module, you processor will stop going in C3 and thou the sounds
stop.
> If the 'processor' module (and its dependants) _are_ loaded, then
> the noise can be initially avoided by passing the boot parameter
>
> idle=halt
What exactly does this parameter do ? Using for all C-States the hlt
instruction ?
> - First, for causing the high-pitch noise to start with, though
> it could be argued that this is a hardware defect that is
> just triggered by ACPI. (However not by Windows XP, on the
> same computer, so it is definitely avoidable.)
>
Could also be that XP dosen't use C3 as much as Linux does
Janosch
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-06-26 0:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-25 22:19 Fw: ACPI and the idle loop - possible bug Andrew Morton
[not found] ` <20050625151923.738504b1.akpm-3NddpPZAyC0@public.gmane.org>
2005-06-26 0:05 ` Janosch Machowinski [this message]
2005-06-26 3:40 ` Stefan Baums
2005-06-27 3:18 ` Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD3057502698BE3-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-06-27 22:09 ` Stefan Baums
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=1119744303.14822.9.camel@localhost \
--to=jmachowinski-mmb7mzphnfy@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=baums@u.washington.edu \
/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