Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NAS-129059 / 25.04 / hide dimm2 and dimm3 temps on x10 #14545

Closed
wants to merge 1 commit into from

Conversation

yocalebo
Copy link
Contributor

This platform has 4x dimm slots but only 2 are populated on X10. The dimms that are not populated report a status of "OK" but the temperature is reported as -1C. This has been happening since CORE days. Fix it by not reporting those dimm sensors.

@yocalebo yocalebo requested a review from a team September 19, 2024 19:35
@bugclerk bugclerk changed the title hide dimm2 and dimm3 temps on x10 NAS-129059 / 25.04 / hide dimm2 and dimm3 temps on x10 Sep 19, 2024
@bugclerk
Copy link
Contributor

if self.model == ControllerModels.X10.value and desc.startswith(('dimm2', 'dimm3')):
# x10 platform only has 2 DIMM slots (dimm0/1) populated so the others report
# -1C temperature but the descriptor status reports as "OK".
return True
Copy link
Contributor

@mgrimesix mgrimesix Sep 19, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The x10 can never and will never support the dimm2 and dimm3 slots?
Maybe don't report if the element status is 'UNSUPPORTED' | 'NOT_INSTALLED' | 'NOT_AVAILABLE'.
Or report only if element status is 'OK' | 'CRITICAL' | 'NONCRITICAL'.

Side notes: This is starting to look like an opportunity to use the match method. These platform specific things can be messy and ever growing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's what I alluded to in my comment. The dimm module isn't populated but the descriptor still reports as "OK". So there isn't a concrete way of knowing that the module isn't populated. We basically have to make some form of assumption here.

@yocalebo yocalebo closed this Sep 20, 2024
@yocalebo yocalebo deleted the NAS-129059 branch September 20, 2024 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants