https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-can-i-check-the-reason-of-sudden-reboot/m-p/43609#M10548 A switch rebooted suddenly.<BR /> I checked the memory-buffer logs and nvram logs, but there is nothing to explain the reboot.<BR /> <BR /> Model : Summit X670-48x<BR /> XOS Ver. : 15.2.2.7-patch1-2<BR /> <BR /> Check the system-dump below<BR /> <BR /> Asan-LAX012.1 # show debug system-dump =============================================== Switch system dump information =============================================== core_dump_info storage: 8/3072 used [empty] Stacktrace: reason: NMI0 id: 0 $0 : z0=00000000 at=1000dc00 v0=00000001 v1=00000000 $4 : a0=00000000 a1=00000002 a2=00000000 a3=00000002 $8 : t0=80000380 t1=00080000 t2=87869e80 t3=00000000 $12: t4=00000000 t5=c25a435c t6=00000008 t7=000001d3 $16: s0=87869d40 s1=81a0a2e0 s2=81a0a2e0 s3=00000001 $20: s4=00000001 s5=0000000e s6=0044beb0 s7=00450000 $24: t8=00000000 t9=8020f588 $28: gp=87868000 sp=87869d08 s8=2b80bdf0 ra=8026a290 Hi : 00138fa7 Lo : c2ed8051 epc : 8026a0b0 <NOT available=""> Tainted: P Status: 504800c0 Cause : 10800000 87869d08: 00000002 807b77a0 00000000 80885e3c 00000001 80224618 00000000 00000001 87869d28: 00000001 8026a290 0046d7f8 87869da4 00000000 ffffffff 81a0a2e0 81a0a2e0 87869d48: 80224618 2b80ba70 00010009 8020d230 00000000 80213640 80224618 00000001 87869d68: 87869e80 8026a47c 00000112 00000112 87869d98 87869d98 00000002 8024bf54 87869d88: 87869d84 87869d8c 87869d8c 00004001 0000000e 85c24c58 88741220 8024cebc 87869da8: 883b0d60 000007f8 00000000 878cadb0 0000000e 85c24c58 88741220 8024da90 87869dc8: 2b80ba70 87869e20 80224618 2b80ba70 87869e80 2b80ba78 2b80ba70 802450e8 87869de8: 00000002 8024f8a8 88741250 81a061e0 81a061e8 88383a64 00000000 00000000 87869e08: 87869e80 802171a8 87869e98 88741200 8836f1c4 00000009 8836e5c0 87869f30 87869e28: 2b80ba60 802183dc 2b80bd10 00000000 0044beb0 2ab06020 878cb15c 2aae6fe8 87869e48: 87869f30 0000000e 87869e80 87869e98 878cb15c 00450000 0044beb0 802177f8 87869e68: 87869f18 87869e80 87869f30 87869ec8 10624dd3 0044beb0 10000000 004176fc 87869e88: 00002000 00000000 00000000 00000000 0000000e 00000080 00000000 00000000 87869ea8: 00000000 000001d3 00000002 8cf31aac 00000080 0046d7f8 00000000 fffffff5 87869ec8: 2b80bd10 00450000 0044beb0 00450000 2b80bdf0 80269398 2b80ba60 2aae6fe8 87869ee8: 00000000 87869f08 2ab06020 00000000 ffffffff 00450000 2b80bdf0 80217938 Call Trace: @[&lt;8026a0b0&gt;] <NOT available=""> @[&lt;8026a290&gt;] <NOT available=""> @[&lt;8026a47c&gt;] <NOT available=""> @[&lt;802450e8&gt;] <NOT available=""> @[&lt;802171a8&gt;] <NOT available=""> @[&lt;802183dc&gt;] <NOT available=""> @[&lt;802177f8&gt;] <NOT available=""> @[&lt;802137d8&gt;] <NOT available=""><BR /> Please let me know about the cause.</NOT></NOT></NOT></NOT></NOT></NOT></NOT></NOT></NOT> Thu, 02 Apr 2015 13:18:00 GMT CellarRat 2015-04-02T13:18:00Z https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-can-i-check-the-reason-of-sudden-reboot/m-p/43609#M10548 A switch rebooted suddenly.<BR /> I checked the memory-buffer logs and nvram logs, but there is nothing to explain the reboot.<BR /> <BR /> Model : Summit X670-48x<BR /> XOS Ver. : 15.2.2.7-patch1-2<BR /> <BR /> Check the system-dump below<BR /> <BR /> Asan-LAX012.1 # show debug system-dump =============================================== Switch system dump information =============================================== core_dump_info storage: 8/3072 used [empty] Stacktrace: reason: NMI0 id: 0 $0 : z0=00000000 at=1000dc00 v0=00000001 v1=00000000 $4 : a0=00000000 a1=00000002 a2=00000000 a3=00000002 $8 : t0=80000380 t1=00080000 t2=87869e80 t3=00000000 $12: t4=00000000 t5=c25a435c t6=00000008 t7=000001d3 $16: s0=87869d40 s1=81a0a2e0 s2=81a0a2e0 s3=00000001 $20: s4=00000001 s5=0000000e s6=0044beb0 s7=00450000 $24: t8=00000000 t9=8020f588 $28: gp=87868000 sp=87869d08 s8=2b80bdf0 ra=8026a290 Hi : 00138fa7 Lo : c2ed8051 epc : 8026a0b0 <NOT available=""> Tainted: P Status: 504800c0 Cause : 10800000 87869d08: 00000002 807b77a0 00000000 80885e3c 00000001 80224618 00000000 00000001 87869d28: 00000001 8026a290 0046d7f8 87869da4 00000000 ffffffff 81a0a2e0 81a0a2e0 87869d48: 80224618 2b80ba70 00010009 8020d230 00000000 80213640 80224618 00000001 87869d68: 87869e80 8026a47c 00000112 00000112 87869d98 87869d98 00000002 8024bf54 87869d88: 87869d84 87869d8c 87869d8c 00004001 0000000e 85c24c58 88741220 8024cebc 87869da8: 883b0d60 000007f8 00000000 878cadb0 0000000e 85c24c58 88741220 8024da90 87869dc8: 2b80ba70 87869e20 80224618 2b80ba70 87869e80 2b80ba78 2b80ba70 802450e8 87869de8: 00000002 8024f8a8 88741250 81a061e0 81a061e8 88383a64 00000000 00000000 87869e08: 87869e80 802171a8 87869e98 88741200 8836f1c4 00000009 8836e5c0 87869f30 87869e28: 2b80ba60 802183dc 2b80bd10 00000000 0044beb0 2ab06020 878cb15c 2aae6fe8 87869e48: 87869f30 0000000e 87869e80 87869e98 878cb15c 00450000 0044beb0 802177f8 87869e68: 87869f18 87869e80 87869f30 87869ec8 10624dd3 0044beb0 10000000 004176fc 87869e88: 00002000 00000000 00000000 00000000 0000000e 00000080 00000000 00000000 87869ea8: 00000000 000001d3 00000002 8cf31aac 00000080 0046d7f8 00000000 fffffff5 87869ec8: 2b80bd10 00450000 0044beb0 00450000 2b80bdf0 80269398 2b80ba60 2aae6fe8 87869ee8: 00000000 87869f08 2ab06020 00000000 ffffffff 00450000 2b80bdf0 80217938 Call Trace: @[&lt;8026a0b0&gt;] <NOT available=""> @[&lt;8026a290&gt;] <NOT available=""> @[&lt;8026a47c&gt;] <NOT available=""> @[&lt;802450e8&gt;] <NOT available=""> @[&lt;802171a8&gt;] <NOT available=""> @[&lt;802183dc&gt;] <NOT available=""> @[&lt;802177f8&gt;] <NOT available=""> @[&lt;802137d8&gt;] <NOT available=""><BR /> Please let me know about the cause.</NOT></NOT></NOT></NOT></NOT></NOT></NOT></NOT></NOT> Thu, 02 Apr 2015 13:18:00 GMT https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-can-i-check-the-reason-of-sudden-reboot/m-p/43609#M10548 CellarRat 2015-04-02T13:18:00Z