summit X-450 switch rebooted suddenly without any log

  • 0
  • 1
  • Question
  • Updated 3 years ago
  • Answered
 i have summit X-450 switch and it rebooted suddenly and when i checked the log  i didn't found any log related for reboot and also i found the below error.

please can somebody help me in this issue  






RPOP1_SW_02.4 # show debug system-dump ===============================================
            Switch system dump information
===============================================
core_dump_info storage: 8/3072 used [EMPTY]
failure: kernel oops
reason: Oops
time: Thu Feb 18 06:26:45 2016
where: Oops:0
$0 : z0=00000000 at=10001f01 v0=8abb3b60 v1=00000000
$4 : a0=00000000 a1=fbf7ff3a a2=f5fffffc a3=fbf7fe3a
$8 : t0=02000000 t1=00000000 t2=00000153 t3=804a4760
$12: t4=7fff6ac8 t5=00000003 t6=00143000 t7=34744f15
$16: s0=c42cf0c0 s1=00000000 s2=00000039 s3=00000001
$20: s4=00000000 s5=fffffbff s6=812012b0 s7=8b994b24
$24: t8=00000000 t9=2aac18fc
$28: gp=8062e000 sp=8062fee8 s8=00000000 ra=c340e42c
Hi : 00000025
Lo : 999999a3
epc   : c37e3290 sal_splhi+0x30/0x8c [linux_bcm_diag_full] Tainted: P          
Status: 10001f03
Cause : 00808008
 8062fee8: 0001869f c41e5470 00000000 0000000d 00000180 0001869f 83baee40 c340e42c
 8062ff08: 00000000 83ac4000 00000000 c38d530c 03bc654d 0e860aca 03bc654d 00000000
 8062ff28: 03bc654d 00000001 83baee40 00000000 00000039 00000001 00000000 fffffbff
 8062ff48: 812012b0 8b994b24 00000000 c163514c 83ac5b62 8010ce60 10001f03 00000000
 8062ff68: c163c358 00000001 00809000 801645f4 804bec60 00000039 804bec94 83baee40
 8062ff88: 804bec60 00000039 804bec94 83baee40 80650000 80164810 00000000 00000000
 8062ffa8: 00000000 00000000 00000000 8062ffd0 2add7000 00400000 8b994b20 812012b0
 8062ffc8: ffffffbf 80104a98 00000000 00000000 00000000 00000000 00000000 00000000
 8062ffe8: 00000000 00000000 00000000 8062e000 89897c70 80106520 1bad2bad 1bad2bad
 80630008: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad
 80630028: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad
 80630048: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad
 80630068: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad
 80630088: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 806300a8: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad
 806300c8: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad
log: ... 00:18:63:01:0d:66
log: <1>CPU 0 Unable to handle kernel paging request at virtual address 00000008, epc == c37e3290, ra == c340e42c

Version #1 SMP Tue Jan 21 18:10:57 EST 2 by release-manager@biltmore.extrem Release 2.6.28.9cougar
Call Trace:
@[<c37e3290>] sal_splhi+0x30/0x8c [linux_bcm_diag_full]
@[<c340e42c>] soc_intr+0x44/0x724 [linux_bcm_diag_full]
@[<c163514c>] gmodule_get+0x14c/0x174 [linux_kernel_bde]

 [<8010ce60>] sibyte_counter_handler+0x84/0xa4
 [<801645f4>] handle_IRQ_event+0x6c/0xd8
 [<80164810>] __do_IRQ+0x1b0/0x260
 [<80104a98>] call_handle_irq+0x20/0x48
 [<80106520>] do_IRQ+0x9c/0x138
Build directory: /data2/release-manager/v15_3_1_4-patch1-30/cougar
--------------------------------
Kernel Panic.
time: Thu Feb 18 06:26:47 2016
Reason: Fatal exception in interrupt
Caller: 0x8010b004 (die+0x124/0x144)
Version #1 SMP Tue Jan 21 18:10:57 EST 2 by release-manager@biltmore.extrem Release 2.6.28.9cougar
Build directory: /data2/release-manager/v15_3_1_4-patch1-30/cougar
Photo of hasan issa

hasan issa

  • 154 Points 100 badge 2x thumb

Posted 3 years ago

  • 0
  • 1
Photo of Hernandez, Joshua

Hernandez, Joshua, Employee

  • 1,564 Points 1k badge 2x thumb
Hello Hasan,

When a switch reboots and shows this type of output it needs to be inspected further.  Please open a service request and attach the following outputs:

show tech
show log messages nvram

We will also need the core dump files to analyze what may have caused the crash. In order to get these see the following article:

How to upload debug information to a TFTP server

Please also upload any syslog messages if there is a syslog configured and note anything that may have been going on prior to the crash with regard to changes, heavy traffic, etc...