High Fan Throttle After Resume from Suspend

The system Suspends and Resumes OK but the fan is at full throttle after Resuming.

Can anyone suggest a fix please?

OS 12.2/3.7.1-2

> Can anyone suggest a fix please?

-=WELCOME=- new poster, but you get my prize:

Day’s Help Request with Least Possible Information Given

so, my suggestion is to give some…


dd http://tinyurl.com/DD-Hardware http://tinyurl.com/DD-Software

On 01/11/2013 07:57 PM, dd wrote:
>
> Day’s Help Request with Least Possible Information Given

actually, i probably should have said something like:

we can’t help without some more information…here is a guide for what
might help us help you:
http://tinyurl.com/anel


dd
http://goo.gl/PUjnL
http://tinyurl.com/DD-Hardware
http://tinyurl.com/DD-Software

Yehhh!!! lol!

Which specifics should I provide?
This is an ACPI-compliant Windows/Vista-compatible machine running OS-12.2 x64 with kernel 3.7.1-2 desktop.

PM-suspend.log:

Initial commandline parameters:
Fri Jan 11 19:48:32 CET 2013: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
suspend initiated: Fri Jan 11 19:48:32 CET 2013

Linux linux-2xmk.site 3.7.1-2-desktop #1 SMP PREEMPT Thu Dec 27 09:08:21 UTC 2012 (ae1c592) x86_64 x86_64 x86_64 GNU/Linux
kernel command line: ‘BOOT_IMAGE=/boot/vmlinuz-3.7.1-2-desktop root=UUID=4eccf6a8-61a7-4fb4-902e-9e4805d9d8ff video=1280x800 resume=/dev/disk/by-id/ata-ST9160412AS_5VG3H8SN-part5 splash=silent quiet showopts apm=on’
Module Size Used by
fuse 87139 3
xt_tcpudp 12885 2
xt_pkttype 12505 3
xt_LOG 17522 10
xt_limit 12712 10
af_packet 39587 0
rfcomm 73109 4
bnep 19702 2
ip6t_REJECT 12940 3
nf_conntrack_ipv6 14684 3
nf_defrag_ipv6 18262 1 nf_conntrack_ipv6
ip6table_raw 12684 1
ipt_REJECT 12542 3
iptable_raw 12679 1
xt_CT 12759 4
iptable_filter 12811 1
ip6table_mangle 12701 0
nf_conntrack_netbios_ns 12666 0
nf_conntrack_broadcast 12590 1 nf_conntrack_netbios_ns
nf_conntrack_ipv4 15013 3
nf_defrag_ipv4 12730 1 nf_conntrack_ipv4
ip_tables 27240 2 iptable_raw,iptable_filter
xt_conntrack 12761 6
nf_conntrack 98470 6 nf_conntrack_ipv6,xt_CT,nf_conntrack_netbios_ns,nf_conntrack_broadcast,nf_conntrack_ipv4,xt_conntrack
ip6table_filter 12816 1
ip6_tables 27208 3 ip6table_raw,ip6table_mangle,ip6table_filter
x_tables 34013 15 xt_tcpudp,xt_pkttype,xt_LOG,xt_limit,ip6t_REJECT,ip6table_raw,ipt_REJECT,iptable_raw,xt_CT,iptable_filter,ip6table_mangle,ip_tables,xt_conntrack,ip6table_filter,ip6_tables
ir_kbd_i2c 13168 0
cpufreq_conservative 13822 0
cpufreq_userspace 13163 0
cpufreq_powersave 12619 0
zl10353 13740 1
tm6000_dvb 13175 0
dvb_core 125515 1 tm6000_dvb
tm6000_alsa 13582 1
rc_hauppauge 12533 0
tuner_xc2028 31266 2
tuner 27416 1
tpm_infineon 17537 0
pata_pcmcia 17075 1
snd_hda_codec_analog 93694 1
tm6000 71424 2 tm6000_dvb,tm6000_alsa
videobuf_vmalloc 13590 1 tm6000
videobuf_core 30119 2 tm6000,videobuf_vmalloc
rc_core 31851 4 ir_kbd_i2c,rc_hauppauge,tm6000
v4l2_common 21325 2 tuner,tm6000
videodev 129333 3 tuner,tm6000,v4l2_common
snd_hda_intel 41993 3
snd_hda_codec 147417 2 snd_hda_codec_analog,snd_hda_intel
snd_hwdep 13603 1 snd_hda_codec
snd_pcm 110154 3 tm6000_alsa,snd_hda_intel,snd_hda_codec
snd_seq 69780 0
snd_timer 29371 2 snd_pcm,snd_seq
snd_seq_device 14498 1 snd_seq
snd 91489 17 tm6000_alsa,snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_seq,snd_timer,snd_seq_device
arc4 12616 2
sg 36525 0
sr_mod 22296 0
cdrom 46688 1 sr_mod
iTCO_wdt 13481 0
iTCO_vendor_support 13719 1 iTCO_wdt
iwl4965 108507 0
iwlegacy 76047 1 iwl4965
mac80211 598005 2 iwl4965,iwlegacy
soundcore 15048 1 snd
pcmcia 65900 1 pata_pcmcia
snd_page_alloc 18711 2 snd_hda_intel,snd_pcm
cfg80211 218484 3 iwl4965,iwlegacy,mac80211
hp_wmi 13953 0
sparse_keymap 13891 1 hp_wmi
ppdev 17679 0
btusb 23871 0
bluetooth 341895 24 rfcomm,bnep,btusb
rfkill 26530 5 cfg80211,hp_wmi,bluetooth
acpi_cpufreq 19572 1
mperf 12668 1 acpi_cpufreq
irda 133213 0
coretemp 13394 0
kvm 475491 0
pcspkr 12719 0
joydev 17378 0
serio_raw 13376 0
firewire_ohci 40402 0
firewire_core 72670 1 firewire_ohci
crc_itu_t 12708 1 firewire_core
sdhci_pci 22796 0
sdhci 38323 1 sdhci_pci
mmc_core 119332 2 sdhci_pci,sdhci
lpc_ich 17062 0
mfd_core 13399 1 lpc_ich
yenta_socket 41228 0
pcmcia_rsrc 18449 1 yenta_socket
pcmcia_core 27630 3 pcmcia,yenta_socket,pcmcia_rsrc
e1000e 252783 0
mei 79557 0
wmi 19071 1 hp_wmi
battery 18769 0
crc_ccitt 12708 1 irda
parport_pc 37266 0
parport 46311 2 ppdev,parport_pc
tpm_tis 19125 0
container 12840 0
tpm 27336 2 tpm_infineon,tpm_tis
tpm_bios 18893 1 tpm
hp_accel 26013 0
lis3lv02d 20192 1 hp_accel
input_polldev 13897 1 lis3lv02d
ac 13133 0
microcode 35785 0
autofs4 42771 2
fan 13003 0
thermal 18712 0
processor 44950 3 acpi_cpufreq
i915 605675 2
drm_kms_helper 50840 1 i915
drm 293115 3 i915,drm_kms_helper
i2c_algo_bit 13414 1 i915
button 13953 1 i915
video 19401 1 i915
thermal_sys 24957 4 fan,thermal,processor,video
scsi_dh_emc 17259 0
scsi_dh_alua 17162 0
scsi_dh_hp_sw 12895 0
scsi_dh_rdac 17409 0
scsi_dh 14844 4 scsi_dh_emc,scsi_dh_alua,scsi_dh_hp_sw,scsi_dh_rdac
ata_piix 35039 0
ata_generic 12911 0

         total       used       free     shared    buffers     cached

Mem: 3983480 947752 3035728 0 43372 424296
-/+ buffers/cache: 480084 3503396
Swap: 2103292 0 2103292

/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:

/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/02rtcwake suspend suspend:
rtcwake alarm not enabled in /etc/pm/config.d/rtcwake.config, doing nothing…

/usr/lib/pm-utils/sleep.d/02rtcwake suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/06autofs suspend suspend:
autofs.service - Automounts filesystems on demand
Loaded: loaded (/lib/systemd/system/autofs.service; disabled)
Active: inactive (dead)
CGroup: name=systemd:/system/autofs.service

/usr/lib/pm-utils/sleep.d/06autofs suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/30s2disk-check suspend suspend:

/usr/lib/pm-utils/sleep.d/30s2disk-check suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/45pcmcia suspend suspend:
ejecting PCMCIA cards…

/usr/lib/pm-utils/sleep.d/45pcmcia suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:

/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/50rcnetwork suspend suspend:

/usr/lib/pm-utils/sleep.d/50rcnetwork suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend:
Having NetworkManager put all interaces to sleep…Failed.

/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:

/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/80acpi-fan suspend suspend:

/usr/lib/pm-utils/sleep.d/80acpi-fan suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/80videobios suspend suspend:

/usr/lib/pm-utils/sleep.d/80videobios suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:

/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:

/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:

/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95packagekit suspend suspend:

/usr/lib/pm-utils/sleep.d/95packagekit suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
Kernel modesetting video driver detected, not using quirks.

/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99Zgrub suspend suspend:

/usr/lib/pm-utils/sleep.d/99Zgrub suspend suspend: success.
Running hook /etc/pm/sleep.d/99at suspend suspend:
atd.service - Execution Queue Daemon
Loaded: loaded (/lib/systemd/system/atd.service; disabled)
Active: inactive (dead)
CGroup: name=systemd:/system/atd.service

/etc/pm/sleep.d/99at suspend suspend: success.
Running hook /etc/pm/sleep.d/99fancontrol.sh suspend suspend:
mythbackend: no process found

/etc/pm/sleep.d/99fancontrol.sh suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99info suspend suspend:

/usr/lib/pm-utils/sleep.d/99info suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:

/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Fri Jan 11 19:48:33 CET 2013: performing suspend
INFO: using built-in quirks database from HAL.
INFO: S2RAM_OPTS from HAL quirks: ’ '.
KMS graphics driver is in use, skipping quirks.
Fri Jan 11 19:48:48 CET 2013: Awake.
Fri Jan 11 19:48:48 CET 2013: Running hooks for resume
Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend:

/usr/lib/pm-utils/sleep.d/99video resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99info resume suspend:

/usr/lib/pm-utils/sleep.d/99info resume suspend: success.
Running hook /etc/pm/sleep.d/99fancontrol.sh resume suspend:
xfce4-panel: Cannot open display: .
Type “xfce4-panel --help” for usage.

/etc/pm/sleep.d/99fancontrol.sh resume suspend: success.
Running hook /etc/pm/sleep.d/99at resume suspend:

/etc/pm/sleep.d/99at resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99Zgrub resume suspend:

/usr/lib/pm-utils/sleep.d/99Zgrub resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:

/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95packagekit resume suspend:

/usr/lib/pm-utils/sleep.d/95packagekit resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led resume suspend:

/usr/lib/pm-utils/sleep.d/95led resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:

/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock resume suspend:

/usr/lib/pm-utils/sleep.d/90clock resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/80videobios resume suspend:

/usr/lib/pm-utils/sleep.d/80videobios resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/80acpi-fan resume suspend:

/usr/lib/pm-utils/sleep.d/80acpi-fan resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules resume suspend:
Reloaded unloaded modules.

/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend:
Having NetworkManager wake interfaces back up…Failed.

/usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/50rcnetwork resume suspend:

/usr/lib/pm-utils/sleep.d/50rcnetwork resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth resume suspend:

/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/45pcmcia resume suspend:
inserting PCMCIA cards…

/usr/lib/pm-utils/sleep.d/45pcmcia resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/30s2disk-check resume suspend:

/usr/lib/pm-utils/sleep.d/30s2disk-check resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/06autofs resume suspend:

/usr/lib/pm-utils/sleep.d/06autofs resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/02rtcwake resume suspend:

/usr/lib/pm-utils/sleep.d/02rtcwake resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave resume suspend:

/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00logging resume suspend:

/usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
Fri Jan 11 19:48:49 CET 2013: Finished.

Problem devices are DVB tuners (as usual), devices tm6000 etc. These are unloaded before Suspension and reloaded on Resume. The fan is at full throttle after resuming regardless of all peripheral devices connected or not.

I’m thinking the power state fails to resume.

On 2013-01-11 20:56, bananaosx wrote:
>
> Which specifics should I provide?
> This is an ACPI-compliant Windows/Vista-compatible machine running
> OS-12.2 x64 with kernel 3.7.1-2 desktop.

Perhaps some module unloads and does not load again. Try comparing
modules before and after.

You may try using laptop-tools (I think that’s the name, not sure).


Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)

On 01/11/2013 08:56 PM, bananaosx wrote:
>
> This is an ACPI-compliant Windows/Vista-compatible machine running
> OS-12.2 x64 with kernel 3.7.1-2 desktop.

that could be the problem right there (i don’t see Linux, UNIX, BSD,
AIX, etc etc mentioned)

some motherboards are known to be more compliant than others…some
manufacturers even provide Linux (as well as Windows) drivers for their
hardware–yours?

but, i am not going to ask you for your hardware…

> kernel command line: ‘BOOT_IMAGE=/boot/vmlinuz-3.7.1-2-desktop
> root=UUID=4eccf6a8-61a7-4fb4-902e-9e4805d9d8ff video=1280x800
> resume=/dev/disk/by-id/ata-ST9160412AS_5VG3H8SN-part5 splash=silent
> quiet showopts apm=on’

read the warning in my sig and then try one or a mixture of these (any
might work, or might make it worse…if it starts up with no fan noise
MONITOR TEMPERATURE CLOSELY:


acpi_osi=Linux
acpi_os_name=Linux *or* acpi_os_name="Microsoft Windows"
acpi_sleep=nonvs
acpi_sleep=sci_force_enable
acpi_enforce_resources=lax *or* acpi_enforce_resources=no

if none of those help you might consider to just Use what works! (don’t
suspend and resume, just power off and reboot.)


dd http://tinyurl.com/DD-Caveat

Thanks, something to go on.
But Mythbuntu 12.04 doesn’t cause any problem with fan throttling on my machine. Only happens on OS-12.2 and Ubuntu 12.10.

On 2013-01-12 13:56, bananaosx wrote:

>
> Thanks, something to go on.
> But Mythbuntu 12.04 doesn’t cause any problem with fan throttling on my
> machine. Only happens on OS-12.2 and Ubuntu 12.10.

Compare kernel versions.


Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)

On 01/12/2013 01:56 PM, bananaosx wrote:
> But Mythbuntu 12.04 doesn’t cause any problem with fan throttling on my
> machine. Only happens on OS-12.2 and Ubuntu 12.10.

hence comes the ‘old saying’ of “Use what works.”

and, i hear there are differences between Win7 and Win8…so, no
surprise there are differences between those three very different
distros!! i’d guess that each runs a different kernel (as do Win7, Win8,
XP, OSX, openSUSE 12.1, openSUSE 12.2, and and and)


dd

Those “three Linux distos” aren’t so different at all. Linux is still linux, like it or not.
Certainly from what I’ve tried, the difference between the distros is an older kernel (3.2) in Mythbuntu 12.04 as opposed to (3.4) in OS 12.2 as Robin_Listas also suggested.

On 01/12/2013 11:26 AM, bananaosx wrote:

> Those “three Linux distos” aren’t so different at all. Linux is still
> linux, like it or not.
> Certainly from what I’ve tried, the difference between the distros is
> an older kernel (3.2) in Mythbuntu 12.04 as opposed to (3.4) in OS 12.2
> as Robin_Listas also suggested.

I agree that the distros are not so different in terms of the utilities;
however, the differences between kernel 3.2 and 3.4 are substantial as 16,918
kernel source files changed between those two versions. Incidentally, that rate
of change is fairly typical. From 3.4 to 3.6, 14,072 files changed. Note that
30,142 files changed between 3.2 and 3.8-rc3, but that 22,074 files changed
between 3.6 and 3.8-rc3. Perhaps there is a surge in changed files with 3.8.

Good point.
Though I changed another system from 3.4 to 3.7 for a software update but apart from that there was no discernable difference to the system which I could notice.
What’s the point of making such radical changes to the kernel so often? I mean Ubuntu expects users to be on kernel 3.2 in what they coin LTS until at least 2014…

On 01/12/2013 06:26 PM, bananaosx wrote:
> Those “three Linux distos” aren’t so different at all. Linux is still
> linux, like it or not.

heh! about 10 (or 15) years ago after i complained that something which
worked in Red Hat didn’t work in Mandrake (or vice versa) an old man
with gray hair (and roots in '60s Big Iron) said:

“When you have seen one Linux, you have seen one Linux.”

i’m not here because i think it fun to spar with questioners…

so, i’m out.


dd

On 2013-01-12 18:26, bananaosx wrote:
> Those “three Linux distos” aren’t so different at all. Linux is still
> linux, like it or not.
> Certainly from what I’ve tried, the difference between the distros is
> an older kernel (3.2) in Mythbuntu 12.04 as opposed to (3.4) in OS 12.2
> as Robin_Listas also suggested.

With that info you can do a bugzilla report against a kernel regression.
Say which kernels work in openSUSE, which do not, and the same with the
other distro.


Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)

On 01/12/2013 12:56 PM, bananaosx wrote:
>
> Good point.
> Though I changed another system from 3.4 to 3.7 for a software update
> but apart from that there was no discernable difference to the system
> which I could notice.

That is the idea.

> What’s the point of making such radical changes to the kernel so often?
> I mean Ubuntu expects users to be on kernel 3.2 in what they coin LTS
> until at least 2014…

The reasons for such “radical changes” are bug fixes, new drivers, new file
systems, and general improvements. If you have a piece of hardware that does not
work at all in 3.2, you would be very happy to have it in the kernel in any
version. Of course, LTS releases are for hardware that existed before that
kernel was released.

If we worked the way Windows does, you would need to be scrambling to find a
crappy, vendor-written driver to install, and then sort out all the system
crashes that are due to the bugs in it. Yes, you may get bit by a bug in a
particular kernel; however, you can be assured that every change has been
scrutinized by many very smart people before it was added to the kernel code
base. As author of over 750 patches since kernel 2.6.18, I can assure you that
making a change is not easy. Many of them went through 5 or more versions before
they were accepted, and several hundred changes that I proposed never made it
into the kernel.

I have the same issue on an HP mini 5102 with linux 3.7 and newer versions, so I reverted to 3.6.3. The problem is that the CPU temperature indicator is stuck at 100 oC, which causes the fan to run at full throttle. This is a known issue, see https://lkml.org/lkml/2012/12/19/166 for more details.

Was a patch to this problem recently submitted?

I reinstalled SUSE 12.2, this time with only the XFCE-DM and the Suspend problem has just gone away. Stock 3.4 kernel.

As I alluded to it in my previous response, the bug is present in kernels newer than 3.7. It has not been fixed, as far as I know.

My fav Linux issue is back having upgraded to openSUSE 12.3 Release.

Fan is at full throttle on resuming from Suspend/Hibernate.

:frowning:

Same issue reported here by another user of 12.3 RC2.

[Bug 807996] New: HP 2230s cpu fan at fully speed after standby/suspend.](http://lists.opensuse.org/opensuse-bugs/2013-03/msg00998.html)