Debug Commands - Cisco 1700 Manual

Debug Commands

Debug Commands
Cisco 1700 Series Router Software Configuration Guide
B-12
Most ROM monitor debugging commands are functional only when Cisco IOS
software has crashed or stopped. 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
R4 = 0x8fab0d76
0x80570000
R8 = 0x00000000
0x00000000
R12 = 0x00000080
0xffffffff
R16 = 0xffffffff
0xffffffff
R20 = 0xffffffff
0xffffffff
R24 = 0xffffffff
0xffffffff
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
R5 = 0x80657d00 R6
R9 = 0x80570000 R10 = 0x0000954c
R13 = 0xffffffff R14 = 0xffffffff
R17 = 0xffffffff R18 = 0xffffffff
R21 = 0xffffffff R22 = 0xffffffff
R25 = 0xffffffff R26 = 0xffffffff
Appendix B ROM Monitor
= 0x53000035 LR
DSISR =
IMMR
= 0xffffffff R3
= 0x80570000 R7
R11
R15
R19
R23
R27
78-5407-03
=
=
=
=
=
=
=
=
=