Bug 239927

Summary: Macbook gets hot (74 C)
Product: [Fedora] Fedora Reporter: Eelco Hoekema <ehoekema>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 6CC: jarod, triage
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: bzcl34nup
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-06 19:35:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Eelco Hoekema 2007-05-12 17:03:56 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20070320 Firefox/

Description of problem:
The MacBook gets too hot. When running OS X, it remains cool, but FC6 had problems controlling the heat

Version-Release number of selected component (if applicable):
kernel 2.6.20-1.2948.fc6

How reproducible:

Steps to Reproduce:
Regular use.

Actual Results:

Expected Results:

Additional info:
This is a MacBook with a 2.0 Ghz Core2Duo.

Comment 1 Jarod Wilson 2007-05-14 17:45:38 UTC
What does '/sbin/service cpuspeed status' say? Sounds sorta like you don't have
any cpu throttling in effect...

Comment 2 Eelco Hoekema 2007-05-15 21:54:44 UTC
[eelco@uyuni ~]$ /sbin/service cpuspeed status
Frequency scaling enabled using ondemand governor

By the way, using Mactels coretemp utility:
[eelco@uyuni temperature]$ sudo ./coretemp 
CPU 0: 59 °C
CPU 1: 59 °C
[eelco@uyuni temperature]$ 

It doesn't get much lower than that. It seems the fan only starts when the
temperature is at 72 degrees or more.

Comment 3 Bug Zapper 2008-04-04 07:13:56 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 4 Bug Zapper 2008-05-06 19:35:51 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.