Error Reporting; Debug Commands - Cisco 1710 Software Configuration Manual

Debug Commands

Error Reporting

Debug Commands
Cisco 1710 Security Router Software Configuration Guide
A-12
Because the ROM monitor console download uses the console to perform the data
transfer, error messages are displayed on the console only when the data transfer
is terminated.
If an error does occur during a data transfer, the transfer is terminated, and an
error message is displayed. If you have changed the baud rate from the default
rate, the error message is followed by a message telling you to restore the terminal
to the baud rate specified in the configuration register.
Most ROM monitor debugging commands are functional only when Cisco IOS
software has crashed or is halted. If you enter a debugging command and Cisco
IOS crash information is not available, you see the following error message:
"xxx: kernel context state is invalid, can not proceed."
The following are ROM monitor debugging commands:
• stack or k—Produce a stack trace. For example:
rommon 6> stack
Stack trace:
PC = 0x801111b0
Frame 00: FP = 0x80005ea8
Frame 01: FP = 0x80005eb4
Frame 02: FP = 0x80005f74
Frame 03: FP = 0x80005f9c
Frame 04: FP = 0x80005fac
Frame 05: FP = 0x80005fc4
• context—Display processor context. For example:
rommon 7> context
CPU context of the most recent exception:
PC = 0x801111b0
0x80113694
CTR = 0x801065e4
0xffffffff
DEC = 0xffffffff
0xffffffff
R0 = 0x00000000
0x00000000
PC = 0x801111b0
PC = 0x80113694
PC = 0x8010eb44
PC = 0x80008118
PC = 0x80008064
PC = 0xfff03d70
MSR = 0x00009032 CR
XER = 0xa0006d36 DAR = 0xffffffff
TBU = 0xffffffff TBL = 0xffffffff
R1 = 0x80005ea8 R2
Appendix A ROM Monitor
= 0x53000035 LR
DSISR =
IMMR
= 0xffffffff R3
78-12696-01
=
=
=