Core Issue
The TLB (Load/Fetch) Exception error message is often the result of a bus error. This is an example of the error message:
*** System received a Bus Error exception ***
Access address = 0x3c210040
signal= 0xa, code= 0x1c, context= 0x60e632f0
PC = 0x6037668c, Cause = 0xc20, Status Reg = 0x34008002
** TLB (Load/Fetch) Exception ***
Access address = 0x4
PC = 0xbfc165f8, Cause = 0x8, Status Reg = 0x30408403
monitor: command "boot" aborted due to exception
Resolution
To resolve bus error exception and continuous loops, refer to the Hardware Failure section of Troubleshooting Bus Error Crashes.
When a hardware replacement is indicated, choose from one of these options:
- If you have a hardware support contract directly with Cisco for this part, use the Service Order Submit Tool to request a replacement part directly.
- For warranty service, contact the Cisco Technical Assistance Center (TAC) directly at 1-800-553-2447, or online by using the TAC Service Request Tool.
- If your product is not covered by contract or warranty, contact your Cisco partner or reseller to request a replacement part for the hardware component that is causing the issue.
