Полезная информация

cc/td/doc/product/software/ios120/12supdoc
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

System Failure Error Messages

System Failure Error Messages

This section discusses other types of error messages that you may encounter (such as bus, parity, timeout, unexpected, and unknown error messages).

These error messages result when the system image crashes, either from a hardware or a software failure. To access these messages, use the bootstrap program.

When you encounter a timeout, bus error, or unknown error message, you must run the k stack trace command at the bootstrap mode prompt (>) to display the stack trace results.

In the following example, a timeout error message appears, the k stack trace command is run, but no stack trace results:

Timeout (control reg=0xCF10) Error, address: 0xFFFFFFE8 \
at 0x317D49E (PC) >k
No stack to dump (NULL frame pointer)

In the following example an unknown error message appears, the k stack trace command is run, and a stack trace results:

Unknown (control reg=0x10) Error, address: 0xD0D0D0D at 0x313DC22 (PC)
>k
Current PC: 0x313DC22
FP: 0xE6620 RA: 0x31411A8
FP: 0xE6634 RA: 0x3123D1C
FP: 0xE6650 RA: 0x312303A
FP: 0xE6668 RA: 0x3133664
FP: 0xE667C RA: 0x31337D2
FP: 0xE6694 RA: 0x31349DA
FP: 0xE66A0 RA: 0x3014B4C

Table 8 describes the fields in this sample stack trace.


Table 8:
Field Description

Current PC: 0x313DC22

Address at which the failure occurred. This address is also called the program counter (PC).

FP: 0xE6620

Stack frame pointer.

RA: 0x31411A8

Program counter of calling function saved in stack frame. This value is used to trace the flow of software function calls leading to the failure.

Stack Trace Fields

After you obtain the stack trace, use the i (initialize) command before you manually boot up the system image. Then use the show version command (when possible) to identify the software release and version number for use by technical staff.

On systems that have a hardware or virtual (software) configuration register and the boot bits (lowest four bits) set to a value greater than zero, the system will repeatedly try to boot up the appropriate system image from resident ROMs, Flash memory, or a server over the network. If the booting is successful, the system prompt appears. You then can use the show stack command to obtain the stack trace.

In cases where the router crashes repeatedly, send a Break character from the console keyboard to obtain the bootstrap mode prompt. Then modify the configuration register boot bits to zero, enter the i (initialize) command, and manually attempt to bootstrap the system image. If it crashes, use the k  stack trace command.


Error Message   
Bus Error control register: [hex]
non-local memory transaction timeout
Bus Error, address: [hex] at [hex] (PC)

Explanation   An invalid memory address is accessed, either because of a software bug or because a boot of an incompatible software image was attempted.

Recommended Action   If the error occurred when your tried to boot up a system image over the network or from reprogrammed Flash memory, a probable reason could be the use of a wrong or incompatible system image. Look in the appropriate documentation to find out which system image to use. If you still need assistance, contact your technical support representative with the following details:

If the error occurred while trying to boot up a built-in ROM-based image, contact your technical support representative with the following details:

If the error occurred while the system was operational, contact your technical support representative after gathering the following information:


Error Message   
Bus Error control register: [hex]
ram byte ([value]) parity error
Bus Error, address: [hex] at [hex] (PC)

Explanation   Memory corruption or failure has occurred, most likely because of a hardware problem or by disturbances such as power line problems.

Recommended Action   Reboot the system and observe whether the problem recurs. Also ensure that the power line has appropriate protection equipment. If the problem is a one-time occurrence, the cause could be a power line disturbance.


Error Message   
Bus Error control register: [hex]
system overtemp
Bus Error, address: [hex] at [hex] (PC)

Explanation   Temperature exceeded the operating range, most likely because of a ventilation, air-conditioning, or hardware problem.

Recommended Action   Power off the system and give it time to cool. Check room ventilation and air conditioning. Also ensure that system air-flow grids are not blocked and that blowers are operational. Call your technical support representative if a blower needs replacement.


Error Message   
Local Timeout (control reg=[hex]) Error, address: [hex] at [hex] (PC)

Explanation   An invalid memory address is accessed, either because of a software bug or because a boot of an incompatible software image was attempted.

Recommended Action   Refer to the Recommended Action for the first "Bus Error control register" message in this section.


Error Message   
Multibus Timeout (control reg=[hex]) Error, address: [hex] at [hex] (PC)

Explanation   An invalid memory address is accessed, either because of a software bug or because of incompatible microcode in a multibus card.

Recommended Action   Reseat the card. If this message recurs, call your technical support representative for assistance.


Error Message   
Parity (control reg=[hex]) Error, address: [hex] at [hex] (PC)

Explanation   Memory corruption or failure has occurred, most likely because of a hardware problem. Disturbances such as power line problems are also possibilities.

Recommended Action   Reboot the system and observe whether the problem recurs. Also ensure that the power line has appropriate protection equipment. If the problem is a one-time occurrence, the cause could be a power line disturbance. If this message recurs, call your technical support representative for assistance.


Error Message   
Shared Memory Parity Error
shared memory control register = [hex]
error caused by slot [dec] access in byte(s) [dec]
Shared Memory Parity Error
shared memory control register = [hex]
error caused by MPU access in byte(s) [dec]

Explanation   Shared (I/O) memory failure or corruption occurred during access by the processor. This problem is most likely due to a hardware failure or by disturbances such as power line problems.

Recommended Action   Reboot the system and observe whether the problem recurs. Also ensure that the power line has appropriate protection equipment. If the problem is a one-time occurrence, the cause could be a power line disturbance.


Error Message   
Unexpected exception to CPU vector [dec], PC = [hex]

Explanation   Either a hardware or a software problem has occurred.

Recommended Action   Refer to the Recommended Action for the first "Bus Error control register" message in this section.


Error Message   
Unexpected vectored interrupt (vector offset [dec])

Explanation   Either a hardware or a software problem has occurred.

Recommended Action   Refer to the Recommended Action for the first "Bus Error control register" message in this section.


Error Message   
Unknown (control reg=[hex]) Error, address: [hex] at [hex] (PC)

Explanation   Either a hardware or a software problem has occurred.

Recommended Action   Refer to the Recommended Action for the first "Bus Error control register" message in this section.


hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1998 © Cisco Systems Inc.