[HP Compaq 6720s] Fan at full speed after suspend

[pieter k]

I'm running Ubuntu 16.04 Xenial 64 bit on my compaq 7620s. Bug 1245164 came back. After suspension the fan makes a loud noise and it continues to do so.
In fact I also noticed it on 15.10.
Also in 14.04.3 it was wrong. But I followed some advice on the internet and after that it behaved good.

But I can't find a cure for the issue now. Just as I couldn't with 15.10
---
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: slmpe 1216 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=c0829020-bf7b-4ef4-a77c-476f90fde613
InstallationDate: Installed on 2016-02-08 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160208)
MachineType: Hewlett-Packard HP Compaq 6720s
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=80d9c9ab-f646-44e0-bb41-c66c93fcb53e ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-2-generic N/A
 linux-backports-modules-4.4.0-2-generic N/A
 linux-firmware 1.155
Tags: xenial
Uname: Linux 4.4.0-2-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/04/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MDU Ver. F.0D
dmi.board.name: 30D8
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 83.0E
dmi.chassis.asset.tag: CNU80831FG
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68MDUVer.F.0D:bd11/04/2008:svnHewlett-Packard:pnHPCompaq6720s:pvrF.0D:rvnHewlett-Packard:rn30D8:rvrKBCVersion83.0E:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6720s
dmi.product.version: F.0D
dmi.sys.vendor: Hewlett-Packard

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1543194/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[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 1543194

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.

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[pieter k (pieterkristensen)]

apport information

[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 v4.5 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'.

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/v4.5-rc3-wily/

[pieter k (pieterkristensen)]

kernel-fixed-upstream

[penalvch (penalvch)]

pieter k, the next step is to fully reverse commit bisect from kernel 4.4 to 4.5-rc3 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

[pieter k (pieterkristensen)]

I am an enthusiastic linux user (mainly (k)ubuntu, but this "bisecting" is above my league. I'm sorry to say. I find the:

linux-headers-4.5.0-040500rc3_4.5.0-040500rc3.201602071930_all.deb
linux-headers-4.5.0-040500rc3-generic_4.5.0-040500rc3.201602071930_amd64.deb
linux-image-4.5.0-040500rc3-generic_4.5.0-040500rc3.201602071930_amd64.deb

to work properly and the 4.4.0(-2 and -4) to not work properly.
I hope I have been of help anyway.

[pieter k (pieterkristensen)]

Luckily there are workarounds for this issue for both the old situation(1) and systemd(2).

1) In the old situation (Trusty Tahr - upstart) I found the following remedy that works like a charm:
Make a file with the following content (just the way I found in on the internet) read further below the quote:
bash script:

#!/bin/sh
#
# Reset fan speeds after resume, otherwise they blow at maximum speed
#
# Used as work-around for ACPI kernel bug 58301
# https://bugzilla.kernel.org/show_bug.cgi?id=58301
#
# The idea for this fix was taken from
# http://ubuntuforums.org/showthread.php?t=1761370
#
# Author: <email address hidden>
#
# To be made executable (sudo chmod 755 AnyName.sh and then to be saved as /etc/pm/sleep.d/AnyName.sh

case "$1" in
  thaw|resume)
    for i in /sys/class/thermal/cooling_device* ; do
      type=`cat $i/type`
      if [ "$type" = "Fan" ] ; then
        echo 0 > $i/cur_state
      fi
  done
  ;;
  esac

2) But things are changed with systemd. After a proces of trial and error I found the following:
step one:

Create a file with the following content (read further below quote) :
bash script:

#!/bin/sh
# make this file executable (chmod 755 NameFile.sh)
# copy this file to folder /lib/systemd/system-sleep/

if [ $1 = post ] && [ $2 = suspend ]
then /usr/local/bin/fansystemd.sh
fi

step two:
Then create a file with the following content:
bash script:

#!/bin/sh
#
# Reset fan speeds after resume, otherwise they blow at maximum speed
#
# Used as work-around for ACPI kernel bug 58301
# https://bugzilla.kernel.org/show_bug.cgi?id=58301
#
# The idea for this fix was taken from
# http://ubuntuforums.org/showthread.php?t=1761370
#
# Author: <email address hidden>
#
# make file exectable (sudo chmod 755 NameFile.sh)
# To be saved as /usr/local/bin/ (sudo cp NameFile.sh /usr/local/bin/)
# this is like the upstart-script only without the first lines

  for i in /sys/class/thermal/cooling_device* ; do
      type=`cat $i/type`
      if [ "$type" = "Fan" ] ; then
        echo 0 > $i/cur_state
      fi
  done
  ;;
  esac

Make file exectable (sudo chmod 755 NameFile.sh), save as as /usr/local/bin/NameFile.sh (sudo cp NameFile.sh /usr/local/bin/). This is like the upstart-script only without the first lines.
This is 100% effective.