1) Check if the slave RSP is halted by issuing the show version command. Look toward the end of the output for the line regarding the slave, as shown in this example:
Router#show version
Cisco Internetwork Operating System Software
IOS (tm) RSP Software (RSP-JSV-M), Version 12.2(13)T, RELEASE SOFTWARE (fc1)
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Sat 16-Nov-02 02:29 by ccai
Image text-base: 0x60010948, data-base: 0x61F00000
!---unncessary part removed
47040K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
16384K bytes of Flash internal SIMM (Sector size 256K).
Slave in slot 2 is halted. <========================================= Look Here
Configuration register is 0x2102
2) If the slave is halted, issue the slave reload global configuration command, as shown in this example:
router(config)#slave reload
3) After the slave reload is complete, issue the write memory or copy running-config startup-config command to check if the error message reoccurs.
Note: Even if the slave does not appear to be halted, issuing the slave reload command may resolve the problem. This is because the issue might not be a halted slave, but a communication problem across the bus between the master and slave RSPs.
4) If after issuing the slave reload command, the error message still appears, physically remove and reinstall the slave RSP.
5) If after reseating the slave RSP, the error continues, the slave RSP may be defective and needs to be replaced.