ACPI: Unable to turn cooling...

Bug #63550 reported by Enrico Sardi
64
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned
linux-source-2.6.17 (Ubuntu)
Won't Fix
Medium
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: acpi

Hi at all!

I have the following message in dmesg:

ACPI: Unable to turn cooling device [cf7d2748] 'on'

It's written several times in the log...it's right?

(My laptop is an Asus 2420)

Bye

Enrico

Revision history for this message
Simon Law (sfllaw) wrote :

Hi Enrico,

If you add "fan" to the end of your /etc/modules file, does this log message disappear?

Changed in linux-source-2.6.17:
assignee: nobody → sfllaw
status: Unconfirmed → Needs Info
Revision history for this message
Enrico Sardi (enricoss) wrote :

I've tried it but the message is still present....

Bye

Enrico

Revision history for this message
Enrico Sardi (enricoss) wrote :

This is my dmesg output...

Bye

Enrico

Revision history for this message
bobo (bobobilly) wrote :

Hey, I'm getting the same thing. It is writing:

"ACPI: Unable to turn cooling device [dbfdfdec] 'on'"

EVERY SIX SECONDS!!!!!

My log files are HUGE!!!

I did some searching and I found that it is coming from a file called 'thermal.c'. (try using google code search). I also found this being talked about in other distro forums but no one seems to have an answer.

Any help would be nice.

Thanks

Revision history for this message
Simon Law (sfllaw) wrote :

The line that says "ACPI: Invalid PBLK length [5]" is our hint here.

The FreeBSD people seem to have fixed this in their ACPI implementation. From http://www.freebsd.org/projects/acpi/completed.html, Nate Lawson writes:

"Invalid PBLK length workaround -- Accept a PBLK of length 5 (spec says 6). Only enable C2 for this though. Some people may be using 7 to indicate another C3 state but we do not support the extra state."

Changed in linux-source-2.6.17:
assignee: sfllaw → nobody
importance: Undecided → Medium
status: Needs Info → Confirmed
Revision history for this message
Arisna (arisna) wrote :

I am experiencing the same issue on a HP Pavilion a706n with kernel version 2.6.17-10. The error message prints every six seconds.

Searching /var/log/dmesg for "PBLK" turned up nothing for me, but I've attached said file.

Previously, I had filed a support request for this issue through a misguided conception of how Launchpad works. It can be found here: https://answers.launchpad.net/ubuntu/+ticket/2935

To summarize that support request, the message is printing even though my fans are running appropriately. Also, the problem seems to affect Fedora as well, judging by discussions I've read elsewhere, so the bug is likely upstream. Also, I tried unloaded the "thermal" module from my kernel temporarily, and that stopped the errors, but it probably isn't safe to leave that module unloaded. Finally, another user mentioned that he solved this problem on his system by flashing his BIOS, but that is not a viable option for many users.

Revision history for this message
Enrico Sardi (enricoss) wrote :

as requested I posted my dmidecode output. The bug is still present in Edgy final... When I can I'll try with Feisty Herd 2 too....

Bye

Enrico

Revision history for this message
Enrico Sardi (enricoss) wrote :

I tried feisty herd 2 and the bug is still present.

Bye

Enrico

Kyle McMartin (kyle)
Changed in linux-source-2.6.20:
status: Unconfirmed → Confirmed
Tim Gardner (timg-tpi)
Changed in linux-source-2.6.20:
assignee: nobody → timg-tpi
Revision history for this message
Ben Collins (ben-collins) wrote :

Confirmed bugs need to be assigned to ubuntu-kernel-team.

Changed in linux-source-2.6.20:
assignee: timg-tpi → ubuntu-kernel-team
importance: Undecided → Medium
Changed in linux-source-2.6.17:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Renjoy (renjoy) wrote :

If any one needs more information on this please let me know, because I have the same issue. I started seeing this after 2.6.17 kernel version. With 2.6.16 I have never seen this. And its there in all distro not just Ubuntu. I have the latest version of Feisty installed with kernel 2.6.20-12, but I still see them.

ACPI: Unable to turn cooling device [e6c34dec] 'on'

Tim Gardner (timg-tpi)
Changed in linux-source-2.6.20:
assignee: ubuntu-kernel-team → ubuntu-kernel-acpi
Revision history for this message
Serge Maneuf (lsmaneuf) wrote :

Same bugg, since migration from dapper to edgy.
Desktop HP pavillion a629.fr

I recently try two fresh installs of Ubuntu 6.06LTS and 7.04 beta :
The message is not there under 6.06LTS
The message is there under 7.04 beta.

Attached dmesg in both cases.

Revision history for this message
Serge Maneuf (lsmaneuf) wrote :
Revision history for this message
Jonathan Métillon (jmetillon) wrote :

Hi,

Same issue here, my log is filling with:

ACPI: Unable to turn cooling device [eace1dec] 'on'

I use Ubuntu Feisty Fawn 7.04 Beta on a Desktop HP pavillion a429.fr, and fans seems to work nicely.

Revision history for this message
bitshifter (bit-shifter52) wrote :

My Linux Mint box has the same message that reappears every six seconds:

Apr 4 19:22:28 Robert-linux kernel: [17180383.936000] ACPI: Unable to turn cooling device [dffeddec] 'on'

This line appears in syslog, messages, and kern.log...

All my fans are turning swiftly and smoothly.

Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

Same here,

I got this message while fans are running fine.

With feisty, 2.6.20-15-generic, on a Toshiba Satellite Pro A100

Revision history for this message
yamo (stephane-gregoire) wrote :

Hi,

I use Feisty ( Linux version 2.6.20-16-386 (root@terranova) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 Thu Jun 7 20:16:13 UTC 2007 (Ubuntu 2.6.20-16.29-386) ) and I have troubles with my system.

it's on ACER desktop Aspire T310 with Intel(R) Celeron(R) CPU 2.80GHz

Revision history for this message
yamo (stephane-gregoire) wrote :

Hi I suppressed powernowd and I haven't this message but I don't know if the trouble is solved I will know that tomorrow!

Revision history for this message
Divilinux (divilinux) wrote : Re: [Bug 63550] Re: ACPI: Unable to turn cooling...

Powernowd is now buggy..try cpufreqd or , better, powersaved
;)

2007/8/7, yamo <email address hidden>:
>
> Hi I suppressed powernowd and I haven't this message but I don't know if
> the trouble is solved I will know that tomorrow!
>
> --
> ACPI: Unable to turn cooling...
> https://bugs.launchpad.net/bugs/63550
> You received this bug notification because you are a member of Ubuntu
> Kernel ACPI Team, which is a bug assignee.
>

--
Ubuntu-it

Revision history for this message
yamo (stephane-gregoire) wrote :

Hi,
I tryed powersaved but It don't work with my celeron.

Aug 14 10:52:44 yamo powersaved: Loading speedstep_centrino
Aug 14 10:52:44 yamo powersaved: enter 'speedstep_centrino' into CPUFREQD_MODULE in /etc/powersave/cpufreq.
Aug 14 10:52:44 yamo powersaved: this will speed up starting powersaved and avoid unnecessary warnings in syslog.
Aug 14 10:52:44 yamo powersaved: Cannot load cpufreq governors - No cpufreq driver available
Aug 14 10:52:44 yamo powersaved: Starting powersaved with ACPI support

If I use speedstep_centrino It says I haven't this on my kernel 2.6.20...

I will wait 2.6.23 in october!

Revision history for this message
Divilinux (divilinux) wrote :

speedstep_centrino i think is not present yet in kernel 2.6.20..
i have nothing in CPUFREQ_MODULE="" but the must important thing is setting

CPUFREQ_CONTROL="userspace"

to point kernel_modules to be used with a normal program in userspace
Sometimes inserting nolapic or noapic for linux to boot may deactivate the
cpu_scaling...do u boot with those parameters?

2007/8/14, yamo <email address hidden>:
>
> Hi,
> I tryed powersaved but It don't work with my celeron.
>
> Aug 14 10:52:44 yamo powersaved: Loading speedstep_centrino
> Aug 14 10:52:44 yamo powersaved: enter 'speedstep_centrino' into
> CPUFREQD_MODULE in /etc/powersave/cpufreq.
> Aug 14 10:52:44 yamo powersaved: this will speed up starting powersaved
> and avoid unnecessary warnings in syslog.
> Aug 14 10:52:44 yamo powersaved: Cannot load cpufreq governors - No
> cpufreq driver available
> Aug 14 10:52:44 yamo powersaved: Starting powersaved with ACPI support
>
> If I use speedstep_centrino It says I haven't this on my kernel
> 2.6.20...
>
> I will wait 2.6.23 in october!
>
> --
> ACPI: Unable to turn cooling...
> https://bugs.launchpad.net/bugs/63550
> You received this bug notification because you are a member of Ubuntu
> Kernel ACPI Team, which is a bug assignee.
>

--
Ubuntu-it

Revision history for this message
Matthew Garrett (mjg59) wrote :

Celerons do not have frequency scaling support.

Revision history for this message
yamo (stephane-gregoire) wrote :

Hi,

Matthew Garrett a écrit , le 15.08.2007 10:42:
> Celerons do not have frequency scaling support.
>
I know that but I doesn't understood why this message appear in my logs.

I 've edited my /etc/powersave/thermal file and now it's work fine! :

COOLING_POLICY="active"
THERMAL_POLLING_FREQUENCY="2000"
THERMAL_CRITICAL_0="92"
THERMAL_HOT_0="90"
THERMAL_PASSIVE_0="35"
THERMAL_ACTIVE_0_0="40"
THERMAL_ACTIVE_0_1="42"

I've also this in my /proc/acpi/thermal_zone/THRM/trip_points file

critical (S5): 90 C
passive: 80 C: tc1=4 tc2=3 tsp=60 devices=0xc1936338
active[0]: 35 C: devices=0xc193e810

--
Stéphane
Sorry for my bad english

Revision history for this message
yamo (stephane-gregoire) wrote :

Hi,
Does this bug is solved in 2.6.22?

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

I've had one or two of these per-boot on previous versions, but I'm seeing this more on hardy (2.6.24-15-generic);
I've got about 20 of these in a row in a second or two in the logs:

[ 871.568649] ACPI: Transitioning device [FAN0] to D0
[ 871.568655] ACPI: Transitioning device [FAN0] to D0
[ 871.568658] ACPI: Unable to turn cooling device [ffff8100baa96dc0] 'on'

This is a Toshiba Equiuum A100-306 with a Core2 Duo;
here is the head of dmidecode:

# dmidecode 2.9
SMBIOS 2.31 present.
36 structures occupying 1129 bytes.
Table at 0x000DC010.

Handle 0x0000, DMI type 0, 20 bytes
BIOS Information
 Vendor: Phoenix Technologies LTD
 Version: 2.10
 Release Date: 10/23/2006
 Address: 0xE4140
 Runtime Size: 114368 bytes
 ROM Size: 1024 kB

This is an upgrade from Gutsy.

Revision history for this message
yamo (stephane-gregoire) wrote :

Hi,
I Have this bug on Ubuntu Gutsy after going back a "Mise en veille" (hibernate on memory?).
After a normal boot there's no bug.

Sorry for my bad english.

In dmesg there's many of :
[ 8450.404012] ACPI: Unable to turn cooling device [df841a38] 'off'
[ 8452.400261] ACPI: Unable to turn cooling device [df841a38] 'off'
[ 8454.396505] ACPI: Unable to turn cooling device [df841a38] 'off'
[ 8456.392748] ACPI: Unable to turn cooling device [df841a38] 'off'
[ 8458.388992] ACPI: Unable to turn cooling device [df841a38] 'off'

Revision history for this message
yamo (stephane-gregoire) wrote :

Hi,
After an upgrade from gutsy to hardy the bug is resolved :)

Revision history for this message
Ben Scott (dragonhawk) wrote : I'm seeing this on kernel 2.6.24 on Hardy

Just finished an install of Ubuntu 8.04 Hardy Heron, and I'm seeing this same issue. The kernel is logging the following every six seconds:

Apr 27 21:28:58 sunshine kernel: [ 1353.176717] ACPI: Unable to turn cooling device [d9dcff18] 'on'

This is with kernel 2.6.24-16-generic. No updates have been released for Hardy as of this writing. (First time I've tried Linux on this hardware, so I don't know if issue presents on this hardware with older software.)

Hardware is an HP Pavilion a635w desktop, which uses an Asus A7V8X-LA motherboard with a VIA KM400 chipset. I've got the latest BIOS from HP installed. Power supply, chassis, and CPU fan are all spinning.

If I rmmod the "thermal" module, log messages cease; if I insmod it again they start up again.

No match for "PBLK" in any of the /var/log/{dmesg,messages,kern.log} files. In an eyeball review, nothing leaps out at me for an obvious cause, but I'm no expert at ACPI. I'll attach dmesg and dmidecode output. If there's anything more I can do to assist, please let me know.

Revision history for this message
Ben Scott (dragonhawk) wrote : dmidecode output for previous comment
Revision history for this message
Serge Maneuf (lsmaneuf-orange) wrote :

I have exactly the behaviour described above by Ben Scott with HP Pavilion a629.fr desktop.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Ben, thanks for the log files against Hardy. I'm reassigning to the kernel team for further investigation.

There was also a comment previously that a BIOS update might help resolve this issue. Just curious if anyone has tried this?

I'm also reassigning this to the "linux" source package since beginning with the Hardy development cycle kernel bug should be reported against the "linux" package instead of linux-source-2.6.24. Also, unfortunately the 2.6.17 Edgy kernel has reached it's end of life for the 18 month support period so against the 2.6.17 kernel this will be closed. Thanks.

Changed in linux-source-2.6.24:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Triaged
Changed in linux-source-2.6.17:
status: Confirmed → Won't Fix
Revision history for this message
Ben Martin (bcmartin) wrote :

Just to add to the chorus, I've got an identical problem. I have an HP Pavilion a620n computer with the most recent (3.15) bios. I don't know if it was a problem before, but it's definitely in Ubuntu 8.04.

Revision history for this message
Jason Costomiris (jcostom) wrote :

Just my $0.02, adjusted for inflation.. Here's a terminal log including my dmesg, acpitool -e and dmidecode output. Running 2.6.24-19-server x86_64 on a Core 2 Quad Q6700 (2.66 Ghz), 8GB RAM. The system is a Shuttle XPC SP35P2 Pro, with the latest BIOS.

Hardy Server x86_64 edition. latest kernel (2.6.24-19-server), as noted above.

Despite the presence of vmware kernel messages - this is the host system, not a VM. Further these messages were appearing prior to the install of vmware on the system...

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
yamo (stephane-gregoire) wrote :

Hi,

I've just tried Ubuntu 8.10 alpha 4 :

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 2.6.26-5-generic #1 SMP Sun Aug 10 20:30:28 UTC 2008 i686 GNU/Linux
ubuntu@ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu intrepid (development branch)
Release: 8.10
Codename: intrepid

Gnome : 2.23.6

And it's like on hardy heron there's no bug on my PC. :)

Revision history for this message
Harbinger (saedaen) wrote :

Posted this a little bit ago under " (undecided) Bug 179729: unable to turn cooling device on" at https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/179729
-----------------------
        Just did a clean install of Heron on my HP Pavilion a620n and i'm getting

Sep 4 17:01:42 HPclunker kernel: [ 18.772106] ACPI: Unable to turn cooling device [dddd1f18] 'on'

every 6 sec in my kern.log, messages, and syslog sections of the system log viewer. Yes, all the fans are on and working just fine. I did a clean install because i was originally getting this in Heron so i upgraded to Ibex and was still getting the same ACPI fan message (diff address).

I went ahead and attached a txt file of the messages log from the first boot after the clean install. I've run the updates since then and still getting same message spam.

I'm going to upgrade to Ibex (again) and see if the problem persists.

Sep 4 17:01:42 HPclunker kernel: [ 18.763983] ACPI: Fan [FAN] (on)
Sep 4 17:01:42 HPclunker kernel: [ 18.772106] ACPI: Unable to turn cooling device [dddd1f18] 'on'
makes me sad
--------------------------

Since then i've upgraded to Ibex and the still getting same fan message.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks for the testing everyone.

Harbinger, can you actually attach your dmesg output from when running the 2.6.27 kernel for Intrepid?

Enrico Sardi, since you are the original bug reporter, we seem to have conflicting feedback so far. Would you be able to test if this is still and issue for you with Intrepid? Alpha5 just came out last week so you should be abel to test with a LiveCD - http://www.ubuntu.com/testing/intrepid/alpha5 . Thanks.

Revision history for this message
Harbinger (saedaen) wrote :

Just finished reinstalling per your request. I'd also like to note that i did swap out my cpu fan with another one i had lying around and still same message.

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Yep, also still seeing in Intrepid (Tosh Equium A100-306):

[ 2.592189] ACPI: CPU1 (power states: C1[C1] C2[C2])
[ 2.592249] processor ACPI0007:01: registered as cooling_device2
[ 2.592253] ACPI: Processor [CPU1] (supports 8 throttling states)
[ 2.598177] ACPI: Thermal Zone [TZ00] (42 C)
[ 2.610868] ACPI: Transitioning device [FAN0] to D0
[ 2.610871] ACPI: Unable to turn cooling device [ffff8800bee31e20] 'on'
[ 2.610875] ACPI: Thermal Zone [TZ01] (45 C)

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The 18 month support period for Feisty Fawn 7.04 has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result, we are closing the linux-source-2.6.20 kernel task. However, this will remain open against the actively developed kernel. Thanks.

Changed in linux-source-2.6.20:
status: Confirmed → Won't Fix
Revision history for this message
Jason Costomiris (jcostom) wrote :

Installing Intrepid now on the machine I've had this trouble with - a Shuttle XPC.

Still seeing "Unable to turn cooling device [ffff88022f05dbe0] 'on'"

Message hit the console during install every 6 seconds. Now that the system is booted normally, same deal, every 6 seconds, I get that message.

After post-install updates, same deal.

Revision history for this message
Mark Freeman (markfrman) wrote :
Download full text (3.3 KiB)

I am having this issue with Intrepid. Current updates applied as of 11/27/2008 10pm est.
The processor is a Core2Duo E7200. The motherboard is a Foxconn G31AXK. The fans are working and are set to be permanently ON.

uname -a
Linux quasar 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64 GNU/Linux

dmesg output is attached.

Fan throttling via ACPI is DISABLED in the bios but ACPI in the kernel seems unaware of this. Also the temperatures read by ACPI are totally wrong and the attempts at starting the fans (which are always running) are totally unnecessary. Actual processor temps are in the low 30's C but the temps being read are 183C - constantly.

 more /proc/acpi/fan/FAN/state
status: on

more /proc/acpi/thermal_zone/THRM/*
::::::::::::::
/proc/acpi/thermal_zone/THRM/cooling_mode
::::::::::::::
0 - Active; 1 - Passive
::::::::::::::
/proc/acpi/thermal_zone/THRM/polling_frequency
::::::::::::::
<polling disabled>
::::::::::::::
/proc/acpi/thermal_zone/THRM/state
::::::::::::::
state: passive
::::::::::::::
/proc/acpi/thermal_zone/THRM/temperature
::::::::::::::
temperature: 183 C
::::::::::::::
/proc/acpi/thermal_zone/THRM/trip_points
::::::::::::::
critical (S5): 232 C
passive: 50 C: tc1=4 tc2=3 tsp=60 devices=CPU0
active[0]: 50 C: devices= FAN

Its really stupid. I dont know where ACPI is getting these numbers for current and critical temp either. The BIOS is not reporting inaccurate temps in the display and the system runs cool with no instability that would accompany such drastically high temps. The processor would not be destroyed running at that temp. The bios is also configured to shutdown at some high double digit celsius value - cant recall offhand what I set it to.

I have removed and blacklisted thermal due to this bug. Not something I should have to do.

My processor also has one core being slowed for no apparent reason. Im not sure if this is related. Could this be a BIOS compatibility issue?

 cpufreq-info
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 1.60 GHz - 2.53 GHz
  available frequency steps: 2.53 GHz, 1.60 GHz
  available cpufreq governors: powersave, userspace, ondemand, conservative, performance
  current policy: frequency should be within 1.60 GHz and 1.60 GHz.
                  The governor "userspace" may decide which speed to use
                  within this range.
  current CPU frequency is 1.60 GHz.
analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 1
  hardware limits: 1.60 GHz - 2.53 GHz
  available frequency steps: 2.53 GHz, 1.60 GHz
  available cpufreq governors: powersave, userspace, ondemand, conservative, performance
  current policy: frequency should be within 1.60 GHz and 2.53 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1.60 GHz.
----------
The current policy freq range for...

Read more...

Revision history for this message
Mark Freeman (markfrman) wrote :

Problems with cpu throttling and thermal module are gone with the latest update to the kernel 2.6.27-9. The problems with Thermal continue if I load it but it seems to be left out - not sure if this is because I blacklisted it, although blacklisting it did nothing in subsequent reboots prior to the kernel update.
The cpu being locked into its lowest setting is fixed though. I wish I knew specifically what was causing these issues.If it wasnt for this update I would be stuck. I can't turn off acpi in the BIOS and retain frequency scaling in the OS.

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

I have the same problem on a Shuttle PC K45

dmesg gives:

[ 4346.132237] ACPI: Unable to turn cooling device [f7418738] 'on'
[ 4352.132250] ACPI: Unable to turn cooling device [f7418738] 'on'
[ 4358.132229] ACPI: Unable to turn cooling device [f7418738] 'on'
[ 4364.132245] ACPI: Unable to turn cooling device [f7418738] 'on'

uname -a -p -i:

Linux aurora 2.6.27-11-generic #1 SMP Fri Dec 19 16:29:52 UTC 2008 i686 GNU/Linux.

Shuttle PC K45 has 5 speed settings for the CPU fan:
Auto
Very low
Low
Medium
High

Setting the speed to Auto makes the Ubuntu reset all the time probably due to overheating (when the processor is in use for extended period of time of 1-2 minutes)

The processor in use is Celeron 420.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Greg Toombs (greg-toombs) wrote :

This "unable to turn fan on" has been happening on my Toshiba A100 since day one with Ubuntu, and still occurs with the newest BIOS and Intrepid. dmesg attached.

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

I am just wondering if this has anything to do with this problem. Few days ago I installed sensors-applet on my system. In order for it to work properly (with all available sensors on the system), I also had to install the lm-sensors package.

I followed the instructions from https://help.ubuntu.com/community/SensorInstallHowto

It says there that after installing lm-sensors, you have to run:

 sudo sensors-detect

The interesting part is that after sensors-detect added some modules to my /etc/modules the

ACPI: Unable to turn cooling device [f7418738] 'on'....

messages disappeared.

Can anyone try this on his PC and see if that works for him too?

Revision history for this message
hummerbliss (hummerbliss) wrote :

The problem is still present in 2.6.27-11-generic on Ubuntu 8.10 as of today. Will be glad to provide any further information.
Can anybody tell me problems with not turning cooling device on ?

Petar Velkovski - Tried, and from what I observe the messages disappear only for some time and appear again.

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

hummerbliss - Go to Administration->Services and check the status of lm-sensors service. Somehow it got deactivated at my computer and I started getting the same messages. I activated it again and now the messages disappeared again.
But I am not certain that automatic speed adjustment works at my computer(set as an option in the BIOS), because it seams that my cooler tends to run faster on higher temperatures as if it regulates itself without external regulation.

Revision history for this message
hummerbliss (hummerbliss) wrote :

Petar Velkovsi - the lm-sensors service is turned on on my services list, but still no luck.

Revision history for this message
Jason Costomiris (jcostom) wrote :

This problem disappeared for me sometime while I was running Intrepid. Now that I've done the upgrade to jaunty, it's back.

I upgraded via the "do-release-upgrade" method.

The precise message is:

Apr 26 10:34:46 arwen kernel: [54142.600473] ACPI: Unable to turn cooling device [ffff88022f81abc0] 'on'

It occurs every 6 seconds, just like everyone else is seeing. In my boot messages, I see:

Apr 25 19:32:41 arwen kernel: [ 1.615740] thermal LNXTHERM:01: registered as thermal_zone0
Apr 25 19:32:41 arwen kernel: [ 1.615984] ACPI: Unable to turn cooling device [ffff88022f81abc0] 'on'
Apr 25 19:32:41 arwen kernel: [ 1.616017] ACPI: Thermal Zone [THRM] (51 C)

acpitool -t gives:

[arwen:jcostom](10:36 AM)
/home/jcostom$ acpitool -t
  Thermal zone 1 : passive, 55 C
  Trip points :
  -------------
  critical (S5): 60 C
  passive: 50 C: tc1=4 tc2=3 tsp=60 devices=CPU0
  active[0]: 50 C: devices= FAN

lm-sensors is also both present and started.

Revision history for this message
Robert Frankel (frankelrs-gmail) wrote :

I did a clean install of Jaunty on 5/5/2009

All seems to function except that I get the same "ACPI Unable message that others have reported

I had this problem with 8.10 and "fixed it" since all fans and temperature on the computer
appear ok by removing the thermal module. Jaunty does not seem to have a thermal module. Any help in killing the log file message

Bob

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

I'm seeing a different symptom in Karmic 2.6.30-5 #6 ; I see quote a lot of

[67420.586325] ACPI: Transitioning device [FAN0] to D0
[67485.450855] ACPI: Transitioning device [FAN0] to D0
[67508.277048] ACPI: Transitioning device [FAN0] to D0
[67522.125350] ACPI: Transitioning device [FAN0] to D0

in the logs - as you can see they are every few minutes.

I do wonder if this is related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/352762
where my fan doesn't turn on/off unless I do an acpi -t
I now have a 'watch acpi -t' running in a terminal in the background.

(Toshiba Equium A100-306 laptop, pheonix bios)

Dave

Revision history for this message
Mathew Hennessy (ubuntu-unixslave) wrote :

I'm getting this error too in jaunty, attaching some output..

Revision history for this message
Tom McK (tommck) wrote :

I am having the same issue on a Jaunty Mythbuntu install:

$ uname -a
Linux genie2 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 19:49:51 UTC 2009 i686 GNU/Linux

I attached output from acpitool -e and dmidecode...

Revision history for this message
Greg Toombs (greg-toombs) wrote :

Not only has this bug persisted through every version of Ubuntu I've had, it's in my current Gentoo installation as well, so it's almost definitely an upstream problem for the kernel people.

Revision history for this message
Mitchell Surface (msurface) wrote :

The problem may well have existed for a long time but the solution that used to work, now doesn't. You used to be able to rmmod the thermal module and the problem would stop. Thermal is no longer a module so that doesn't work. I very much doubt the kernel people dictate what Ubuntu builds into the kernel or as a module.

Revision history for this message
Greg Toombs (greg-toombs) wrote :
Revision history for this message
Jason Costomiris (jcostom) wrote :

My solution (until I attempt the solution in Greg's bug report) for now has been to move to syslog-ng and add a filter to dump this message:

filter f_acpierror { not match("ffff88022f81abc0"); };

Then insert filter(f_acpierror); in the log {} stanza for destination(df_messages).

At my next reboot, I'll try out the solution that was suggested for Greg...

Revision history for this message
Michael Carpenter (mcarpent) wrote :

Looks like Greg's upstream bug got marked as invalid....

http://bugzilla.kernel.org/show_bug.cgi?id=13989
and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/354085

Both suggest the following boot option:
acpi.power_nocheck=1

I am going to test it tonight for my own issue.

- Michael

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
wlraider70 (wlraider70) wrote :

This bug still plagues me.

in 9.10.

Jun 12 22:13:04 media kernel: [ 847.292865] ACPI: Unable to turn cooling device [f6c2af18] 'on'
(repeat)

let me know if you need more details.

Revision history for this message
Divilinux (divilinux) wrote : Invito a collegarsi su LinkedIn

LinkedIn
------------

Bug,

Vorrei aggiungerti alla mia rete professionale su LinkedIn.

-nicola

nicola crupi
Libero professionista Internet
Maceió Area, Brazil

Conferma che conosci nicola crupi
https://www.linkedin.com/e/-22i0gj-gnvtftoz-n/isd/2935367187/pp3mk30r/

--
(c) 2011, LinkedIn Corporation

Curtis Hovey (sinzui)
Changed in linux-source-2.6.20 (Ubuntu):
assignee: Registry Administrators (registry) → nobody
Revision history for this message
dino99 (9d9) wrote :

This version has expired

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.