fix zero temp (#467) #840
Merged
fix zero temp (#467) #840
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
this fixes #467 at least on AWS. The issue is that
found_sensorscontains some random sensor that isn't even really showing any temperature (/sys/devices/pci0000:00/0000:00:04.0/nvme/nvme0/hwmon0/temp1_on my system).My 'fix' is to just ignore nvme devices as temperature sensors. I suspect that on other systems other strange sensors may show up, but on my AWS VM at least, this solves the issue: temperature is just not showing (which is correct as no real temp sensor is showing up in
/sys)