686a1df5c3
Co-authored-by: Zhi Yuan (Carl) Zhao <zyzhao@arista.com> Why I did it Arista 7060 platform has a rare and unreproduceable PCIe timeout that could possibly be solved with increasing the switch PCIe timeout value. To do this we'll call a script for this platform to increase the PCIe timeout on boot-up. No issues would be expected from the setpci command. From the PCIe spec: "Software is permitted to change the value in this field at any time. For Requests already pending when the Completion Timeout Value is changed, hardware is permitted to use either the new or the old value for the outstanding Requests, and is permitted to base the start time for each Request either on when this value was changed or on when each request was issued. " How I did it Add "platform-init" support in swss docker similar to how "hwsku-init" is called, only this would be for any device belonging to a platform. Then the script would reside in device data folder. Additionally, add pciutils dependency to docker-orchagent so it can run the setpci commands. How to verify it On bootup of an Arista 7060, can execute: lspci -vv -s 01:00.0 | grep -i "devctl2" In order to check that the timeout has changed. |
||
|---|---|---|
| .. | ||
| Arista-7060CX-32S-C32 | ||
| Arista-7060CX-32S-D48C8 | ||
| Arista-7060CX-32S-Q32 | ||
| plugins | ||
| Arista-7060CX-32S-C32-T1 | ||
| default_sku | ||
| fancontrol | ||
| platform_reboot | ||
| platform-init | ||
| sensors.conf | ||