...
In some specific timing condition, BGP process may crash RP/0/RSP1/CPU0:Feb 26 03:06:29.492 KST: dumper[61]: %OS-DUMPER-7-DUMP_REQUEST : Dump request for process pkg/bin/bgp RP/0/RSP0/CPU0:Feb 26 03:06:29.494 KST: dumper[61]: %OS-DUMPER-7-PROC_PAGES : Process memory pages 1174 RP/0/RSP1/CPU0:Feb 26 03:06:29.494 KST: dumper[61]: %OS-DUMPER-7-DUMP_ATTRIBUTE : Dump request with attribute 7 for process pkg/bin/bgp RP/0/RSP1/CPU0:Feb 26 03:06:29.494 KST: dumper[61]: %OS-DUMPER-4-SIGSEGV : Thread 17 received SIGSEGV - Segmentation Fault RP/0/RSP1/CPU0:Feb 26 03:06:29.494 KST: dumper[61]: %OS-DUMPER-4-SIGSEGV_INFO : Accessed BadAddr 0x0 at PC 0xffffffff. Signal code 0 - Unknown SIGSEGV code. 0 RP/0/RSP1/CPU0:Feb 26 03:06:29.494 KST: dumper[61]: %OS-DUMPER-4-SIGNALCORE_INFO : Core for pid = 909621 (pkg/bin/bgp) as signal 11 sent by pkg/bin/bgp@node0_RSP1_CPU0 RP/0/RSP0/CPU0:Feb 26 03:06:29.496 KST: dumper[61]: %OS-DUMPER-6-FALLBACK_CHOICE : Fall back choice: 0(harddisk:/dumper) in use RP/0/RSP0/CPU0:Feb 26 03:06:29.496 KST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : EDI ESI EBP(fp) EXX RP/0/RSP0/CPU0:Feb 26 03:06:29.496 KST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : R0 153ff03c 142283c4 03df0b10 fc737cd0 RP/0/RSP0/CPU0:Feb 26 03:06:29.496 KST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : EBX EDX ECX EAX RP/0/RSP0/CPU0:Feb 26 03:06:29.496 KST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : R4 14223804 00000000 ffffffff 00000000 RP/0/RSP0/CPU0:Feb 26 03:06:29.496 KST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : EIP(pc) CS EFL ESP RP/0/RSP0/CPU0:Feb 26 03:06:29.496 KST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : R8 0b64d63f 000000f3 00001246 03df0af0 RP/0/RSP0/CPU0:Feb 26 03:06:29.496 KST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : SS RP/0/RSP0/CPU0:Feb 26 03:06:29.496 KST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : R12 000000fb
It do not always happen, it only happen in some specific timing condition; in addition, in order to trigger this problem, a default route should be in bgp table.
none