From: Valdis.Kletnieks@vt.edu
To: Andrew McGregor <andrew@indranet.co.nz>
Cc: Tuncer M zayamut Ayaz <tuncer.ayaz@gmx.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.69 strange high tone on DELL Inspiron 8100
Date: Sun, 11 May 2003 16:48:38 -0400 [thread overview]
Message-ID: <200305112048.h4BKmdkc006140@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sun, 11 May 2003 23:28:25 +1200." <3191078.1052695705@[192.168.1.249]>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
On Sun, 11 May 2003 23:28:25 +1200, Andrew McGregor <andrew@indranet.co.nz> said:
> cpufreq and speedstep don't work on Dell P3 laptops anyway, and the
> *internal power supplies* of the i8x00 series make wierd noises when APM
> tries to idle the CPU. The board will do this anyway, without making
> noise, so linux need not.
Dell Latitude C840 (1.6G Pentium4 Mobile) has the "power supplies buzz at 1Khz
on APM idle" symptom too. I haven't checked the ACPI side of the fence yet, nor
have I gotten brave enough to try the cpufreq and speedstep stuff.
Even *more* bizarre, there's "something odd" done by the seti@home client
(which usually causes 100% CPU use and thus silence) several minutes into a
workunit that causes the noise to change frequencies - it will start down
around 500hz, sweep up to 1Khz (taking about 2 seconds to do so), and repeat
(so the buzzing is exhibiting a sawtooth wave). I'm not seeing any paging
or swapping or I/O, so I'm wondering if it's some code walking through a large
array with strides 1/2/4/8/16 (like an FFT) causing different cache hit ratios,
and thus different power consumption patterns while it's stuck on a L1/L2
cache miss.....
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-05-11 20:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 13:57 2.5.69 strange high tone on DELL Inspiron 8100 Tuncer M zayamut Ayaz
2003-05-10 13:59 ` Alan Cox
2003-05-10 15:07 ` Tuncer M zayamut Ayaz
2003-05-10 15:28 ` Tuncer M zayamut Ayaz
2003-05-10 15:39 ` Ahmed Masud
2003-05-10 15:46 ` Tuncer M zayamut Ayaz
2003-05-10 16:25 ` Jamie Lokier
2003-05-10 16:51 ` Tuncer M zayamut Ayaz
2003-05-10 17:35 ` Tuncer M zayamut Ayaz
2003-05-10 17:47 ` Xavier Bestel
2003-05-10 20:06 ` Tuncer M zayamut Ayaz
2003-05-10 20:23 ` Tuncer M zayamut Ayaz
2003-05-10 21:13 ` Tuncer M zayamut Ayaz
2003-05-11 10:50 ` Dumitru Ciobarcianu
2003-05-11 13:11 ` Tuncer M zayamut Ayaz
2003-05-11 11:28 ` Andrew McGregor
2003-05-11 13:03 ` Tuncer M zayamut Ayaz
2003-05-12 0:34 ` Andrew McGregor
2003-05-12 6:17 ` Tuncer M zayamut Ayaz
[not found] ` <200305120620.h4C6K64j061741@ns.indranet.co.nz>
2003-05-12 20:11 ` Andrew McGregor
2003-05-13 6:20 ` Tuncer M zayamut Ayaz
2003-05-11 20:48 ` Valdis.Kletnieks [this message]
2003-05-12 0:41 ` Andrew McGregor
2003-05-13 12:43 ` Troels Walsted Hansen
2003-05-13 12:50 ` Tuncer M zayamut Ayaz
[not found] <20030510154639.02DDC32C9@marauder.googgun.com>
2003-05-10 15:52 ` Ahmed Masud
2003-05-10 16:04 ` Tuncer M zayamut Ayaz
2003-05-10 18:33 ` Jos Hulzink
2003-05-10 16:46 ` Tuncer M zayamut Ayaz
2003-05-10 19:46 Chuck Ebbert
2003-05-10 20:06 ` Tuncer M zayamut Ayaz
2003-05-11 2:28 Chuck Ebbert
2003-05-11 19:27 ` Tuncer M zayamut Ayaz
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=200305112048.h4BKmdkc006140@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=andrew@indranet.co.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=tuncer.ayaz@gmx.de \
/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).