Bug 199812

Created attachment 132864 [details]
dmesg output

Still happens with kernel-2.6.17-1.2617.2.1.fc6

I'm also getting the same error many times to /var/log/message.  I have an AMD
XP 3000+ (32-bit) in a Compaq Presario S6000Z, and I use Fedora Core 5 with
kernel 2.6.18-1.2200.fc5 .

Oct 21 12:52:53 z kernel: ACPI: Unable to turn cooling device [ebec0dec] 'on'
Oct 21 12:53:24 z last message repeated 73 times
Oct 21 12:54:25 z last message repeated 143 times

This is still happening with kernel 2.6.18-2869.fc6.  The machine is a Compaq
Presario SR1300NX with an Asus A7V8X-LA motherboard.  The CPU is an AMD Sempron
3000+.  I have checked and the CPU fan is running.  I went out and attached a
case fan to the only case fan power port that I could find on the motherboard,
and the fan spun up, and the message is still being sepwed to my console and
syslog.  What's really funny is the following:

Jan 14 23:10:34 leibniz kernel: ACPI: Fan [FAN] (on)
Jan 14 23:10:34 leibniz kernel: ACPI: Unable to turn cooling device [c166ddec] 'on'

These are messages from bootup, and just before it utters the 'cooling device'
message for the first time, it says that some fan is actually on.  So why in the
world is it complaining about not being able to turn it on then!?  Is acpi
complaining about trying to turn on a device that is already on?

Here is the output of acpitool -t:

  Thermal zone 1 : passi, 36 C
  Trip points : 
  ------------- 
  critical (S5):           100 C
  passive:                 -248 C: tc1=4 tc2=3 tsp=60 devices=0xc166d338 
  active[0]:               -266 C: devices=0xc166ddec 

I don't know if this matters or not, but why is the trip point that relates to
the cooling device in question (0xc166ddec) set to just a few degrees centigrade
above absolute zero?

I still see this in 2.6.20-1.2944.  I presume this is an AMD specific issue. I
have an HP Pavillion a420n, another AMD system, not a 64 bit system.  As best I
can tell the problem is harmless, but it sure is annoying when you go to a
virtual console.

I also got the same problem on a HP Pavillion a619.dk

CPU0: AMD Athlon(tm) XP 3000+ stepping 00

lot of dmesg spam 
ACPI: Unable to turn cooling device [c1587dec] 'on'

Workaround available here:

http://www.centos.org/modules/newbb/viewtopic.php?topic_id=8158

The problem persists on the latest Fedora 7 i386.  I also have an AMD Athlon XP
3000+.

Linux z.localdomain 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
athlon i386 GNU/Linux

2.6.23.1-10 should be out any say now, and is in koji now:

http://koji.fedoraproject.org/koji/buildinfo?buildID=21666

Still happens with

kernel-2.6.23.1-37.fc8

Does the workaround in comment #7 work?

This is probably a BIOS problem, all we can do is work around it.

kernel-2.6.23.1-41.fc8 strangely seems not to display this behaviour.. which is
mighty strange since nothing that should affect this has changed in between
those two kernels.

Very odd. 

I have a machine that I upgraded to F7 a bit before F8 came out.  When I first
upgraded, the kernel was kernel-2.6.21-1.3194.fc7.  The workaround in comment #7
where you echo a string of trip points into
/proc/acpi/thermal_zone/THRM/trip_points fixed that kernel.  However, when I
upgraded to kernel-2.6.23.1-21.fc7, I received the error:

echo: write error: Input/output error

whenever I try to echo values into that file now.  It seems as though that file
was made read-only in the kernel between 2.6.21 and 2.6.23.1.  I will need to
see what happens when I upgrade to F8.

Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

This continues to happen on F-8 and devel. Workaround does not work

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

This continues on 2.6.25.6-55.fc9.i686

This bug is present and easily reproduced with a system we have running RHEL 5.2. Please note that this needs to be fixed in the RHEL 5.x stream.

The system we see it on is an Aopen DE-965HG, which is a tiny box built on mobile componentry and which draws very little power. Nice test boxes, and nice remote servers to collect data, store and transmit. Inexpensive, too.

There is a patch to fix this issue, which is already in Andi's ACPI test tree.
Please refer to
http://bugzilla.kernel.org/show_bug.cgi?id=11000
comment #30 #31 #32.
please give them a try.

Thanks for the heads-up. Hopefully this will be wrapped into the next RHEL 5.x maint. I'm presently running a test kernel on the same box to deal with a Realtek Ethernet issue, so I'm not in a good position to roll in this fix right now. I am hoping both will make it into a bug fix patch to RHEL 5.2, and in releases beyond.

It's baaack....

leibniz_1001% rpm -q kernel
kernel-2.6.27.5-117.fc10.i686
kernel-2.6.27.21-170.2.56.fc10.i686
leibniz_1002% uname -a
Linux leibniz 2.6.27.21-170.2.56.fc10.i686.PAE #1 SMP Mon Mar 23 23:24:26 EDT 2009 i686 athlon i386 GNU/Linux
leibniz_1003% dmesg | tail -20
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'

This seems to be the latest F10 kernel, 2.6.27.21-170.2.56.

This issue is also still happening in the RHEL release chain. The latest RHEL 5.3 kernel spews these messages. A work around or fix really would be appreciated, especially in the RHEL chain.

boot option "acpi.power_nocheck=1" doesn't work any more?

Are you suggesting that setting acpi.power_nocheck=1 is a work-around for this bug? If so, please explain, provide references or other. This particular bug report goes back 3 years, and this is the first mention of this boot option.

A quick test on a system exhibiting the behavior showed no change when this boot option was added.

Output of acpitool on my system exhibiting the behavior:

# acpitool -t
  Thermal zone 1 : passi, 65 C
  Trip points : 
  ------------- 
  critical (S5):           200 C
  passive:                 50 C: tc1=4 tc2=3 tsp=60 devices=0xffff8800012372b0 
  active[0]:               50 C: devices=0xffff880000f7b990

(In reply to comment #23)
> boot option "acpi.power_nocheck=1" doesn't work any more?  

It doesn't seem to yet:
leibniz_1005% dmesg | tail
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
ACPI: Unable to turn cooling device [eb815f18] 'on'
leibniz_1006% cat /proc/cmdline
ro root=UUID=bd8c223b-daf4-4636-97bf-8a3ea838b87d rhgb acpi.power_nocheck=1
                                                       ^^^^^^^^^^^^^^^^^^^^
leibniz_1007% uname -a
Linux leibniz 2.6.27.21-170.2.56.fc10.i686 #1 SMP Mon Mar 23 23:37:54 EDT 2009 i686 athlon i386 GNU/Linux

Now looking at the URL in comment #19, it would appear that the patch for the above kernel command line option was committed to kernel 2.6.28-rc1, whereas the current kernel version is 2.6.27.21.  So we might have to wait until we have a 2.6.28 kernel before we see any relief for this bug.

(In reply to comment #25)
> Output of acpitool on my system exhibiting the behavior:
> 
> # acpitool -t
>   Thermal zone 1 : passi, 65 C
>   Trip points : 
>   ------------- 
>   critical (S5):           200 C
>   passive:                 50 C: tc1=4 tc2=3 tsp=60 devices=0xffff8800012372b0 
>   active[0]:               50 C: devices=0xffff880000f7b990  

Here is the output on my system:

leibniz_1008% acpitool -t
  Thermal zone 1 : passi, 39 C
  Trip points : 
  ------------- 
  critical (S5):           100 C
  passive:                 -248 C: tc1=4 tc2=3 tsp=60 devices=CPU0 
  active[0]:               -266 C: devices= FAN 

Note the temperatures that are approaching absolute zero.

One fix that was given all the way back in the URL in comment #7 seemed to indicate that at one time, you could simply echo trip points that were more sane into /proc/acpi/thermal_zone/THRM/trip_points.  At one time, this workaround did seem to work.  However, it stopped working when that file was made read-only.  Does anyone know why the trip_points file was made read-only and why the trip points seem to be reading so ridiculously low?

This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

cc Yakui

Someone please update version to F10.  I have this message 2371 times in dmesg on 2.6.27.19-170.2.35.fc10.i686

Or just move it over onto RHEL 5.3, as it still happens there.

The AMD64 machine that displayed this problem has since ended it's life in a tragic io controller and mobo related suicide. Luckily it seems others are capable of reproducing this now.

i have 2 machines making this error

http://www.smolts.org/client/show/pub_9efe092f-fb6c-41e6-abf3-bc76f72473c0
running Fedora 11.

http://www.smolts.org/client/show/?uuid=pub_899d8fc9-0d4d-4b81-8a28-5650d55881e9
running Fedora 10

http://www.smolts.org/client/show/?uuid=pub_899d8fc9-0d4d-4b81-8a28-5650d55881e9

this one is reported in this one

https://bugzilla.redhat.com/show_bug.cgi?id=470796

Hi
   Will you please try the latest kernel(2.6.30-rc7) and see whether the issue still exists?
   IMO this issue is related with the broken BIOS. OS will verfity the power state again in course of power device transition. If it is not the expected power state, it will complain the above the warning message.
   
   This issue can be fixed by adding the boot option of "acpi.power_nocheck=1" since the 2.6.28 kernel.
   
   Please try it and see whether it still exists. Thanks

The issue still exists in 2.6.29.6-213.fc11.i586 (no special boot options tested).

my Compaq Presario s6500nx has been stuck at 'loading' fc11 for a month now (soon after upgrade) with just the heavy white line across the bottom.  been using dell d600 meanwhile, but really need to get this one working again.  linux newbie here, just figured out to hit 'esc' and I see now it appears 'hung' with perpetual ...
acpi: unable to turn cooling device [f6c63f18] 'on'
acpi: unable to turn cooling device [f6c63f18] 'on'
acpi: unable to turn cooling device [f6c63f18] 'on'
acpi: unable to turn cooling device [f6c63f18] 'on'
(never stops this; won't boot)
h-e-l-p-!!  please say how/where to edit what, remember I'm green - thanks much

SOMEBODY???  ANYBODY???  It's been 15 days since I reported this.  Really need to get my Compaq working again.  HELP??

faith: I am 90% sure the ACPI messages are unrelated (they don't cause the symptom of not being able to start the system), so you need to focus somewhere else.

yakui.zhao:
>This issue can be fixed by adding the boot option of "acpi.power_nocheck=1"
>since the 2.6.28 kernel.

Tested, but I still get the message.  From grub:

kernel /boot/vmlinuz-2.6.29.6-217.2.16.fc11.i586 ro root=UUID=c2969cdd-a078-4dce-abba-d3b10e191cd8 rhgb quiet acpi.power_nocheck=1

After three years and 13 kernel releases, finally seems OK in 2.6.30.5-43.fc11.i586 :)

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.