Bug 13636 - Laptop fan randomly slows down and causes opverheating
Summary: Laptop fan randomly slows down and causes opverheating
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-01 19:49 CEST by Pavel Kreuzt
Modified: 2015-02-16 08:15 CET (History)
1 user (show)

See Also:
Source RPM: lm_sensors
CVE:
Status comment:


Attachments

Description Pavel Kreuzt 2014-07-01 19:49:36 CEST
Since latest updates the fan stops working randomly, without much load on the processor or high temperature. It seems to happen when the system has been up for several hours without much load. Temperature then raises to 80ºC or more and sometimes causes freezing of the system, needing hard reset. After subsequent boot the fan is working at maximum power to cool down the laptop and seems to work well. Not sure if it's ACPI or kernel related, faults seem completely random and looking in both syslog, messages or kernel logs gives no clues. This Asus laptop has Optimus technology and I'm using bumblebee, but discrete graphics card is not enabled when this problem appears.
Pavel Kreuzt 2014-07-01 19:50:20 CEST

Source RPM: (none) => kernel?

Pavel Kreuzt 2014-07-05 17:50:37 CEST

Source RPM: kernel? => lm_sensors

Comment 1 Pavel Kreuzt 2014-07-05 18:21:18 CEST
Reproduced the problem with unmounted laptop, the fan is working but at a very slow rate so the air flow is negligible. So now I think it's more related to lm_sensors settings, changed report.

Summary: Laptop fan randomly stops working and causes opverheating => Laptop fan randomly slows down and causes opverheating

Comment 2 Rémi Verschelde 2015-02-14 01:57:23 CET
Sorry for the late answer Pavel. Is this bug still valid?

CC: (none) => remi

Comment 3 Pavel Kreuzt 2015-02-16 00:15:23 CET
It's been a while since last time it happened, so it can be considered as resolved.
Comment 4 Rémi Verschelde 2015-02-16 08:15:14 CET
Thanks :)

Status: NEW => RESOLVED
Resolution: (none) => OLD


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