public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Nils Faerber
	<nils.faerber-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Kernel 2.4.23 passive cooling
Date: Mon, 12 Jan 2004 20:04:18 +0100	[thread overview]
Message-ID: <20040112190418.GA18452@hell.org.pl> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401720BEE-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>

Thus wrote Yu, Luming:
> Try
> #echo -n 0x04000000 > /proc/acpi/debug_layer
> #echo -n 0xffffffff > /proc/acpi/debug_level

I produced a log (http://hell.org.pl/~sziwan/thermal.log) using those
switches. A bit of commentary:
18:57:59 -- I switch to passive cooling
18:59:07 -- Back to active
18:59:19 -- Forth to passive
[no thermal events till 19:25:12, the readings are trigerred manually]
After that, the temperature rocks up and down, as fan switch in at 3480 dK. 
This seems to be a DSDT bug after all, since the debug output doesn't seem
suspicious and it even fails to notice the fans (which is normal, since the
method to reevaluate the fans is internally called from within the GPE
context). See http://bugme.osdl.org/show_bug.cgi?id=1185 for the DSDT and
additional info.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html

  parent reply	other threads:[~2004-01-12 19:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03  3:29 Kernel 2.4.23 passive cooling Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720BEE-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-12 19:04   ` Karol Kozimor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-13  6:47 Yu, Luming
2003-12-01 18:02 Nils Faerber
     [not found] ` <1070301739.1353.6.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2003-12-02 12:26   ` Karol Kozimor
     [not found]     ` <20031202122644.GA6024-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-12-02 12:42       ` Karol Kozimor

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=20040112190418.GA18452@hell.org.pl \
    --to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=nils.faerber-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.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