Bug 17568 - A temperature sensor is every times at 90 °
Summary: A temperature sensor is every times at 90 °
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2016-01-21 17:56 CET by Jean-Louis CURCI
Modified: 2018-10-07 16:22 CEST (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Jean-Louis CURCI 2016-01-21 17:56:31 CET 
I found a bug on starting : the sensor "temp6" of "ACPI" module gives all the time a very temperature : 90° . This temperature is not the right value .
Sometimes the others temperatures are about 20° and this one is at maximum.
I think you will find a problem with the sensors Manager on starting. May it try to access on ACPI module before that Manager is open. 
So in fact , the problem is simple : some variables  

         /sys/class/thermal/cooling_device?/cur_state

are not reseated to zero.

By executing  echo 0 >   /sys/class/thermal/cooling_device?/cur_state

Now on starting the Manager will consider that the temperatures are unknown and will not send an error signal.
I added in the script 
     /etc/rc.d/init.d/mandrake_evrytime

echo 0 >   /sys/class/thermal/cooling_device0/cur_state
echo 0 >   /sys/class/thermal/cooling_device1/cur_state
 ... etc ..

Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2016-01-22 09:33:13 CET 
what is the output (in a konsole or terminal) of 

  rpm -qa | grep kernel | grep latest

and of 

  rpm -qa | grep lm_sensors

and please also attach lspcidrake.txt that is the result of

  lspcidrake -v > lspcidrake.txt

Keywords: (none) => NEEDINFO
CC: (none) => geiger.david68210, marja11
Assignee: bugsquad => tmb
Source RPM: lip6 => kernel

Comment 2 Thierry Vignaud 2016-06-17 11:55:59 CEST 
This is not an installer bug

CC: (none) => thierry.vignaud
Component: Installer => RPM Packages

Comment 3 Marja Van Waes 2016-08-26 11:43:18 CEST 
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.

Assignee: tmb => kernel

Comment 4 Marja Van Waes 2018-04-28 21:57:25 CEST 
Hi Jean-Louis,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja
Comment 5 Marja Van Waes 2018-10-07 16:22:29 CEST 
@ Jean-Louis:

No reply, so closing as OLD since Mageia 5 is no longer maintained.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.