[platform][arista] Fix NVMe sensor chip address in sensors.conf for 7060X6-64PE-B#22639
Merged
StormLiangMS merged 2 commits intosonic-net:masterfrom May 27, 2025
Merged
[platform][arista] Fix NVMe sensor chip address in sensors.conf for 7060X6-64PE-B#22639StormLiangMS merged 2 commits intosonic-net:masterfrom
StormLiangMS merged 2 commits intosonic-net:masterfrom
Conversation
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
@rick-arista could you review the PR |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
r12f
approved these changes
May 19, 2025
Contributor
|
@sdszhang for viz. |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Commenter does not have sufficient privileges for PR 22639 in repo sonic-net/sonic-buildimage |
Contributor
Author
|
/azpw run |
Collaborator
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
Cherry-pick PR to msft-202412: Azure/sonic-buildimage-msft#1165 |
r12f
added
Included in msft-202412 Branch
and removed
Created PR to msft-202412 Branch
labels
10 tasks
Collaborator
|
Cherry-pick PR to 202505: #22781 |
liushilongbuaa
added
Included in 202505 Branch
and removed
Created PR to 202505 Branch
labels
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
9 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.
Why I did it
The
sensors.conffile was referencing a non-existent NVMe PCI address (nvme-pci-0500) on the Arista-7060X6-64PE-B platform. This mismatch causedpmon#sensordto report repeated I/O errors while attempting to read sensor data for a non-existent device (nvme/#7). Updating the config to use the correct PCI address (nvme-pci-0400) resolves the issue.Work item tracking
How I did it
Modified
sensors.confto change the chip identifier fromnvme-pci-0500tonvme-pci-0400to match the actual hardware PCI bus location.How to verify it
/dev/nvme*devices are present and functionallspcisensors.confand restartedpmon(systemctl restart pmon)pmon#sensordno longer reports I/O errors fornvme/#7Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Fix
sensors.confNVMe chip config for Arista-7060X6-64PE-B to match actual PCI address and prevent pmon sensor read errorsLink to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)