Hi Team
i have a case want dissus with all of team. i have 3 ASR 9010 devices with dual RSP-4G, but i can't understand why all of them has rebooting problem.
Last week, we must cut off the electric system but we forgot power off the device, and after that, it restart and the second RSP can't boot IOS XR software.
i tried other way in rommon mode, but nothing changes. I think this RSP have problem and need replace new one.
Here some output console logging when it rebooting, please check and recommend me some ideas about it.
Thanks
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
POST 3 : PASSED : code 0 : Slot ID/Board Type Validity
PCI-E1: Ready as Root Complex
PCI-E2: Ready as Root Complex
set_chassis_type: chassis_type=0xef02fe found=TRUE
ASR9K (8641D PPC) platform with 4096 Mb of main memory
program load complete, entry point: 0x100000, size: 0x2ac20
program load complete, entry point: 0x100000, size: 0x2ac20
MBI Candidate = disk0:asr9k-os-mbi-3.9.2/mbiasr9k-rp.vm
CARD_SLOT_NUMBER: 5
CPU_INSTANCE: 1
MBI Validation starts ...
Mgt LAN 0 interface is selectedInterface link changed state to UP.
Interface link state up.
MBI validation sending request.
HIT CTRL-C to abort
..........
No MBI confirmation received from dSC
AUTOBOOT: Boot string = disk0:asr9k-os-mbi-3.9.2/mbiasr9k-rp.vm,1;
AUTOBOOT: autobootstate=0, autobootcount=0, cmd=boot disk0:asr9k-os-mbi-3.9.2/mbiasr9k-rp.vm
program load complete, entry point: 0x100000, size: 0x2ac20
MBI size from header = 11371848,Bootflash resident MBI filesize = 11371848
............................................
program load complete, entry point: 0x1fcf28, size: 0xad7648
Attempting to start second CPU
SMP initialized.
Config = SMP, Running = SMP
######################################################
BSP: Board type : RO-RSP2
tracelogger: starting tracing in background ring mode
tracelogger running with args: -startring -F 1 -F 2
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagiraph
(c) of then Commercial Compiuter Software - tRestricted
Righ:ts clause at FAR sec. 52.227-19 'flashdrvrand subparagraph'
(c) (1) (ii) o abnormally f the Rights in tTechnical Data aerminated, rnd Computer
Sofespawn count 1 (1,1,256)
tware clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
init: 'flashdrvr' abnormally terminated, respawn count 2 (1,1,256)
170 West Tasman Drive
San Jose, California 95134-1706
init: 'flashdrvr' abCisco IOS XR Sofnormally terminated, respawn count 3 (1,1,256)
tware for the Cisco XR ASR9K, Version 3.9.2
Copyright (c) 2009 by Cisco Systems, Inc.
init: 'flashdrvr' abnormally terminated, respawn count 4 (1,1,256)
init: respawn 'flashdrvr' disabled, INIT_MAX_SPAWN reached (1)
Writing crashinfo
Active processes:
asr9k-os-3.9.2/bin/init Thread ID 2 on cpu 0
Active processes:
pkg/bin/i2c-master Thread ID 0 on cpu 1
[0x05b654b63] Record Reboot History, reboot cause = 0x2c000007, descr = Cause: LITE: respawn 'flashdrvr' disabled, exit_code 256, INIT_MAX_SPAWN reached Process: init Traceback: 4c0d6a78 4[0x05db3c6be] Record crashinfo
[0x05e01b8ff] Record Syslog
1970-01-01 00:00:08.771
NOTE: This is NOT a Kernel Crash. This crash was triggered
by the process 'init', by calling reboot API.
Crash Reason: Cause: LITE: respawn 'flashdrvr' disabled, exit_code 256, INIT_MAX_SPAWN reached Process: init Traceback: 4c0d6a78 4c0d6c88 40007324 4c0ef17c 4c0e9d34 400037c4 (Cause Code: 0x2c000007)
Exception at 0x4c0d6d1c signal 5 c=1 f=3
Active process(s):
asr9k-os-3.9.2/bin/init Thread ID 2 on cpu 0
pkg/bin/i2c-master Thread ID 0 on cpu 1
REGISTER INFO
r0 r1 r2 r3
R0 4c0d6d70 9bf5ddb0 5000f180 00000000
r4 r5 r6 r7
R4 00000000 00000000 9bf5dd88 00000000
r8 r9 r10 r11
R8 540be400 00000000 2de4ddba 00000000
r12 r13 r14 r15
R12 50004e23 5000f180 00000000 00000000
r16 r17 r18 r19
R16 00000000 00000000 00000000 00000000
r20 r21 r22 r23
R20 50006f10 50000000 50007678 50000000
r24 r25 r26 r27
R24 9bf5def0 00000000 9bf5df58 50000000
r28 r29 r30 r31
R28 ec010000 9bf5ddbc ec00b884 00000000
cnt lr msr pc
R32 4c04e298 4c0d6d70 0002d932 4c0d6d1c
cnd xer
R36 24004088 00000000
SUPERVISOR REGISTERS
Memory Management Registers
Instruction BAT Registers
Index # Value
IBAT0U # 0x1ffe
IBAT0L # 0x12
IBAT1U # 0
IBAT1L # 0
IBAT2U # 0
IBAT2L # 0
IBAT3U # 0xfffc0003
IBAT3L # 0x40011
IBAT4U # 0x4c0007ff
IBAT4L # 0x74000011
IBAT5U # 0
IBAT5L # 0
IBAT6U # 0
IBAT6L # 0
IBAT7U # 0
IBAT7L # 0
Data BAT Registers
Index # Value
DBAT0U # 0x1ffe
DBAT0L # 0x12
DBAT1U # 0x34000002
DBAT1L # 0xdc00002a
DBAT2U # 0x3000001e
DBAT2L # 0xc800002a
DBAT3U # 0xfffc0003
DBAT3L # 0x40011
DBAT4U # 0x4c0007ff
DBAT4L # 0x74000011
DBAT5U # 0
DBAT5L # 0
DBAT6U # 0
DBAT6L # 0
DBAT7U # 0
DBAT7L # 0
Exception Handling Registers
Data Addr Reg # DSISR
0x6012c000 # 0x40000000
SPRG0 # SPRG1 # SPRG2 # SPRG3
0 # 0xec00b884 # 0x9bf5ddbc # 0
SaveNRestore SRR0 # SaveNRestore SRR1
0x4c0d6d18 # 0x2d932
Miscellaneous Registers
Processor Id Reg # 0
HID0 # 0x8493c1bc
HID1 # 0x2cc80
MSSCR0 # 0x8000
MSSSR0 # 0
STACK TRACE
#0 0x4c0d6d70
[0x0803a457a] Initializing harddisk file system
[0x08495b4dc] Record TSEC information
!!
Writing TSEC done
!
Writing crashinfo done!
Examine crashinfo file for reboot reason
Writing ppc kernel core file
[0x0862d199f] Kernel core dump start...
fill phdr vaddr=0xfe8a000, offset=0x34fd494, size=0x176000
!!!!!!!!!!!!!!!!!!!!!!!!!!
Core dump success. Total_size 57095316
[0x09386311e] Successfully dumped Kernel core
[0x093ef1f47] Record PCDS information
Writing PCDS done
Dump Directory
KD: RSP1.700101-000008.tsec, start = 1000, size = 4000, crc = 0
KD: RSP1.700101-000008.crashinfo.by.init, start = 5000, size = ae5a, crc = 0
KD: RSP1.700101-000008.kernel_core.by.init.Z, start = 10000, size = 25f5d3, crc = 22f228a4
KD: RSP1.700101-000008.pcds, start = 270000, size = ff000, crc = 18ff3d46
Writing kernel core file done!
rebooting
