HP Compaq 8510w: Fan is running constantly in high speed after resume from suspend to RAM

[Jarno Suni]

No proper reason for running at so high speed as there is not much CPU load. Product number of the notebook: GC114EA#AK8

WORKAROUND: Put following script in /etc/pm/sleep.d :
#!/bin/sh
case "$1" in
        resume|thaw)
                for i in $(seq 0 10) ;
                do
                        echo "0" > /sys/devices/virtual/thermal/cooling_device${i}/cur_state
                done
;;
esac

In ubuntu 15.04 or later you may have to add this executable script in /lib/systemd/system-sleep/ :

#!/bin/sh
case $1/$2 in
  pre/*)
    ;;
  post/*)
    for i in $(seq 0 10) ; do
      echo "0" > /sys/devices/virtual/thermal/cooling_device${i}/cur_state
    done
    ;;
esac

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-18-generic 4.2.0-18.22
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jarnos 1404 F.... pulseaudio
CurrentDesktop: XFCE
Date: Thu Nov 26 15:37:42 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=19c075ab-2b2e-4285-a3a5-dbd15ee7b31e
InstallationDate: Installed on 2015-11-21 (4 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-18-generic N/A
 linux-backports-modules-4.2.0-18-generic N/A
 linux-firmware 1.149.2
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MVD Ver. F.20
dmi.board.name: 30C5
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.36
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.version: F.20
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Jarno Suni (jarnos)]

This is an old issue with the hardware. This answer and its comment give workarounds that seem to work: http://superuser.com/a/642911/490855

[Jarno Suni (jarnos)]

Joseph Salisbury, how is this incomplete?

[penalvch (penalvch)]

Jarno Suni, could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description)?

[penalvch (penalvch)]

Jarno Suni, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[penalvch (penalvch)]

Jarno Suni, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Jarno Suni (jarnos)]

I suspended using Suspend action button in Xfce GUI. Tried mainline kernel 4.4-rc5 with which bug exists.

[Jarno Suni (jarnos)]

I did two suspend-resume cycles. Dmesg after that is attached.

[Id2ndR (id2ndr)]

The script from http://superuser.com/questions/229849/high-fan-speed-after-return-from-suspend-on-ubuntu/642911#642911 work in 14.04.3 (linux-image-generic-lts-vivid)

[Launchpad Janitor (janitor)]

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

[penalvch (penalvch)]

Jarno Suni, to advise, the suspend article has been completely revamped. Hence, could you please first test the latest mainline kernel (4.5) and advise to if this is still reproducible?

[Jarno Suni (jarnos)]

The bug is fixed in 4.5.0-040500-generic.

[Jarno Suni (jarnos)]

Please include the fix in the next Ubuntu release.

[penalvch (penalvch)]

Jarno Suni, the next step is to fully reverse commit bisect from kernel 4.4-rc4 to 4.5 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

After the fix commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Jarno Suni (jarnos)]

Aren't there any comments connected to commits to give hint about what changes have been made? If I understood right, you tell me to do potentially several reboots with different kernels and build several kernels.