From: Paul Jackson <pj@sgi.com>
To: Martin Drab <drab@kepler.fjfi.cvut.cz>
Cc: gene.heskett@verizon.net, linux-kernel@vger.kernel.org
Subject: Re: PC speaker beeping on high CPU loads on an nForce2
Date: Sun, 27 Nov 2005 11:10:29 -0800 [thread overview]
Message-ID: <20051127111029.0d6ef37f.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0511271839480.24919@kepler.fjfi.cvut.cz>
With that many fans, make sure you have good airflow,
with all the fans pushing the air the same way.
Good airflow is like good rush hour traffic on the
freeway - steady, consistent, minimal causes of
turbulence, wide lanes, no bottlenecks, ...
Cooling your Computer
http://www.atruereview.com/Articles/compcool.php
THE HEATSINK GUIDE: Case Cooling
http://www.heatsink-guide.com/content.php?content=case.shtml
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
prev parent reply other threads:[~2005-11-27 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-27 3:23 PC speaker beeping on high CPU loads on an nForce2 Martin Drab
2005-11-27 3:31 ` Petr Vandrovec
2005-11-27 13:39 ` Martin Drab
2005-11-28 15:50 ` Jan Engelhardt
2005-11-28 16:05 ` ACPI: PCI Interrupt Link [LNKA] (IRQs *7) JaniD++
2005-11-29 8:15 ` Denis Vlasenko
2005-11-29 15:36 ` Carlos Martín
2005-11-30 17:35 ` Jan Engelhardt
2005-11-30 23:25 ` JaniD++
2005-11-30 23:18 ` JaniD++
2005-11-30 23:14 ` JaniD++
2005-11-27 6:11 ` PC speaker beeping on high CPU loads on an nForce2 Gene Heskett
2005-11-27 14:34 ` Ivan Yosifov
2005-11-27 17:56 ` Martin Drab
2005-11-27 18:33 ` Willy Tarreau
2005-11-27 21:38 ` Martin Drab
2005-11-27 19:10 ` Paul Jackson [this message]
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=20051127111029.0d6ef37f.pj@sgi.com \
--to=pj@sgi.com \
--cc=drab@kepler.fjfi.cvut.cz \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@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