Skip to content

Commit 8493901

Browse files
authored
[platform][arista] Fix NVMe sensor chip address in sensors.conf for 7060X6-64PE-B (sonic-net#22639)
Why I did it The sensors.conf file was referencing a non-existent NVMe PCI address (nvme-pci-0500) on the Arista-7060X6-64PE-B platform. This mismatch caused pmon#sensord to 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 Microsoft ADO (number only): 32849896 How I did it Modified sensors.conf to change the chip identifier from nvme-pci-0500 to nvme-pci-0400 to match the actual hardware PCI bus location. How to verify it Verified that the /dev/nvme* devices are present and functional Confirmed correct PCI ID using lspci $ show plat sum Platform: x86_64-arista_7060x6_64pe_b HwSKU: Arista-7060X6-64PE-B-C512S2 ASIC: broadcom ASIC Count: 1 Serial Number: XXXXXXXX Model Number: DCS-7060X6-64PE-B Hardware Revision: 02.00 $ lspci -nn | grep -i nvme 04:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation E18 PCIe4 NVMe Controller [1987:5018] (rev 01) Edited sensors.conf and restarted pmon (systemctl restart pmon) Monitored logs to ensure pmon#sensord no longer reports I/O errors for nvme/#7
1 parent 231e18a commit 8493901

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

device/arista/x86_64-arista_7060x6_64pe_b/sensors.conf

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ chip "max6581-i2c-27-4d"
88
ignore temp7
99
ignore temp8
1010

11-
chip "nvme-pci-0500"
11+
chip "nvme-pci-0400"
1212
# TODO: sensors complaining about tempX_min and tempX_max
1313
ignore temp2
1414
ignore temp3

0 commit comments

Comments
 (0)