Issue #18 Detect failed memory#19
Merged
czerwonk merged 1 commit intoMauveSoftware:mainfrom Dec 6, 2025
Merged
Conversation
ChrisPortman
force-pushed
the
failed-mem-has-no-status
branch
from
922c491 to
6a68dc3
Compare
czerwonk
approved these changes
Dec 6, 2025
This file contains hidden or 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
2 participants
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.
This change additionally looks at
Oem.Hpe.DIMMStatusif there is no top levelStatusfield in a attempt to positively determine the health status of a memory DIMM.As per the Issue, at least the Gen10 Ilos, appear to report a healthy status under
.Status.Health, however completely omit the.Statusstructure when unhealthy.