Bug 11691 - cooling fan will not turn on - toshiba satellite amilo a100-998
cooling fan will not turn on - toshiba satellite amilo a100-998
Status: REJECTED INSUFFICIENT_DATA
Product: ACPI
Classification: Unclassified
Component: Other
All Linux
: P1 normal
Assigned To: ykzhao
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-03 07:51 UTC by terry gardener
Modified: 2008-11-20 23:18 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.27
Tree: Mainline
Regression: ---


Attachments
acpidump contents (160.74 KB, text/plain)
2008-10-07 03:08 UTC, terry gardener
Details
acpidump file (141.13 KB, text/plain)
2008-10-07 03:23 UTC, terry gardener
Details
dmesg file (41.50 KB, text/plain)
2008-10-07 03:24 UTC, terry gardener
Details
dmesg file (40.71 KB, text/plain)
2008-10-15 14:05 UTC, terry gardener
Details

Description terry gardener 2008-10-03 07:51:22 UTC
Latest working kernel version:
Earliest failing kernel version:
Distribution:
Hardware Environment:
Software Environment:
Problem Description:
laptop toshiba satellite amilo a100-998

Intel centrino duo 1.66.

the fan in the laptop is not turning on and cant even hear it, i have checked the log messages and that has confirmed it with a message saying:
acpi: transitioning device [fan0] to D0
ACPI: unable to turn cooling device [f7414468] 'on'

and this is repeated 5 times.

ubuntu intrepid (development branch) alpha 6
release: 8.10

The fan works in hardy and linux mint 5.

also tried: 


installed the acpitool and typed the above acpitool -f and got response fan : off.
i tried the next command acpitool -F 1 got message.

forcing the fan of/off is ony supported on toshiba laptops.
no toshiba acpi extensions were found .

the above is the exact text given when running the commands.

i originally raised this bug at ubuntu launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/272537 but was asked to raise it here because it is kernel related. 

Steps to reproduce:
Comment 1 ykzhao 2008-10-06 07:02:31 UTC
Will you please try the patch set in 
http://bugzilla.kernel.org/show_bug.cgi?id=11000#C30,31,32 and see whether the problem still exists?(Please add the boot option of "acpi.power_nocheck=1").

Will you please attach the output of acpidump, dmesg?
Thanks.
Comment 2 terry gardener 2008-10-06 13:43:50 UTC
sorry can you give me instructions on how to do the patch and get the outputs you require. 

i have only used ubuntu and linux for just over 1 year and first time i have ever tried a alpha release. 
Comment 3 ykzhao 2008-10-06 17:50:25 UTC
Hi, terry
    You can apply the patch set on the latest kernel(2.6.27-rc8) and do the test as mentioned in comment #1. (The boot option of "acpi.power_nocheck=1").
    
    Please use the acpidump tool to get the acpidump. The latest dump tool(Pmtools-20071116) can be found in http://www.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
    
    Of course it will be great if you can attach the output of dmesg.
    thanks.
    
    
    
Comment 4 terry gardener 2008-10-07 03:08:29 UTC
Created attachment 18188 [details]
acpidump contents
Comment 5 terry gardener 2008-10-07 03:09:38 UTC
(In reply to comment #4)
> Created an attachment (id=18188) [details]
> acpidump contents
> 
ignore this attachment wrong pc 
Comment 6 terry gardener 2008-10-07 03:23:31 UTC
Created attachment 18189 [details]
acpidump file
Comment 7 terry gardener 2008-10-07 03:24:18 UTC
Created attachment 18190 [details]
dmesg file 

dmesg file as requested
Comment 8 terry gardener 2008-10-07 03:40:41 UTC
please can you give step by step instruction on how to do the patch. 

i have downloaded the patch from comment #22 in the above weblink. 

i have read the readme file and did --dry-run on the patch files and all of then said file to patch. (didn't know the answer so canceled it) 

thanks 
Comment 9 ykzhao 2008-10-07 18:20:32 UTC
Hi, Terry
    It is Ok to apply the patch set one by one on the latest kernel (2.6.27-rc9). 
    Thanks.
Comment 10 terry gardener 2008-10-08 03:39:28 UTC
hello

sorry to be a pain about this but it is the first time i have ever filed a bug report, and i have no programming knowledge or experience what so ever. 

just have couple of questions. 

i am using kernel version 2.6.27.6-generic.from command uname -r

which patches should i be downloading from bug 11000 the one in comment 22 or from comment 30-32, the comment 20 doesn't seem to work. 

also please can i have instructions how to apply the patch because i have tried "patch -p0 < patch-name" and it says file to patch and don't know the answer. 

thanks 
Comment 11 Len Brown 2008-10-08 12:20:10 UTC
kernel patch directions are here:
http://lesswatts.org/projects/acpi/applying-patches.php
Comment 12 terry gardener 2008-10-08 13:47:33 UTC
please can someone confirm which patch that i am suppose to be applying to fix this issue. 

the latest patch from here http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.6.26/ or from the bug 11000, if from the bug 11000 which one should i use one from comment 22 or 30-32 as the link in comment 20 doesn't work properly. 

also thank you for the information on how to apply the patch. 
Comment 13 ykzhao 2008-10-08 20:06:31 UTC
Hi, Terry
    What Lenb said in comment #11 is only to tell you how to apply the patch set.
    Please try the patch in http://bugzilla.kernel.org/show_bug.cgi?id=11000#C30,31,32 and not the comment #20.
    When it says file to patch, please type the file name.
    for example:
     >|Index: linux-2.6/drivers/acpi/scan.c
|===================================================================
|--- linux-2.6.orig/drivers/acpi/scan.c
|+++ linux-2.6/drivers/acpi/scan.c
--------------------------
    >File to patch: drivers/acpi/scan.c
    After type the file name, it will be prompted that the file is patched successfully.
    >patching file drivers/acpi/scan.c
    >Hunk #1 succeeded at 1252 (offset -18 lines)

    Thanks again.
Comment 14 terry gardener 2008-10-09 03:01:09 UTC
when i have tried to apply the patches it seems to have failed on the 3rd patch.

patch --dry-run -Np1 < /home/terry/patch/power_debug2.patch
patching file Documentation/kernel-parameters.txt
patching file drivers/acpi/power.c
Hunk #2 FAILED at 236.
Hunk #3 FAILED at 293.
2 out of 3 hunks FAILED -- saving rejects to file drivers/acpi/power.c.rej
patching file include/acpi/acpi_drivers.h
patching file drivers/acpi/bus.c
 
the other 2 seems like they work. 

terry@terry-laptop:~$ cd /usr/src/linux
terry@terry-laptop:/usr/src/linux$ patch --dry-run -Np1 < /home/terry/patch/acpi_device_debug.patch
patching file drivers/acpi/scan.c
Hunk #1 succeeded at 1252 (offset -10 lines).
Hunk #2 succeeded at 1291 (offset -10 lines).
terry@terry-laptop:/usr/src/linux$ patch --dry-run -Np1 < /home/terry/patch/power_debug.patch
patching file drivers/acpi/power.c
patching file drivers/acpi/scan.c
Hunk #1 succeeded at 807 (offset -7 lines).

i am currently using linux kernel 2.6.27.6-generic. 

i didn't want to apply it for real since it failed on the 3 patch without checking if it is ok to. 

thanks 
Comment 15 terry gardener 2008-10-09 03:39:39 UTC
ij wasn't 100% sure where to do the acpi.power_nocheck=1 bit so, after looking through power_debug2.patch i found "acpi.power_nocheck=" under the first section so i added the 1 to it to make acpi.power_nocheck=1, i have pasted where i edited the patch below.

Index: linux-2.6/Documentation/kernel-parameters.txt
===================================================================
--- linux-2.6.orig/Documentation/kernel-parameters.txt
+++ linux-2.6/Documentation/kernel-parameters.txt
@@ -231,6 +231,13 @@ and is between 256 and 4096 characters. 
 			The number can be in decimal or prefixed with 0x in hex.
 			Warning: Many of these options can produce a lot of
 			output and make your system unusable. Be very careful.
+	acpi.power_nocheck=1	[HW,ACPI]
+			Format: 1/0 enable/disable the check of power state.
+			On some bogus BIOS the _PSC object/_STA object of
+			power resource can't return the correct device power
+			state. In such case it is unneccessary to check its
+			power state again in power transition.
+			1 : disable the power state check
 
 	acpi_pm_good	[X86-32,X86-64]
 			Override the pmtimer bug detection: force the kernel 

if this is wrong please tell me where to insert this option. 
Comment 16 terry gardener 2008-10-09 13:28:37 UTC
i have also tried again with kernel version 2.6.27-rc9 with the dry run command and first 2 patches seem fine but patch 3 gets the same message as in comment #14
Comment 17 ykzhao 2008-10-09 20:17:30 UTC
Hi, Terry
    I try the patch set on the 2.6.27-rc9 and it can be applied successfully. Can you confirm whether the patch is applied one by one?(Pay attention to the apply order. Patch 1, then patch 2, the last is patch 3)
    thanks.
Comment 18 terry gardener 2008-10-10 14:49:24 UTC
i reinstalled ubuntu today so that i could dual boot between hardy and intrepid and installed the latest kernel stable 2.6.27 as 2.6.27-rc9 no longer available. 

i have applied the patch on the new stable release 2.6.27. and the patches said applied successfully. 

i have monitored the logs and i am still getting. 
acpi: transitioning device [fan0] to D0
ACPI: unable to turn cooling device [f4812468] 'on'

the f number changes also same message but also [f7414468]

ubuntu has just had kernel change to 2.6.27-7-generic and i will monitor it. 

any ideas 
thanks 

ps if you need the dmesg and acpidump again just ask. 

Comment 19 terry gardener 2008-10-11 05:52:35 UTC
i installed gnome sensors applet to check the temp of the cpu/gpu. 

i also ran glxgears to put some stress on the cpu for the temp to go up. 

when idle the cpu is running at between 45 - 50c averaging about 48 c 

when i ran glxgears the cpu temp went up to around the 60c mark and seemed to stay at this temp and i ran it for 30 mins

i have held the laptop to my ear and can hear the fan (it is quiet) and i can feel cool air from the cpu fan and can also fear warm air coming out of the vents. 

i am still getting the messages in the logs, but doing these checks at least put my mind at ease because isn't getting to hot. 

i did these checks using kernel 2.6.27-7-generic 
Comment 20 ykzhao 2008-10-12 07:58:13 UTC
Will you please confirm whether the boot option of "acpi.power_nocheck=1" is added after the patch set is applied?
Thanks.
Comment 21 terry gardener 2008-10-12 09:26:25 UTC
please can you read comment #15, i wasn't 100% sure where i had to add the acpi.power_nocheck=1. if this isn't correct please tell me where to add acpi.power_nocheck=1
Comment 22 ykzhao 2008-10-12 18:08:02 UTC
Hi, Terry
    "acpi.power_nocheck=1" is a boot option(kernel parameters). And it should be added to kernel cmdline parameters.
     
    From the acpidump it seems that the problem is related with your BIOS.
    >PowerResource (FN00, 0x00, 0x0000)
        {
            Method (_STA, 0, Serialized)
            {
                If (LEqual (FANS, Zero))
                {
                    Return (Zero)
                }
                Else
                {
                    Return (One)
                }
            } // the _STA method of power resource can't return the correct status of power resource

            Method (_ON, 0, Serialized)
            {
            }

            Method (_OFF, 0, Serialized)
            {
            }//bogus definition of _ON/_OFF ACPI method

     Will you please also try the two patches in http://bugzilla.kernel.org/show_bug.cgi?id=9485#C20,C21 and see whether the problem still exists?(Of course the patch set in comment #1 is still required. And they should be applied firstly. The boot option of "acpi.power_nocheck=1" is also needed).
    thanks.
    
Comment 23 terry gardener 2008-10-13 12:01:20 UTC
i have applied all 5 patches and it is still the same. however i am still confused about the acpi.power_nocheck=1 boot option and where to add it. 

there is acpi.power_nocheck=1 in the kernel-parameters.txt file. located /usr/src/linux/Documentation/kernel-parameters.txt. 

i have checked the /proc/cmdline file using gedit and it seems to be empty. 

if it is only needed in the kernel-parameters file then it is already there, infact the is 2 of these in that file. 

if you need this boot option somewhere else please can you give step by step instructions, or a site that gives step by step instructions on how to do this. 

sorry for being such a pain but this it is the very first time i have ever done this and i have only been using ubuntu and linux for just over 1 year, i have never done anything like this before. 
Comment 24 terry gardener 2008-10-13 12:31:52 UTC
after looking here about applying boot options https://lists.ubuntu.com/archives/kubuntu-users/2007-November/022241.html

i have added the boot option acpi.power_nocheck=1 and i now get a message when booting saying 

unknown boot option 'acpi.power_nocheck=1  ignoring

Comment 25 ykzhao 2008-10-13 19:07:26 UTC
Hi, Terry
   the boot option should be "acpi.power_nocheck=1" ,not " 'acpi.power_nocheck=1 ".
   Please refer to the bug 9485.
   Thanks.
Comment 26 terry gardener 2008-10-14 10:40:54 UTC
i have it as "acpi.power_nocheck=1" but without the ". but in the error it says unknown boot option 'acpi.power_nocheck=1' ignoring. 

Comment 27 ykzhao 2008-10-14 19:09:05 UTC
Please attach the output of dmesg.
Thanks.
Comment 28 terry gardener 2008-10-15 14:05:41 UTC
Created attachment 18328 [details]
dmesg file 

as requested dmesg output
Comment 29 ykzhao 2008-10-15 18:21:55 UTC
Hi, Terry
   Can you confirm whether the required patch set is applied when the boot option of "acpi.power_nocheck=1" is added?
   I tried it on my box. If the patch set is applied, there doesn't exist the following warning message when "acpi.power_nocheck=1" is added.
   >Unknown boot option `acpi.power_nocheck=1': ignoring

    Will you please try it again?
    Thanks.
Comment 30 terry gardener 2008-10-16 11:20:00 UTC
i have tried to reply the patches and it says they are already applied as follows. 

terry@terry-laptop:~$ sudo -s 
root@terry-laptop:~# cd /usr/src/linux
root@terry-laptop:/usr/src/linux# patch -Np1 < /home/terry/Documents/patch/acpi_device_debug.patch
patching file drivers/acpi/scan.c
Reversed (or previously applied) patch detected!  Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file drivers/acpi/scan.c.rej
root@terry-laptop:/usr/src/linux# patch -Np1 < /home/terry/Documents/patch/power_debug.patch
patching file drivers/acpi/power.c
Reversed (or previously applied) patch detected!  Skipping patch.
9 out of 9 hunks ignored -- saving rejects to file drivers/acpi/power.c.rej
patching file drivers/acpi/scan.c
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/acpi/scan.c.rej
root@terry-laptop:/usr/src/linux# patch -Np1 < /home/terry/Documents/patch/power_debug2.patch
patching file Documentation/kernel-parameters.txt
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file Documentation/kernel-parameters.txt.rej
patching file drivers/acpi/power.c
Reversed (or previously applied) patch detected!  Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file drivers/acpi/power.c.rej
patching file include/acpi/acpi_drivers.h
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file include/acpi/acpi_drivers.h.rej
patching file drivers/acpi/bus.c
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/acpi/bus.c.rej
root@terry-laptop:/usr/src/linux# patch -Np1 < /home/terry/Documents/patch/power_cleanup.patch
patching file drivers/acpi/power.c
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/acpi/power.c.rej
root@terry-laptop:/usr/src/linux# patch -Np1 < /home/terry/Documents/patch/power_cleanup2.patch
patching file drivers/acpi/power.c
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/acpi/power.c.rej
root@terry-laptop:/usr/src/linux# 
root@terry-laptop:/usr/src/linux# 

yes i can also confirm that the i have added the boot option acpi.power_nocheck=1 and still get message on boot up
>Unknown boot option `acpi.power_nocheck=1': ignoring

if you wish i can try reinstalling ubuntu and then the latest kernel and the patches over the weekend, but cant see it making much difference. 
Comment 31 ykzhao 2008-10-23 20:05:19 UTC
hi, terry
    I don't know where is the problem. But if you apply the patch set on the latest kernel and add the boot option of "acpi.power_nocheck=1", there should not exist the warning message. 
    >Unknown boot option `acpi.power_nocheck=1': ignoring
    
    Will you please try it again?
    Thanks.
Comment 32 terry gardener 2008-10-27 10:57:44 UTC
i reinstalled ubuntu over the weekend and installed the latest stable kernel 2.6.27.3 and then applied the first 3 patch and added the boot option and then applied the other 2 and i am still getting the message 
Unknown boot option `acpi.power_nocheck=1': ignoring
also the original error in the logs are still appearing.
Comment 33 ykzhao 2008-10-31 00:27:03 UTC
Hi, Terry
   Will you please try the latest kernel(2.6.28-rc2) and add the boot option of "acpi.power_nocheck=1"? (The patch set in comment #13 is already shipped in 2.6.28-rc1.) In such case you are not required to apply the patch set again. 
   
   After the system is booted, please check whether the problem still exists.
   If exists, please attach the output of dmesg.
   Thanks.
    
Comment 34 ykzhao 2008-11-20 23:18:52 UTC
As the patch set mentioned in comment #13 can't be applied correctly by the bug reporter and there is no response for about one month, the bug will be rejected. 
Please try the boot option of "acpi.power_nocheck=1" on the latest kernel(2.6.28-rc5) and see whether the problem still exists. If the problem still exists, please reopen this bug and attach the output of dmesg.

Thanks.

Note You need to log in before you can comment on or make changes to this bug.