From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Martin Drab <drab@kepler.fjfi.cvut.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PC speaker beeping on high CPU loads on an nForce2
Date: Sun, 27 Nov 2005 04:31:35 +0100 [thread overview]
Message-ID: <43892897.9020900@vc.cvut.cz> (raw)
In-Reply-To: <Pine.LNX.4.60.0511270409430.30055@kepler.fjfi.cvut.cz>
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?
Nope. Your system is overheating, and on-board temperature sensors are
complaining. Probably you should find whether lm-sensors have drivers for chips
your motherboard has, and look at sensors output in that case...
Maybe ACPI could report thermal zone as well, try looking at
/proc/acpi/thermal_zone/* tree.
Petr
next prev parent reply other threads:[~2005-11-27 3:31 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 [this message]
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
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=43892897.9020900@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=drab@kepler.fjfi.cvut.cz \
--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