Users experience a persistent issue where the routing engine enters a hung state upon executing "chassis" commands, leading to the generation of core dumps by the chassisd daemon. The problem is seen along with readback errors for various Field Replaceable Units (FRUs), starting with FPM (Front Panel Module) and extending to other FRUs.

Routing engine prompt remains unresponsive when "chassis" commands are issued, accompanied by the generation of coredumps by the chassisd daemon. Readback errors initially occur for multiple FRUs, with FPM being the first affected.

Logs :

 In the log messages, you will see readback errors for all the FRUs starting with FPM

Feb 14 19:30:00 chassisd[81326]: CHASSISD_I2CS_READBACK_ERROR: Readback error from I2C slave for FPM 0 ([0x2a, 0x13] -> 0x0)
Feb 14 19:30:00 kernel: tcbc i2c accelerator error: Group 0x2a device 0x54 cmd timedout 9000 usecs
Feb 14 19:30:00 kernel: tcbc i2c accelerator error: Write failed for (FPD1) group 0x2a device 0x54 bytes 1 err 60
Feb 14 19:30:00 kernel: tcbc i2c accelerator error: Group 0x2a device 0x54 cmd timedout 8002 usecs

Check for Abnormalities Regarding FPM:

• Temporarily remove FPM and observe if FPM logs cease. Replace FPM and monitor for issue resolution. If the problem persists, proceed to the next step.

RE Switchover:

• If step 1 does not resolve the issue, perform a Routing Engine (RE) switchover. If the problem is resolved with the other CB as the master, replace the original CB to address the issue.