From: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
To: Matthew Brett <matthew.brett@gmail.com>
Cc: "Karasyov, Konstantin A" <konstantin.a.karasyov@intel.com>,
Salatiel Filho <salatiel.filho@gmail.com>,
linux-acpi@vger.kernel.org
Subject: Re: PROBLEM: CPU fan shuts down on load of fan.ko in kernel 2.6.18 and later
Date: Sat, 13 Jan 2007 16:12:09 +0300 [thread overview]
Message-ID: <45A8DAA9.3010300@linux.intel.com> (raw)
In-Reply-To: <1e2af89e0701130429x7083b6d7we89174dd7e130364@mail.gmail.com>
Matthew Brett wrote:
> Hi,
>
>> Unfortunately, thermal zones defined in your DSDT doesn't contain any
>> trip points except critical, but the fan control requires at least
>> one active trip point (_ACx) to be defined.
>> Also, there are no fan devices (i.e. device with 'PNP0C0B' HID) defined.
>>
>> This means, that no fan and minimal thermal control is available on
>> your system through the ACPI functionality.
>
> Hmm - I guess I had the idea that my ACPI was broken, but in this
> case, the inadequacy of the ACPI means that the linux kernel had
> become dangerous for the hardware, in a way that Windows is not. Is
> there any way of making it less likely that problems in the ACPI will
> shut off the fan?
>
Matthew,
If BIOS does not export fan controls to OS via DSDT, it means that BIOS
wants to control fans via its own means (hardware), this doesn't mean
that your machine is at risk, it only means that you are not allowed to
tamper with it...
Regards,
Alex.
next prev parent reply other threads:[~2007-01-13 13:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <beb91d720701110549r346991beh95547e912f68d98f@mail.gmail.com>
2007-01-11 14:15 ` PROBLEM: CPU fan shuts down on load of fan.ko in kernel 2.6.18 and later Karasyov, Konstantin A
2007-01-11 14:37 ` Salatiel Filho
2007-01-13 12:29 ` Matthew Brett
2007-01-13 13:12 ` Alexey Starikovskiy [this message]
2007-01-13 13:33 ` Matthew Brett
2007-01-13 15:51 ` Alexey Starikovskiy
2007-01-14 5:24 ` Bjorn Helgaas
2007-01-15 13:33 ` Karasyov, Konstantin A
2007-01-15 17:06 ` Bjorn Helgaas
2007-01-16 0:39 ` Matthew Brett
2007-01-17 2:49 ` Luming Yu
2007-01-17 9:02 ` Matthew Brett
2007-01-16 16:54 ` Bjorn Helgaas
2007-01-19 12:37 ` Karasyov, Konstantin A
2006-12-28 17:14 Matthew Brett
2006-12-28 21:03 ` Alexey Starikovskiy
2006-12-28 23:36 ` Matthew Brett
2007-01-03 11:40 ` Matthew Brett
2007-01-03 20:29 ` Bjorn Helgaas
2007-01-03 20:45 ` Alexey Starikovskiy
2007-01-07 20:10 ` Matthew Brett
2007-01-08 5:08 ` Bjorn Helgaas
2007-01-09 16:53 ` Karasyov, Konstantin A
2007-01-10 1:12 ` Matthew Brett
2007-01-10 3:18 ` Salatiel Filho
2007-01-11 13:37 ` Karasyov, Konstantin A
2007-01-13 12:23 ` Matthew Brett
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=45A8DAA9.3010300@linux.intel.com \
--to=alexey.y.starikovskiy@linux.intel.com \
--cc=konstantin.a.karasyov@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=matthew.brett@gmail.com \
--cc=salatiel.filho@gmail.com \
/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