This appears to be the same issue found during kernel testing on KBL HP laptop. I suspect it is missing the firmware which is not yet available. During kernel testing I found the fan ran full speed occasionally after resume, 2x from 7 resumes. Once it starts running it doesn't stop, even with a reboot. It only stops following a complete cold boot. It now seems to do so shortly after login following a cold boot aswell. Noticed mainly on battery power. Nothing appears to be consuming unnecessary cycles and sensors data looks OK. # sensors coretemp-isa-0000 Adapter: ISA adapter Physical id 0: +34.0°C (high = +100.0°C, crit = +100.0°C) Core 0: +33.0°C (high = +100.0°C, crit = +100.0°C) Core 1: +32.0°C (high = +100.0°C, crit = +100.0°C) pch_skylake-virtual-0 Adapter: Virtual device temp1: +32.0°C acpitz-virtual-0 Adapter: Virtual device temp1: +70.0°C Will attach dmesg, journal and cpu info.
Created attachment 9566 [details] cpu.txt cat /proc/cpuinfo
Created attachment 9567 [details] dmesg.txt
Created attachment 9568 [details] journal.txt from this boot
It's really hit & miss. Quite unpredictable. Suspended with the fan still running and on resume it had stopped and all is well again. $ uname -a Linux localhost.localdomain 4.9.40-desktop-1.mga6 #1 SMP Fri Jul 28 00:49:58 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Still valid kernel-desktop-4.14.30-desktop-3.mga6 Anecdotally - It seems to occur after resuming on battery after suspending on power, or the other way around too when resuming on power after suspending on battery. Suspend/resume on current power provisioning clears it.
Summary: Kaby Lake fans running for no reason - requires cold boot to stop => Kaby Lake fans running for no reason - requires cold boot or suspend/resume to stop
Also, the fan doesn't start right away. As if the first time it's needed it just ramps up, beyond normal speed for light use, and forgets to stop.
Have you checked if there is newer bios or ec firmware for that system yet?
Updated uefi last week on it using a HP utility in a windows partition. Incidentally, it nuked the boot priority and mageia from the settings completely, leaving only windows accessible, but miraculously maintained all other settings. (fixed with "boot from efi file" and efibootmgr)
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 6's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Best regards, Aurélien Bugsquad Team
Status: NEW => RESOLVEDCC: (none) => ouaurelienResolution: (none) => OLD