Bug 554625 - Fan stays off after resume from suspend/hibernate: Compaq Presario A916NR T2330 cpu
Summary: Fan stays off after resume from suspend/hibernate: Compaq Presario A916NR T23...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-12 07:06 UTC by Phil V
Modified: 2010-09-27 02:05 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-27 02:05:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg on bootup (no suspending) (35.46 KB, text/plain)
2010-01-12 07:06 UTC, Phil V
no flags Details
dmesg after resume. CPU core temps are drifting up. (42.25 KB, text/plain)
2010-01-12 07:28 UTC, Phil V
no flags Details

Description Phil V 2010-01-12 07:06:48 UTC
Created attachment 383184 [details]
dmesg on bootup (no suspending)

Description of problem:

Each time laptop is resumed from suspend, I observe the following behavior:
1. cpu core temperatures rapidly (about 1 minute) steadily soar up on idle machine from around 50C past 80C, heating stops only by reboot or poweroff.

2. Two other temperatures are falsely reported as constantly 27C:
    *  /proc/acpi/thermal_zone/TZ01/temperature
    *  sensors -> acpitz-virtual-0  (AKA libsensors temp1)

Version-Release number of selected component (if applicable):
DVD install of x86_64 on 
This has been a problem with Fedora 11 if not earlier and continues to be a problem with Fedora 12. 


How reproducible: Every time machine is resumed from suspend.


Steps to Reproduce:
1. Suspend
2. Resume
3. Watch cpus bake

Actual results: 

Expected results:  Idle machine should not threaten to melt its CPUs.

Additional info: Laptop specs at 
www.newageinc.com/pdfs/CPQ%20A916NR.pdf
Compaq A916NR Presario Intel Pentium Dual-Core Mobile Processor T2330 

More information available on request. What would be helpful?

Comment 1 Phil V 2010-01-12 07:28:57 UTC
Created attachment 383189 [details]
dmesg after resume.  CPU core temps are drifting up.

Note the temp1 below stays constant; the others drift higher and higher until reboot.

$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:       +26.8°C  (crit = +100.0°C)                  

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +66.0°C  (high = +100.0°C, crit = +100.0°C)  

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +68.0°C  (high = +100.0°C, crit = +100.0°C)  


$ cat /proc/acpi/thermal_zone/TZ01/temperature 
temperature:             27 C

Comment 2 Phil V 2010-01-28 06:05:15 UTC
This happens both in case of suspend to RAM and in suspend to disk.

Any hints on things to look into would be greatly appreciated.

I've since upgraded to the latest BIOS for the machine. 
Problem continues just as before.

Comment 3 Phil V 2010-02-20 06:16:36 UTC
Normally CPU is at 43-50C when idle.
After resume from suspend/hibernate, and even when idle, temperature drifts upwards past 80C (only reboot stops the increase)

What can I do to help solve this problem?

Comment 4 Phil V 2010-02-20 07:11:34 UTC
I hope it helps to point out a different but likely related problem on similar hardware is reported at:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/352583 (A900) 

less similar hardware, but similar problem at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/352739 
https://bugs.launchpad.net/fedora/+bug/234519 

(the first suspend resume from power up work, but the second suspend resume fails on resume where the hd does not even wake up; requiring the power button to be held in to power down from that failed resume.)

I seem to recall I had that problem as well; but don't resume anymore, so I don't see it often! 

What do you recommend?

Comment 5 Phil V 2010-04-23 03:51:18 UTC
Is there any information I can provide that would help move this forwards?

Comment 6 Phil V 2010-06-05 19:53:06 UTC
Perhaps the similar sounding bug

https://bugzilla.kernel.org/show_bug.cgi?id=14667

has the same cause.

Comment 7 Phil V 2010-07-15 21:35:20 UTC
Apparently the fan does not come on after resume.
This is a problem that others have experienced as well.
There are no entries in /proc/acpi/fan
neither before nor after resume.
Before suspend/hibernate the fan will vary with CPU temperatures;
after resume the fan stays off.

Please help.

Comment 8 Chuck Ebbert 2010-09-03 13:37:14 UTC
Does kernel 2.6.34.6-47 fix this problem?

Comment 9 Phil V 2010-09-19 21:56:11 UTC
How can I test that? yum update gives me 2.6.34.6-54.fc13.x86_64 which fails to boot.

Which was made to appear a worse problem since the grub menu was hidden: 
it made it look like the system was completely unbootable.
https://bugzilla.redhat.com/show_bug.cgi?id=634894


 * Is there a way to install a particular kernel, or to 
 * block a particular kernel?

Your advice much welcomed here!

Comment 10 Phil V 2010-09-27 01:08:18 UTC
(In reply to comment #9)

Apologies -- Comment 9 belonged on a different bug report.

Comment 11 Phil V 2010-09-27 02:05:47 UTC
In fact kernel 2.6.34.6-47 and later seem to fix the problem with the 

       fan not coming back on

 * if the system resumes successfully. * 

However the system resumes less successfully than with previous kernels.

With the new kernels, only ONE successful suspend-resume cycle is possible.
It is only possible to get this one cycle if:
 the lid is closed without invoking the GNOME menu suspend option.

Interestingly, closing the lid on the Cntl-Alt-Fn consoles does not suspend.
Closing the lid on the X login window does suspend successfully once.

Repeating this, or if suspend is triggered any other way, on resume the screen remains black, keyboard is unresponsive, attaching an external keyboard doesn't help as it too is unresponsive.

I have opened Bug# 637650 
https://bugzilla.redhat.com/show_bug.cgi?id=637650

I think I should close this bug.


Note You need to log in before you can comment on or make changes to this bug.