From: "Matthew Brett" <matthew.brett@gmail.com>
To: Luming Yu <luming.yu@gmail.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
"Karasyov, Konstantin A" <konstantin.a.karasyov@intel.com>,
Alexey Starikovskiy <alexey.y.starikovskiy@linux.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: Wed, 17 Jan 2007 09:02:02 +0000 [thread overview]
Message-ID: <1e2af89e0701170102u45618fbdo851cb29d86bf54ae@mail.gmail.com> (raw)
In-Reply-To: <3877989d0701161849s35069b88u537fffcd913b355d@mail.gmail.com>
Hi,
> Does it really solve the problem of CPU fan shutting down on load of fan.ko?
> Could you just re-test, since that is the problem from the beginning.
Yes; normally fan.ko is insmodded in my boot sequence. At that point
in the boot sequence the fan turns off and cannot be turned on again
(see results of echos to fan state earlier). After the DSDT patch, the
fan stays on through the boot sequence, fan.ko is shown as loaded via
lsmod, and echos to fan state behave as expected.
Best,
Matthew
next prev parent reply other threads:[~2007-01-17 9:02 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
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 [this message]
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=1e2af89e0701170102u45618fbdo851cb29d86bf54ae@mail.gmail.com \
--to=matthew.brett@gmail.com \
--cc=alexey.y.starikovskiy@linux.intel.com \
--cc=bjorn.helgaas@hp.com \
--cc=konstantin.a.karasyov@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=luming.yu@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