The chassisd Daemon Might Be Stuck And Not Response When I2C Bus Gets Stuck with the below messages
chassisd[1077]: CHASSISD_PIPE_WRITE_ERROR: Pipe write error: Broken pipe chassisd[1077]: CHASSISD_IPC_FLUSH_ERROR: ch_flush_fru_pipe: flush operation failed for LCD 1 chassisd[1077]: CHASSISD_SIGPIPE: SIGPIPE received /kernel: i2c_wait:EBUSY: count = 50 chassisd[1077]: pem_mojito_pmbus_i2c_read Error reading i2c device:19 error num 16 /kernel: i2c_wait:EBUSY: count = 50 chassisd[1077]: pem_mojito_pmbus_read: error in reading from device:0x13 cmd:0xffffffff offset:0x8d len:2 ret_val:-1
You will see the below messages
On an EX4300 platform, when the chassisd related show command executes, it doesn't have corresponding information return, but return error message like following. This issue only impact the chassisd related commands, it doesn't has service/forwarding impact. user@hostname> show chassis environment power-supply-unit error: the chassis-control subsystem is not responding to management requests <--this error just means that chassisd is not running and is in the problematic condition. And, at the same time, continuous log messages as following might be seen in syslog: chassisd[1077]: CHASSISD_PIPE_WRITE_ERROR: Pipe write error: Broken pipe chassisd[1077]: CHASSISD_IPC_FLUSH_ERROR: ch_flush_fru_pipe: flush operation failed for LCD 1 chassisd[1077]: CHASSISD_SIGPIPE: SIGPIPE received /kernel: i2c_wait:EBUSY: count = 50 chassisd[1077]: pem_mojito_pmbus_i2c_read Error reading i2c device:19 error num 16 /kernel: i2c_wait:EBUSY: count = 50 chassisd[1077]: pem_mojito_pmbus_read: error in reading from device:0x13 cmd:0xffffffff offset:0x8d len:2 ret_val:-1 This issue stands resolved in following releases : 14.1X53-D37 14.1X53-D39 14.1X53-D40 15.1R4 External-TriggerThis issue might be seen if following conditions are met: * On an EX4300 platform * When the I2C bus gets stuck * Execute any chassisd related command at the same time, for example, "show chassis *"