Bug 42605 - CPU fan runs very very fast ubuntu 11.10 dell xpsl702x
Summary: CPU fan runs very very fast ubuntu 11.10 dell xpsl702x
Status: REJECTED WILL_NOT_FIX
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Fan (show other bugs)
Hardware: All Linux
: P1 blocking
Assignee: Zhang Rui
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-19 08:53 UTC by Amit Rana
Modified: 2013-06-24 02:34 UTC (History)
5 users (show)

See Also:
Kernel Version: 3.0.0-14-generic
Subsystem:
Regression: No
Bisected commit-id:


Attachments
"grep . /sys/class/thermal/*/*" output (2.46 KB, text/plain)
2012-12-11 08:07 UTC, Amit Rana
Details

Description Amit Rana 2012-01-19 08:53:18 UTC
copied from: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836480
creating new bug here as per comment #22

1. Till login screen fan speed is ok
2. Soon after login fan starts running like crazy. The air coming out becomes hot after sometime.
3. Fan works quite normally on windows 7
4. Works fine with on 11.04.
5. I booted and worked using Open Suse 11.04 , fan was fine.
Comment 1 Len Brown 2012-01-31 03:24:29 UTC
when you run top, does it show that a process is running 100%
of the time?  which process?

If no process is implicated above...
can you reproduce this using an upstream kernel.org kernel?

if yes, what is the oldest kernel that 1st see's this issue,
and the newest kernel that does not see this issue?
Comment 2 Amit Rana 2012-01-31 05:35:42 UTC
1. top says system is 89.9% idle
2. I do not remember the exact version now but the kernel that comes with 11.04 was perfect. 11.10 is the one with problem. When I was using 11.04 I had the latest kernel.

I asked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836480 as well, I am not an expert can someone guide me how to test different kernels without having to reinstall?
Comment 3 Amit Rana 2012-02-18 06:40:30 UTC
Yesterday I was trying to solve some other problem, following steps given on this page http://www.ivegotavirus.com/blog/2011/11/06/how-to-get-optimus-working-on-ubuntu-11-10-oneiric/

Soon after step 3) sudo apt-get install bumblebee, fan started working fine.

Is this related? Now fan works fine. I haven't finishe the steps mentioned on the page. Just installed bumblebee, now fan is working normally.

I also keep ubuntu uptodate so not sure if that is also related. I am using 3.0.0-16-generic x86_64
Comment 4 Zhang Rui 2012-11-28 10:04:59 UTC
I googled bumblebee but it seems that it has nothing to do with Fan?

please attach the output of "grep . /sys/class/thermal/*/*".
and try "echo 1,0 > /sys/class/thermal/cooling_deviceX/cur_state", while cooling_deviceX type is FAN.

But anyway you can not reproduce the problem right now, right?
Comment 5 Amit Rana 2012-11-28 10:27:37 UTC
No, I am not able to reproduce the problem now.
Comment 6 Zhang Rui 2012-11-29 05:25:27 UTC
well, how to debug without reproducing it?
can you reproduce the bug if you remove bumblebee?
Comment 7 Zhang Rui 2012-12-11 01:43:47 UTC
ping...
Comment 8 Amit Rana 2012-12-11 08:06:32 UTC
Yes I was able to reproduce after unisntalling bumblee.
sudo apt-get remove bumblebee
It removed bumblebee and bumblebee-nvidia

After reboot fan is going crazy. Attaching output of "grep . /sys/class/thermal/*/*"
Comment 9 Amit Rana 2012-12-11 08:07:16 UTC
Created attachment 88901 [details]
"grep . /sys/class/thermal/*/*" output
Comment 10 Amit Rana 2012-12-11 08:09:05 UTC
I reinstalled BumbleeBee and fan is normal. No need for reboot

sudo add-apt-repository ppa:bumblebee/stable
sudo apt-get update
sudo apt-get install bumblebee bumblebee-nvidia
Comment 11 Sergio Durigan Junior 2013-04-24 06:20:27 UTC
Possibly related issue: bug #57051.
Comment 12 Zhang Rui 2013-05-15 07:07:25 UTC
(In reply to comment #10)
> I reinstalled BumbleeBee and fan is normal. No need for reboot
> 
do you mean the fan problem can not be reproduced any more after reinstalling BumbleeBee?
Comment 13 Aaron Lu 2013-06-21 07:38:52 UTC
Please also attch acpidump output here, thanks.
Comment 14 Zhang Rui 2013-06-24 02:34:04 UTC
problem is resolved by reinstalling a user space tool.

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