mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Keith Chew <keith.chew@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BIOS THRM-Throttling and driver timings
Date: Sun, 08 Oct 2006 23:45:06 +0200	[thread overview]
Message-ID: <1160343907.3000.183.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20061008211821.GA4280@elf.ucw.cz>

On Sun, 2006-10-08 at 23:18 +0200, Pavel Machek 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.
> 
> > in general linux should be ok with this happening. However for specific
> > cases... you'll need to provide more information; you're not
> > mentioning
> 
> Really? AFAICT P4 will happily slow down behind our backs, making at
> least udelays() with interrupts disabled sleep for too long.

it will during thermal throttle yes. but udelay() and co as API never
have  been super accurate; they mostly promise at least this much delay




  reply	other threads:[~2006-10-08 21:45 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
2006-10-08 21:18   ` Pavel Machek
2006-10-08 21:45     ` Arjan van de Ven [this message]
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=1160343907.3000.183.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=keith.chew@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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®