You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also please copy or attach ~/.local/state/gotop/errors.log if it exists and contains logs:
06:21:04 temp.go:18: error updating temp for Thermal zone 0: exit status 1
06:21:04 temp.go:18: error updating temp for CPU 0 : exit status 1
06:21:09 temp.go:18: error updating temp for CPU 0 : exit status 1
06:21:09 temp.go:18: error updating temp for Thermal zone 0: exit status 1
06:21:14 temp.go:18: error updating temp for CPU 0 : exit status 1
06:21:14 temp.go:18: error updating temp for Thermal zone 0: exit status 1
06:21:19 temp.go:18: error updating temp for CPU 0 : exit status 1
06:21:19 temp.go:18: error updating temp for Thermal zone 0: exit status 1
06:21:24 temp.go:18: error updating temp for CPU 0 : exit status 1
06:21:24 temp.go:18: error updating temp for Thermal zone 0: exit status 1
06:21:29 temp.go:18: error updating temp for CPU 0 : exit status 1
06:21:29 temp.go:18: error updating temp for Thermal zone 0: exit status 1
06:21:34 temp.go:18: error updating temp for Thermal zone 0: exit status 1
06:21:34 temp.go:18: error updating temp for CPU 0 : exit status 1
06:21:39 temp.go:18: error updating temp for CPU 0 : exit status 1
06:21:39 temp.go:18: error updating temp for Thermal zone 0: exit status 1
06:21:44 temp.go:18: error updating temp for CPU 0 : exit status 1
06:21:44 temp.go:18: error updating temp for Thermal zone 0: exit status 1
06:21:49 temp.go:18: error updating temp for CPU 0 : exit status 1
06:21:49 temp.go:18: error updating temp for Thermal zone 0: exit status 1
06:21:54 temp.go:18: error updating temp for CPU 0 : exit status 1
06:21:54 temp.go:18: error updating temp for Thermal zone 0: exit status 1
Using Gotop 4.0.1 with the -f switch on FreeBSD 12.1 results in really high CPU temps being reported. So much so I'm pretty sure things would be melting if that was the correct value. In the attached screenshot gotop is running on the right, and the left is the CPU temp (in Celsius) as reported by the sysctl utility. In it sysctl reports that the temp for each core is 47.6C which looks about right for the "CPU 0" temp reported by Gotop but the next line says the temp is 25,467F.
So either my CPU can melt steel or something off with the values reported by gotop 🤷♂️
The text was updated successfully, but these errors were encountered:
Occasionally conversion bugs show up on some non-Linux systems, like the code expecting C and getting F. This looks more like a floating point rounding error. Thanks for the report.
I'm pulling this out of the next release; I don't have access to a FreeBSD machine, and sysctl on QEMU returns no CPU thermal information. I'm stuck as how to proceed debugging this until I get a VM that provides data, probably through renting.
gotop version:
gotop 4.0.1
OS/Arch:
12.1-RELEASE-p7
Terminal emulator:
Urxvt
Any relevant hardware info:
AMD Ryzen 7 1700 Eight-Core Processor
Also please copy or attach
~/.local/state/gotop/errors.log
if it exists and contains logs:Using Gotop 4.0.1 with the
-f
switch on FreeBSD 12.1 results in really high CPU temps being reported. So much so I'm pretty sure things would be melting if that was the correct value. In the attached screenshot gotop is running on the right, and the left is the CPU temp (in Celsius) as reported by thesysctl
utility. In itsysctl
reports that the temp for each core is 47.6C which looks about right for the "CPU 0" temp reported by Gotop but the next line says the temp is 25,467F.So either my CPU can melt steel or something off with the values reported by gotop 🤷♂️
The text was updated successfully, but these errors were encountered: