Cisco Cisco IOS Software Release 12.4(4)T

Cisco IOS Release 12.4(20)T3 is a rebuild release for Cisco IOS Release 12.4(20)T. The caveats in this 
section are resolved in Cisco IOS Release 12.4(20)T3 but may be open in previous Cisco IOS releases. 

CSCsg84765

Symptoms: A MWAM-SSG processor may reload automatically with the following error message:

%ALIGN-1-FATAL: Corrupted program counter pc=0x0 , ra=0x21A8C118 , sp=0x45E7D7D0

Conditions: The symptom is observed with MWAM in a Cisco 7600 series router that is running 
Cisco IOS Release 12.4(3b).

Workaround: There is no workaround. 

CSCsi43340

Symptoms: DSMP is not programming the DSP for supervisory tone while alerting tone is there, 
which leads to FXO disconnect supervision issue.

Conditions: Occurs on routers running Cisco IOS Release 12.3(14)T and later releases.

Workaround: Downgrade to Cisco IOS Release 12.3(11)T. 

CSCsj93465

Symptoms: A PRE-3 may crash at the “pppatm_pas_fs” function.

Conditions: This symptom is observed on a Cisco 10000 series that runs the c10k3-p11-mz image 
of Cisco IOS Release 12.2(31)SB1 and that is configured for PPP. The symptom occurs after a write 
operation. The symptom may not be platform-specific.

Workaround: There is no workaround. 

CSCsk43926

Symptoms: High CPU usage may occur interrupt context on an RP, and spurious memory accesses 
may be generated when a route-map update is checked. You can verify this situation in the output 
of the show align command.

Conditions: This symptom is observed on a Cisco 7600 series that is configured for BGP.

Workaround: There is no workaround. 

CSCsk45399

Symptoms: A device might crash when the QoS configuration is changed.

Conditions: This symptom is observed on a device that has a QoS configuration.

Workaround: There is no workaround.

CSCsl46159

Symptoms: When the cost-minimization feature is used in OER, prefixes are moved to minimize the 
cost, but it never reaches a stable point. In other words, prefixes are moved back and forth 
periodically.

Conditions: This symptom is observed only if OER cost-minimization is configured.

Workaround: There is no workaround.