public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Len Brown <lenb@kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: Fan resume not working on nx6325 without userland assistance
Date: Tue, 22 Jan 2008 20:40:56 +0300	[thread overview]
Message-ID: <47962AA8.9010600@suse.de> (raw)
In-Reply-To: <200801221814.05416.rjw@sisk.pl>

Does revert of 93ad7c07ad487b036add8760dabcc35666a550ef helps?



Rafael J. Wysocki wrote:
> On Tuesday, 22 of January 2008, Rafael J. Wysocki wrote:
>> Hi,
>>
>> It turns out that the following script (from openSUSE 10.3):
>>
>> #############################################################
>> # triggers the ACPI fan(s) after resume. Since ACPI drivers
>> # have no suspend support, this is sometimes necessary.
>> # see http://article.gmane.org/gmane.linux.acpi.devel/16643
>> kick-fan()
>> {
>>         local FAN DUMMY STATE
>>         for FAN in /proc/acpi/fan/*/state; do
>>                 [ ! -e $FAN ] && continue
>>                 read DUMMY STATE < $FAN
>>                 if [ "$STATE" = "on" ]; then
>>                         echo "kicking $FAN"
>>                         echo -n 3 > $FAN
>>                         echo -n 0 > $FAN
>>                 fi
>>         done
>> }
>>
>> case $1 in
>>         thaw|resume)
>>                 kick-fan
>>                 ;;
>> esac
>>
>> is necessary to make the fan behave appropriately after a resume from RAM
>> (I haven't checked resume from hibernation, but I guess the same thing happens)
>> on HP nx6325 with 2.6.24-rc8 (and with previous kernels probably too).
>>
>> It wasn't needed at one point, so something has regressed.  Sigh.
> 
> Ah, I didn't say that thermal management is completely busted after a resume
> if the fan is not kicked from the user land (using the above script).  Usually
> the fan is 100% on (that corresponds to all ACPI "fans" being on), but once it
> had gone off and I was unable to turn it on by any means (including rising the
> temperature to a dangerous level).
> 
> Greetings,
> Rafael


  reply	other threads:[~2008-01-22 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22  1:41 Fan resume not working on nx6325 without userland assistance Rafael J. Wysocki
2008-01-22 17:14 ` Rafael J. Wysocki
2008-01-22 17:40   ` Alexey Starikovskiy [this message]
2008-01-22 20:56     ` Rafael J. Wysocki
2008-01-23 15:02       ` Rafael J. Wysocki

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=47962AA8.9010600@suse.de \
    --to=astarikovskiy@suse.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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