Closed akrychowski closed 5 months ago
Similar error here, spamming the journal
May 30 18:47:07 framework python3[3393]: ERROR: Can't get value of subfeature temp1_input: Can't read
I am also having this issue. Looks like it is unable to verify the temperature for the wifi chip iwlwifi_1-virtual-0. Unfortunately telling lm-sensors to ignore that category crashes the script.
EDIT: Oh, it only seems to happen when the wifi is disabled. I guess that makes sense.
Added pull request to send these errors to /dev/null to prevent flood of journal.
This issue should be marked fixed. The latest commit from @TamtamHero works great.
but I think that the messages are just symptom of other problem. Today I was hit again by unusual high CPU usage of the service: systemctl status fw-fanctrl.service ● fw-fanctrl.service - FrameWork Fan Controller Loaded: loaded (/etc/systemd/system/fw-fanctrl.service; enabled; preset: disabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: active (running) since Tue 2023-09-12 13:35:01 CEST; 1 day 20h ago Main PID: 212122 (python3) Tasks: 4 (limit: 18775) Memory: 5.8M CPU: 1h 51min 206ms CGroup: /system.slice/fw-fanctrl.service └─212122 /usr/bin/python3 /usr/local/bin/fw-fanctrl --config /home/arturro/.config/fw-fanctrl/config.json --no-log
CPU time almost 2hr - causing the system to be almost unusable
Closing the issue since the main problem has been fixed
Today I was hit again by unusual high CPU usage of the service:
This is probably https://github.com/TamtamHero/fw-fanctrl/issues/17
Fedora 36 kernel 6.2.12., framework gen 12th. Just notice that despite the service was in running state it was not working - CPU got 100 C and start throttling. Here is journalctl:
Before the time I can notice that the service consume a lot of CPU and also have different errors (which probably is why the FW was so quite) :