noisy fan after suspend to RAM

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Please run the following command which will attach necessary information:

apport-collect 577058
if you are using Karmic Koala (9.10) or newer, or

apport-collect -p linux-image-`uname -r` BUGNUMBER
if you are using Jaunty Jackalope (9.04).

Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python-launchpadlib'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.

If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options):

First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).

For your reference, the full description of procedures for kernel related bug reports is available at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies. Thanks in advance!

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Thanks a lot dirk klaes.

Now, please follow the instructions at [1] and provide here any information that you think might be useful to identify the cause of the problem.

[1] https://wiki.ubuntu.com/Kernel/Debugging/HighTemperatures#Diagnostic%20Techniques

If I boot the System with "GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_enforce_resources=lax", I'm able to run pwmconfig without the error message "/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed".
The fan is controlled by fancontrol even when the machine comes back from suspend.

With sensors-detect a winbond w83627hf was detected and I wrote it into /etc/modules
Now the output of sensors is:

privat@kubuntu:$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +29.0°C (crit = +100.0°C)

w83627hf-isa-0290
Adapter: ISA adapter
in0: +1.09 V (min = +0.00 V, max = +4.08 V)
in1: +2.59 V (min = +0.00 V, max = +4.08 V)
in2: +3.26 V (min = +2.82 V, max = +3.79 V)
in3: +3.04 V (min = +1.52 V, max = +2.03 V) ALARM
in4: +3.06 V (min = +3.98 V, max = +2.00 V) ALARM
in5: +1.52 V (min = +3.02 V, max = +3.52 V) ALARM
in6: +1.17 V (min = +1.95 V, max = +0.50 V) ALARM
in7: +3.28 V (min = +3.55 V, max = +4.08 V) ALARM
in8: +2.98 V (min = +2.03 V, max = +4.08 V)
fan1: 948 RPM (min = 332 RPM, div = 16)
fan2: 0 RPM (min = 332 RPM, div = 16) ALARM
fan3: 0 RPM (min = 332 RPM, div = 16) ALARM
temp1: +27.0°C (high = +93.0°C, hyst = -69.0°C) sensor = thermistor
temp2: +29.0°C (high = +50.0°C, hyst = +45.0°C) sensor = diode
temp3: +28.5°C (high = +50.0°C, hyst = +45.0°C) sensor = thermistor
cpu0_vid: +0.000 V
beep_enable:enabled

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Same is happening on oneiric kernel with an HP-620.

The bug is fixed using a precise (3.1.0) kernel, so I think it would be possible to bisect to merge the fix.

Klaes, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? 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 the development 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 . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

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