Bug 677619

Summary: Asus EeeTop ET1610: hot CPU, no audio
Product: [Fedora] Fedora Reporter: Gabriele Turchi <turchi>
Component: kernelAssignee: John Feeney <jfeeney>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 14CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 21:32:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
powertop -d output none

Description Gabriele Turchi 2011-02-15 11:42:06 UTC
Description of problem:

Installing Fedora 14 on a new version Asus EeeTop ET1610 the CPU (Atom D410, 1.66 GHz) became immediately really hot (minimum temp about 70C, with fan always running), and no sound is available.

Version-Release number of selected component (if applicable):

Tried with 32 (PAE and not) and 64 bits versions (2.6.35.11-84). Even with current rawhide 32 bits kernel (2.6.38-0.rc4.git0)


How reproducible:

Always

Steps to Reproduce:
1. Install the system (or start a Live Image)
2.
3.
  
Actual results:

High CPU temperature and no audio.


Expected results:

Lower temperature and no fan running (at least when load is close to 0).

Additional info:

Usual load < 0.1

Ondemand cpufreq governor is not available, and lowering by hand cpu speed (even to lower 208 MHz from 1.66 GHz) doesn't help).

Tested with hyperthreading enabled and disabled.

Comment 1 Gabriele Turchi 2011-02-15 12:30:25 UTC
Alsamixer reports a Realtek ALC887.

For the audio problem, I found a workaround here, and is working for me:

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5047

Comment 2 Matthew Garrett 2011-02-24 19:33:25 UTC
Can you install powertop, make sure the system is idle, then (as root) run 

powertop -d >powertop.out

Don't touch the machine while it's running. Once it's finished, attach powertop.out to this bug.

Comment 3 Gabriele Turchi 2011-03-01 11:20:46 UTC
Created attachment 481594 [details]
powertop -d output

Comment 4 Matthew Garrett 2011-03-04 23:42:49 UTC
Ok. The D410 doesn't support speedstep and has no worthwhile low-power idle state support, so I'd expect it to run reasonably hot. However, 70C does seem excessive. There's nothing in your powertop output to indicate that the system is excessively active. Have you run any other versions of Linux on this hardware, and if so do they behave the same way?

Comment 5 Gabriele Turchi 2011-03-28 12:50:23 UTC
I haven't (yet) run other Linux versions on the same hardware, I'll try as soon as I can.

Apparently, when the CPU warms up, the fan is accelerated to cold it, but when the fan stops the temperature is higher than before, like some sort of "inverted hysteresis". 

Obviously then, the time between a fan startup and the next is becoming shorter and shorter, until the fan runs continuously, fast and noisy.

I think that forcing the fan to remain faster until reaching a lower temperature could be a solution.


P.S.: My apologizes for my bad english...

Comment 6 Fedora End Of Life 2012-08-16 21:32:14 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping