FPC restart occurred due to a SIOC down condition, triggered by delayed responsiveness of the "ata5" (ATA/SATA) link. The link was slow to initialize, which caused the NMI timer to expire, leading to a protective restart of the FPC.

The issue can be identified with the following log sequence:

• Kernel logs indicating ATA link delay:

kernel: ata5: link is slow to respond, please be patient (ready=0)
kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

• Chassis logs showing NMI timeout and FPC restart:

LCC: fru_nmi_timer: NMI timer expired for FPC 1
LCC: fru_trigger_nmi: No NMI support for FPC slot 1
CHASSISD_FRU_NMI_RESTART: Restart FPC 1 due to NMI timeout

Steps:

• Check kernel logs for ATA/SATA link delay messages such as:
  • "link is slow to respond"
• Correlate with:
  • NMI timeout logs
  • FPC restart events

Action:

If these logs are observed, open a JTAC ticket for further investigation and provide:

• Kernel logs
• /var/logs/
• Exact event timestamps

This behavior may indicate an underlying hardware or subsystem responsiveness issue that requires deeper analysis.