From: "Matthew Brett" <matthew.brett@gmail.com>
To: "Karasyov, Konstantin A" <konstantin.a.karasyov@intel.com>
Cc: 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: Wed, 10 Jan 2007 01:12:28 +0000 [thread overview]
Message-ID: <1e2af89e0701091712h692985eesdf66dba6b3e7daec@mail.gmail.com> (raw)
In-Reply-To: <E3C0BCA40296C347AF7142161DB9FC8293DA20@mssmsx411>
Hi,
> Could you please perform the following testing:
Thanks a lot for the reply. Results of tests below. I've included
the output from the 2.6.17 kernel and 2.6.20-rc3 kernel with comments.
Patched kernel gave identical output to unpatched... CPU load did
not turn on the fan as before.
Best,
Matthew
2.6.17 kernel, fan on at boot
[root@bob ~]# cat /proc/acpi/thermal/*/*
cat: /proc/acpi/thermal/*/*: No such file or directory
[root@bob ~]# cat /proc/acpi/thermal_zone/*/*
<setting not supported>
cooling mode: passive
<polling disabled>
state: passive
temperature: -270 C
critical (S5): -264 C
passive: -273 C: tc1=0 tc2=0 tsp=600 devices=0xf7ffd340
active[0]: -267 C: devices=0xf7ffd5c0
[root@bob ~]# cat /proc/acpi/fan/*/state
status: on
[root@bob ~]# echo 3 > /proc/acpi/fan/*/state
-bash: echo: write error: Exec format error
[Fan goes off]
[root@bob ~]# echo 0 > /proc/acpi/fan/*/state
[No effect, fan stays off]
[root@bob ~]#
2.6.20-rc3 kernel, fan off at boot
[root@bob ~]# cat /proc/acpi/thermal/*/*
cat: /proc/acpi/thermal/*/*: No such file or directory
[root@bob ~]# cat /proc/acpi/thermal_zone/*/*
<setting not supported>
cooling mode: passive
<polling disabled>
state: passive active[0]
temperature: -266 C
critical (S5): -264 C
passive: -273 C: tc1=0 tc2=0 tsp=600 devices=0xc18fd2c0
active[0]: -267 C: devices=0xc18fd798
[root@bob ~]# cat /proc/acpi/fan/*/state
status: on
[root@bob ~]# echo 3 > /proc/acpi/fan/*/state
-bash: echo: write error: Exec format error
[No effect]
[root@bob ~]# echo 0 > /proc/acpi/fan/*/state
[No effect]
next prev parent reply other threads:[~2007-01-10 1:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 17:14 PROBLEM: CPU fan shuts down on load of fan.ko in kernel 2.6.18 and later 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 [this message]
2007-01-10 3:18 ` Salatiel Filho
2007-01-11 13:37 ` Karasyov, Konstantin A
2007-01-13 12:23 ` Matthew Brett
[not found] <beb91d720701110549r346991beh95547e912f68d98f@mail.gmail.com>
2007-01-11 14:15 ` Karasyov, Konstantin A
2007-01-11 14:37 ` Salatiel Filho
2007-01-13 12:29 ` Matthew Brett
2007-01-13 13:12 ` Alexey Starikovskiy
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
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=1e2af89e0701091712h692985eesdf66dba6b3e7daec@mail.gmail.com \
--to=matthew.brett@gmail.com \
--cc=konstantin.a.karasyov@intel.com \
--cc=linux-acpi@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