fan never turns off

[nfusi]

I have a HP zd7395ea laptop, running on a P4 3.6ghz cpu.

Linux xxxxxx 2.6.24-17-generic #1 SMP Thu May 1 14:31:33 UTC 2008 i686 GNU/Linux

Even after a cold start, the fan starts up and does not turn off until I shutdown. The cpu temp after a cold start should be 43 C, but it's actually 56 C.
This problem does not happen with the previous kernel (2.6.22) or windows, it happens only with the hardy kernel (2.6.24-17).

I have experienced this bug even with a vanilla 2.6.24 kernel.

Steps to reproduce: turn on the laptop, wait until the kernel is loaded

WORKAROUND: Turning off acpi (by passing acpi=off at boot) "solves" the problem.

[Leann Ogasawara (leannogasawara)]

There hasn't been any recent activity in this bug report and we were wondering if this is still an issue? The Ubuntu kernel team is actively working on the upcoming Intrepid Ibex 8.10 release. If you could please test the latest Alpha release for Intrepid it would be much appreciated - http://www.ubuntu.com/testing . Please let us know your results. If the issue still exists, please also provide the appropriate debugging information as outlined at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance.

[Leann Ogasawara (leannogasawara)]

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.

[Tomas M. (el-dragon)]

ive got this problem too, but its intermittent.

my notebook is an everex stepnote sa2053.

im attaching lsmods dmesg and whatnot with and without fan control, it might prove useful.

one tiny bit of info i should add is: im running a slightly patched kernel to fix the following bug, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187671 but the issue is present with the latest kernel as its on my patched version (patch has been attached to the bug linked if it needs review.

[Tomas M. (el-dragon)]

now attaching lsmod when fan does not work

[Tomas M. (el-dragon)]

i can confirm this is the case with linux kernel 2.6.27-7

[matt goto (hikuiishi)]

hi-
i have the same problem where my fan never shuts off. i am just trying out ubuntu and i like what i see, however, i don't like the fan running all the time. i am willing to test stuff out, but i don't know what to test or try to make the fan stop. or even what kind of information that you would need to know about my computer. i will try to give as much as i can in this post.

when i start the computer in windows, the fan runs at full speed, but then it quiets down after booting is done. when i start the computer in ubuntu, the fan runs at full speed all the time - even after booting. i ran the hardware testing application in system -> administration, but there wasn't anything in that application to express problems.

my computer is a pretty old one - a sony viao pcv-rx540 with a little bit more memory - ubuntu says that it has 501.3 MiB of memory. the processor is Intel(R) Celeron(TM) CPU 1200MHz. Ubuntu release 8.10 (intrepid) Kernel Linux 2.6.27-7-generic GNOME 2.24.1.

if you tell me what additional information you might need, i can get it for you or test changes (provided there are instructions on how to do the testing). thanks

--matt goto

[Aesaert Wim (wim-aesaert)]

Hello,

I have the same problem on my Toshiba Satellite L350D-10i laptop.

case 1) When I boot the laptop into Kubuntu Intrepid, sometimes the fan speed works good and changes accordingly to the cpu temp. This never causes my system to hang or stall. Even not when I try to compile a vanilla kernel.

case 2) When I boot the laptop into Kubuntu Intrepid, sometimes the fan speed runs at a constant low speed, no matter what the cpu temp. is. This causes my system to stall when I do some cpu intensive tasks (like compiling a vanilla kernel), but luckily it allows me to work without problems when I just send some mail or surf the net.

case 1 and case 2 happen in a kernel I compiled myself. I enabled some Toshiba options and I also changed some things on the ACPI and CPU settings. Most changes involve power and sensor settings. = kernel 2.6.27.2-met-toshiba-ondersteuning

only case 2 happens on kernel 2.6.27-7-generic an 2.6.27-9-generic, which are the ones that came with intrepid.

In the attachment i tarred 8 files. All are from the vanilla kernel but 4 are from case 1 (fan-changeable-speed) and 4 are from case 2 (fan-constant-low-speed).

case 1
dmesg.log-fan-good-changeable-speed.log
lspci-vvnn.log-fan-good-changeable-speed.log
uname-a.log-fan-good-changeable-speed.log
version.log-fan-good-changeable-speed.log

case 2
dmesg.log-fan-low-constant-speed.log
lspci-vvnn.log-fan-low-constant-speed.log
uname-a.log-fan-low-constant-speed.log
version.log-fan-low-constant-speed.log

If you want more info or i need to test something for you, I'm happy to do that.

Greetz,

Wim

[pablomme (pablomme)]

I am having a similar fan problem since I upgraded to Intrepid -- didn't happen in previous versions of Ubuntu, which I use since 7.04. In my case it doesn't happen all that often --about 5 times in 5 weeks of using Intrepid-- but it is a problem nonetheless. There seems to be no particular circumstance triggering the fan behaviour, and it can start happening hours after having turned the computer on.

What I noticed in dmesg is the following:

Normal fan
==========
The "CPUx attaching sched-domain" message occurs shortly after starting the desktop session:
...
[ 70.571768] CPU0 attaching NULL sched-domain.
[ 70.571785] CPU1 attaching NULL sched-domain.
[ 70.574586] CPU0 attaching sched-domain:
[ 70.574597] domain 0: span 0-1 level MC
[ 70.574602] groups: 0 1
[ 70.574613] CPU1 attaching sched-domain:
[ 70.574617] domain 0: span 0-1 level MC
[ 70.574622] groups: 1 0
...

Fan goes bad
============
The "CPUx attaching sched-domain" message does not occur at the start of the desktop session. However, later I get:
...
[ 2034.964654] CPU0 attaching NULL sched-domain.
[ 2034.964673] CPU1 attaching NULL sched-domain.
[ 2034.972117] CPU0 attaching sched-domain:
[ 2034.972129] domain 0: span 0-1 level MC
[ 2034.972134] groups: 0 1
[ 2034.972146] CPU1 attaching sched-domain:
[ 2034.972150] domain 0: span 0-1 level MC
[ 2034.972154] groups: 1 0
[ 2037.704837] wlan0: authenticate with AP 00:1b:2f:50:cf:94
[more wlan authentication messages]
[ 2399.907705] wlan0: associated
[ 2402.525669] padlock: VIA PadLock not detected.

And later on:

[ 3157.907395] CE: hpet increasing min_delta_ns to 15000 nsec
[ 8011.064170] usb 4-1: USB disconnect, address 3
[ 8016.725661] CPU0 attaching NULL sched-domain.
[ 8016.725676] CPU1 attaching NULL sched-domain.
[ 8016.727606] CPU0 attaching sched-domain:
[ 8016.727616] domain 0: span 0-1 level MC
[ 8016.727621] groups: 0 1
[ 8016.727632] domain 1: span 0-1 level CPU
[ 8016.727637] groups: 0-1
[ 8016.727645] CPU1 attaching sched-domain:
[ 8016.727650] domain 0: span 0-1 level MC
[ 8016.727654] groups: 1 0
[ 8016.727675] domain 1: span 0-1 level CPU
[ 8016.727680] groups: 0-1
[ 8054.188887] CPU0 attaching NULL sched-domain.
[ 8054.188905] CPU1 attaching NULL sched-domain.
[ 8054.193246] CPU0 attaching sched-domain:
[ 8054.193257] domain 0: span 0-1 level MC
[ 8054.193263] groups: 0 1
[ 8054.193273] CPU1 attaching sched-domain:
[ 8054.193277] domain 0: span 0-1 level MC
[ 8054.193282] groups: 1 0
[end]

I don't know how the wlan or usb events above relate to the sched-domain messages (other than coinciding in time within a margin of a few seconds in an otherwise clean dmesg). I don't know when the fan went wrong, since it wasn't I who was using the computer and only noticed it later (22000 seconds after boot), but my bet is that it was at either 2000 or 8000 seconds.

Perhaps the above logs may be meaningful to someone else?

BTW, my laptop is similar to eldragon's. Also, I'm using the unmodified 2.6.27-8.17 kernel which was in the intrepid-proposed repository (haven't upgraded because of bug #294667). 2.6.27-7 behaved the same.

[pablomme (pablomme)]

I'm having a different variant of the fan problem since I upgraded to 2.6.27-10. When the computer boots, the BIOS sets the fan running at medium intensity, and under normal conditions the Linux kernel stops when it begins probing devices (when the splash screen appears). Now it doesn't, and the fan simply keeps running.

Under normal conditions, the four fan intensity levels are triggered at 61, 71, 81 and 91 degrees when temperature increases, and the speed level is reduced at 50, 60, 70 and 80 degrees when the temperature decreases (i.e., reaching 50 means stopping the fan).

When the fan starts non-stop from boot, if I heat up the CPU to 61 degrees (first trigger), the fan switches to the lowest intensity, and then it stops if I allow it to cool down to 50 degrees. I use a bash script to warm up the CPU, which I've attached in case anyone wants to use it. I usually need to block the air vent with my hand to prevent the running fan from spoiling the trick. Keep an eye on the temperature if you use this!

But I've also had cases where the fan won't respond to increasing the temperature. This is getting annoying.. does anyone have any idea of what may be going wrong here, or where to look to gather clues?

[penalvch (penalvch)]

nfusi, thank you for reporting this and helping make Ubuntu better. Hardy desktop reached EOL on May 12, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]