Created attachment 936078 [details] Output of # dmesg | grep -i acpi Description of problem: When using ACPI, my laptop overheats and I have no control over the fan speed. Actually, I cannot control fan in any way. Although one may argue that 65-70 C is not "overheating" and it is safe for the CPU, the laptop becomes almost unusable (expecially the trackpad), and in the past it was cooler and usable (sorry but I cannot identify when this issue started to happen). My laptop is an Acer Aspire 4830TG, w/ CPU Intel Core i5-2410M. Sensors just cannot find the fans: sensors-detect will find the coretemp module, which I think is fine, but even loading it, I have no fan available. # sensors coretemp-isa-0000 Adapter: ISA adapter Physical id 0: +57.0°C (high = +86.0°C, crit = +100.0°C) Core 0: +55.0°C (high = +86.0°C, crit = +100.0°C) Core 1: +57.0°C (high = +86.0°C, crit = +100.0°C) # find /sys -name fan /sys/bus/acpi/drivers/fan # ls /sys/bus/acpi/drivers/fan bind uevent unbind A fan is found by dmidecode though, but I don't know what to do with this info # dmidecode | grep -i -A 5 fan Type: Fan Status: OK OEM-specific Information: 0x00000000 Nominal Speed: 2000 rpm Description: Cooling Device Description. Booting with acpi=off in grub, will partially fix the issue, because the fans will actually run faster and the temperature drops a bit (still hot, anyway). Finally, dobby, on the forum (see below), suggested me that my ACPI tables are broken. I'm not sure about what to do regarding this, but I attach you a log so you can check. Additional info: A complete discussion of this issue is on the forum: http://forums.fedoraforum.org/showthread.php?t=300617
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
$ uname -r 3.17.2-200.fc20.x86_64 Bug not solved and situation is still exactly the same.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.18.7-100.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
Created attachment 1024573 [details] dmesg | grep -i acpi for the current kernel Updating for the current kernel and release.
Still experiencing the issue with F21. Same status - no fan visible using sensors - no fan node in /sys - Fan listed using dmidecode Temperature still high, fan can't be regulated.
Confirming this bug on my Gateway NV57H43u (i5-2410M) temp stays around 58°C until doing something like Minecraft or other cpu-intensive tasks, where it jumps to around 98°C and mcelog complains like crazy no fan node in /sys no fan detected in lm_sensors output fan listed via dmidecode: Type: Fan Status: OK OEM-specific Information: 0x00000000 Nominal Speed: 2000 rpm Description: Cooling Device Description. current kernel: 4.0.4-202.fc21.x86_64
Created attachment 1035735 [details] journalctl -t mcelog --since 15:30 the sort of thing I see constantly while doing something cpu-intensive like Minecraft
Is this bug still occurring in F22? If so, we should bump the bug version.
Confirming bug still exists in Fedora 22. boot from live USB, install lm_sensors, run sensors-detect. no fan info. tlp also thinks there is no fan, yet dmidecode clearly finds the same info as before. I would still like to see this fixed in F21 as well though.
confirming problem still exists with recent update kernel-4.0.5-200.fc21.x86_64
It is my opinion that the severity of this bug should be bumped to High, as not only does the constant throttling affect performance, but the high temperatures that occur until throttling can also damage components over time. The laptop's trackpad becomes unusable at these times as well, because of the temperature. This is also a regression from previous kernels (occurring somewhere between F16 and F20) as I am completely certain this functionality was present on my system when it was still running F16.
I confirm the bug is still present in F22 with kernel 4.0.6-300.fc22.x86_64. I noticed changes in /sys, but still unable to control the fan and no fan listed in sensors: /sys/bus/platform/drivers/acpi-fan /sys/bus/platform/drivers/acpi-fan/bind /sys/bus/platform/drivers/acpi-fan/uevent /sys/bus/platform/drivers/acpi-fan/unbind I agree in changing the severity: with summer this is becoming a major issue :P
I'm going to change the severity for you, but I don't know if the Kernel team in charge of this question is actually fixing this issue. I think you guys need to track down the people that can help you fix this issue and make sure they fix the problem. Some teams don't look in Bugzilla or aren't getting emails about bugs, so you guys might want to try tracking down the people responsible on IRC.
derp, clicked the wrong link in the email, blindly -- wasn't trying to unsubscribe from this. Anyway, Since I'm more than a little sure this feature worked fine in Fedora 16, I'm going to try testing the intervening versions (17-19) as well, via virtualboxes and see if I can more closely determine exactly when the regression occurred.
confirming bug still present for F21 recent update kernel-4.1.3-100.fc21.x86_64
confirming bug still present in kernel-4.1.4-100.fc21.x86_64 kernel-4.1.5-100.fc21.x86_64 kernel-4.1.6-100.fc21.x86_64 kernel-4.1.7-100.fc21.x86_64
confirming bug still present in kernel-4.1.8-100.fc21.x86_64
confirming bug still present in kernel-4.1.10-100.fc21.x86_64 kernel-4.1.12-101.fc21.x86_64
so you need to change the wording on "submit only my new changes" that you get when you accidentally double click the save changes button, because it gives the false impression it was going to save ONLY one of the two, and yes I realize that one of the other options was throw away one. I would have chosen to use ALSO rather than ONLY in the other sentence.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
>$ uname -r 4.10.17-200.fc25.x86_64+debug Bug not solved and situation is exactly the same.
we are now in Fedora 25, kernel 4.11.5-200.fc25.x86_64+debug bug not solved and situation is exactly the same.
Please bump this bug to Fedora version 25 so it can be held open kernel 4.11.8-200.fc25.x86_64 bug not solved and situation is exactly the same
Also for the record, I finally got around to loading a bunch of Fedora versions on USB sticks and booting to them, installing various devtools (lm_sensors, acpitool, etc) and trying to see if the fan is detectable with ACPI loaded. All the way back to Fedora 14. no luck. This bug is much older than I had surmised.
kernel 4.11.11-200.fc25.x86_64 bug not solved and situation us exactly the same
Created attachment 1305117 [details] acpidump-acpica file from my NV57H43u laptop w/ i5-2410M cpu on the off chance that this may help debug the issue, attached is a dump from acpidump-acpica on my system
kernel-4.12.13-200.fc25.x86_64 kernel-4.12.14-200.fc25.x86_64 kernel-4.13.5-100.fc25.x86_64 bug not solved and situation is exactly the same.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.