lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1159886437.2891.532.camel@laptopd505.fenrus.org>
Date:	Tue, 03 Oct 2006 16:40:36 +0200
From:	Arjan van de Ven <arjan@...radead.org>
To:	Keith Chew <keith.chew@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: BIOS THRM-Throttling and driver timings

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ