From: Arjan van de Ven <arjan@infradead.org>
To: Keith Chew <keith.chew@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BIOS THRM-Throttling and driver timings
Date: Tue, 03 Oct 2006 16:40:36 +0200 [thread overview]
Message-ID: <1159886437.2891.532.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20f65d530610030729o42658bd6hcc204f8deac4a33e@mail.gmail.com>
On Wed, 2006-10-04 at 03:29 +1300, Keith Chew wrote:
> Hi
>
> We have a motherboard that has Thermal Throttling in the BIOS (which
> we cannot disable). This causes the CPU usage to go up and down when
> the CPU temperature reaches (and stays around) the Throttling
> temperature point.
>
> What we would like to know is whether this will affect the timings in
> drivers, eg the wireless drivers we are using. What can we check in
> drivers' code that will tell us that its operations may be affected
> the throttling?
>
> In the past few days, we noticed that some of the linux units we
> deployed freezes after deveral hours of operation, we are now trying
> to reproduce the problem in our test environment. Some insight on the
> affect of throttling will help us narrow down the search.
Hi,
in general linux should be ok with this happening. However for specific
cases... you'll need to provide more information; you're not mentioning
which drivers you are using for example. Or even which versions of the
kernel etc etc....
(also: if you actually HIT throttling, there is something very very
wrong; you're not supposed to hit that unless the fan is defective, but
never in "normal" healthy operation. If you do hit it without hardware
defects then there is most likely a fundamental airflow problem you'll
want to fix urgently)
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
next prev parent reply other threads:[~2006-10-03 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 14:29 Keith Chew
2006-10-03 14:40 ` Arjan van de Ven [this message]
2006-10-08 21:18 ` Pavel Machek
2006-10-08 21:45 ` Arjan van de Ven
2006-10-08 22:04 ` Keith Chew
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=1159886437.2891.532.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=keith.chew@gmail.com \
--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®