[HP 6730b] Fan at full speed after suspend

[MNLipp]

After upgrading to 13.04 the fan of my HP 6730b runs at full speed when resuming after suspend. Before the suspend everything is ok.

Workaround is to boot with the old kernel from 12.10 (3.5.0-27).

I also tried mainline build 3.8.9-030809. Problem occurs there as well.
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mnl 2949 F.... pulseaudio
CRDA:
 country DE:
  (2400 - 2483 @ 40), (N/A, 20)
  (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
  (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
  (5470 - 5725 @ 40), (N/A, 26), DFS
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=86292e17-edd2-4a1b-8e1b-5208a1731140
InstallationDate: Installed on 2010-11-10 (900 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#ABD)
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=cff10fb4-08a2-459b-be12-80698b20d2d3 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
Tags: raring
Uname: Linux 3.8.0-19-generic i686
UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare voice wireshark
dmi.bios.date: 12/07/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDD Ver. F.20
dmi.board.name: 30DD
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 96.23
dmi.chassis.asset.tag: CNU9326SJY
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDDVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#ABD):pvrF.20:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6730b (GB990EA#ABD)
dmi.product.version: F.20
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1173997

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

apport information

[MNLipp (mnl)]

Seems to be knwon upstream:

https://bugzilla.redhat.com/show_bug.cgi?id=895276
https://lkml.org/lkml/2012/12/4/428

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0].

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-raring/

[MNLipp (mnl)]

I tested v3.9.0. The result is "kernel-replaces-bug-upstream". Resume from suspend works without the fan going up, BUT in regular operation, the fan will no longer go down, once its speed has increased.

With v3.9.0 I get this: starting two endless loops (it's a dual core machine) makes the temperature rise and the fan goes up. Now I kill the processes and wait for the temperature to drop down again. But the fan never goes down, it keeps the speed it had when the two processes were running.

I'll leave it to you to tag and close this bug. There is still something lurking there with fan control.

[quina (kowalik-krzysztof)]

Hello!
Have exactly the same problem for a VERY long time (about 2 years, maybe a bit longer - from the time i have started using Ubuntu on my laptop). Kernell version is 3.8.0-20.
Ubuntu 13.04, HP 6730b.

[Brad Figg (brad-figg)]

There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.

You can update to the latest kernel by simply running the following commands in a terminal window:
    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the
bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[quina (kowalik-krzysztof)]

Problem still occur.
Kernel: 3.8.0-27-generic

[penalvch (penalvch)]

MNLipp, could you please test for this in Saucy and advise on the post-suspend results via http://cdimage.ubuntu.com/daily-live/current/ ?

quina, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Oliver Joos (oliver-joos)]

It seems to be fixed and the fixed will be backported: https://bugzilla.kernel.org/show_bug.cgi?id=58311

[Pavel Karpukhin (raiderx+launchpad)]

What's about this bug?
I have HP Compaq 6720s GR650EA with Ubuntu 12.04 x86_64
After restoring from suspend fan of my notebook runs very fast.
$ uname -a
Linux linux-raider 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed Sep 11 18:21:16 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Pavel Karpukhin, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[penalvch (penalvch)]

OR using EOL release, and no response for years.