From: "Keith Chew" <keith.chew@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BIOS THRM-Throttling and driver timings
Date: Mon, 9 Oct 2006 11:04:18 +1300 [thread overview]
Message-ID: <20f65d530610081504o3a72f654pf60cb9e0278bf2e0@mail.gmail.com> (raw)
In-Reply-To: <1160343907.3000.183.camel@laptopd505.fenrus.org>
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
>
> Really? AFAICT P4 will happily slow down behind our backs, making at
> least udelays() with interrupts disabled sleep for too long.
>
I believe we are seeing similar behaviours with the drivers. As a
temporary workaround, we have asked the manufacturers to supply us
with a BIOS that disabled THRM-Throttling. So far, things are looking
good, but we are still doing more testing.
> > (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)
>
> At least in toshiba notebook, I was hitting thermal throttling even
> through both fans were okay. There are many misdesigned machines out
> there, I fear.
In our case, we are running the unit in mobile environment, with not
much ventilation. In our test environment, the unit runs fine at
temperatures of 80-90 degrees. In the real environment, we only expect
temperatures of 50-70 degrees.
Regards
Keith
prev parent reply other threads:[~2006-10-08 22:04 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
2006-10-08 22:04 ` Keith Chew [this message]
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=20f65d530610081504o3a72f654pf60cb9e0278bf2e0@mail.gmail.com \
--to=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®