From: Justin Piszcz <war@starband.net>
To: "David D. Hagood" <wowbagger@sktc.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux & X11 & IRQ Interrupts
Date: Sun, 05 May 2002 21:37:26 -0400 [thread overview]
Message-ID: <3CD5DE56.B8A4C74D@starband.net> (raw)
In-Reply-To: <3CD5D57D.DED89DFC@starband.net> <3CD5DD6D.60800@sktc.net>
Ahh...
Thanks for the information.
"David D. Hagood" wrote:
> Justin Piszcz wrote:
>
> > With the console speaker attached, it can be clearly heard, as well as
> > performing fast packet movements (nmap (with insane option)) or such you
> > can literally hear the packets.
>
> What you are hearing is the noise in the computer's power supply. As the
> load on the power supply changes, the voltage changes by a few tens of
> millivolts, and that is the noise you are hearing.
>
> This primary reason you don't hear this under Windows and you hear it
> under Linux is that Linux will shut the processor off when there is
> nothing to do, greatly reducing the load on the power supply. When
> something happens, like a mouse interrupt or a network interrupt, the
> CPU springs back to life, drawing a burst of power from the power supply
> and momentarily bringing the voltage down a bit. This cycling of the CPU
> happens in microseconds.
>
> Windows, especially older versions of Windows, doesn't do this - when
> there is no work for the CPU, it spins in a busy loop looking for work.
> As a result, the load on the power supply never changes. Of course, your
> system will also run hotter and burn more power.
>
> If this bothers you, you could try getting another power supply (one
> that is "stiffer" and less prone to voltage sag) or you could run a
> program like Seti@home or Distributed.Net and keep your CPU busy all the
> time.
next prev parent reply other threads:[~2002-05-06 1:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 0:59 Justin Piszcz
2002-05-06 1:33 ` David D. Hagood
2002-05-06 1:37 ` Justin Piszcz [this message]
2002-05-06 20:53 ` Andrew Morton
2002-05-06 15:24 ` Alan Cox
2002-05-06 16:17 ` Grogan
2002-05-06 16:28 ` Diego Calleja
2002-05-06 16:46 ` Tomas Szepe
2002-05-06 18:05 ` Diego Calleja
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=3CD5DE56.B8A4C74D@starband.net \
--to=war@starband.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wowbagger@sktc.net \
/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
all inboxes | Powered by JetHome®