From: Willy Tarreau <willy@w.ods.org>
To: Martin Drab <drab@kepler.fjfi.cvut.cz>
Cc: Gene Heskett <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 19:33:13 +0100 [thread overview]
Message-ID: <20051127183313.GQ11266@alpha.home.local> (raw)
In-Reply-To: <Pine.LNX.4.60.0511271839480.24919@kepler.fjfi.cvut.cz>
On Sun, Nov 27, 2005 at 06:56:23PM +0100, Martin Drab wrote:
> On Sun, 27 Nov 2005, Gene Heskett wrote:
>
> > On Saturday 26 November 2005 22:23, Martin Drab wrote:
> > >Hi,
> > >
> > >on an nForce2 system (GigaByte 7NNXP) when the CPU is under heavy load
> > >(like during kernel compilation for instance, or any compilation of any
> > >bigger project, for that matter), I hear some beeps comming out of the
> > > PC speaker. It's like few short beeps per second for a while, then
> > > silence for few seconds, then a beep here and there, and again, and so
> > > on. It is quite strange. It happens ever since I remember (I mean in
> > > kernel versions of course, I have the board for about 1.5 years). I've
> > > just been kind of ignoring it until now. Does anybody else happen to
> > > see the same symptoms? What could be the cause of this. Is it
> > > something about timing? But how come the PC speaker gets kiced in,
> > > while it's not being used at all (well, at least not intentionally)
> > > for anything. Perhaps something is writing some ports it is not
> > > supposed to?
> > >
> > >Martin
> >
> > Usually, thats a sign of cpu overheating. At 18 months, if the cpu
> > fan/heat sink hasn't been blown out by an air hose, its so packed full
> > of dust bunnies that no amount of rpms can force any air thru the cpu's
> > heat sink fins.
>
> No, it isn't a problem of dust or grease. It is a problem of a case full
> of devices and bad airflow within it. (There's 6 HDDs, 8 PCI cards, an
> AthlonXP 3200+ with massive Zalman CNPS6000-Cu on top of it and 10 fans
> that are doing all they can running at maximum (with the noise of a
> medium vacuum cleaner ;), trying to cool it all, but it just isn't
> enough.) So I'll try to solve it by a water cooling.
Should be cheaper to buy a bigger case with a *real airflow path, and
remove some of those fans. It's non-sense to put 10 fans in a mono-proc
system ! even with 6 disks (probably even IDE disks).
BTW, if you have the case FAN orthogonal to the CPU's and close to it,
you'd better stop it as ot will prevent part of the airflow from entering
the CPU's fan. It's amazing to see the number of boxes with a case FAN
which increases the CPU temperature by 5 degrees once it spins up ! I
too had one which made my dual athlon regularly crash, and it's OK now
that I have unplugged it. I noticed it first because the rear CPU was
5 degrees hotter than the front one.
> I just didn't connect these sounds with the MB alarm. (Even though I know
> that there is this kind of feature.)
If your system is stable, you can also disable the alarm. It's very
conservative and will beep for nearly nothing. My dual athlon runs
up to 92 degrees celcius on summer without crashing. The highest alarm
threshold was something like 60 degrees...
> However thanks for the advises anyway,
> Martin
Regards,
Willy
next prev parent reply other threads:[~2005-11-27 18:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-27 3:23 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 [this message]
2005-11-27 21:38 ` Martin Drab
2005-11-27 19:10 ` Paul Jackson
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=20051127183313.GQ11266@alpha.home.local \
--to=willy@w.ods.org \
--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
all inboxes | Powered by JetHome®