<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic RE: summit X-450 switch rebooted suddenly without any log in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x-450-switch-rebooted-suddenly-without-any-log/m-p/24089#M2567</link>
    <description>Hello Hasan,&lt;BR /&gt;
&lt;BR /&gt;
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:&lt;BR /&gt;
&lt;BR /&gt;
show tech&lt;BR /&gt;
show log messages nvram&lt;BR /&gt;
&lt;BR /&gt;
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:&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-upload-debug-information-to-a-TFTP-server" target="_blank" rel="nofollow noreferrer noopener"&gt;How to upload debug information to a TFTP server&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
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...</description>
    <pubDate>Thu, 18 Feb 2016 20:40:00 GMT</pubDate>
    <dc:creator>Hernandez__Josh</dc:creator>
    <dc:date>2016-02-18T20:40:00Z</dc:date>
    <item>
      <title>summit X-450 switch rebooted suddenly without any log</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x-450-switch-rebooted-suddenly-without-any-log/m-p/24088#M2566</link>
      <description>&lt;B&gt; 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.&lt;/B&gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;please can somebody help me in this issue  &lt;/B&gt;&lt;BR /&gt;
&lt;BR /&gt;
RPOP1_SW_02.4 # show debug system-dump ===============================================&lt;BR /&gt;
            Switch system dump information&lt;BR /&gt;
===============================================&lt;BR /&gt;
core_dump_info storage: 8/3072 used [empty]&lt;BR /&gt;
failure: kernel oops&lt;BR /&gt;
reason: Oops&lt;BR /&gt;
time: Thu Feb 18 06:26:45 2016&lt;BR /&gt;
where: Oops:0&lt;BR /&gt;
$0 : z0=00000000 at=10001f01 v0=8abb3b60 v1=00000000&lt;BR /&gt;
$4 : a0=00000000 a1=fbf7ff3a a2=f5fffffc a3=fbf7fe3a&lt;BR /&gt;
$8 : t0=02000000 t1=00000000 t2=00000153 t3=804a4760&lt;BR /&gt;
$12: t4=7fff6ac8 t5=00000003 t6=00143000 t7=34744f15&lt;BR /&gt;
$16: s0=c42cf0c0 s1=00000000 s2=00000039 s3=00000001&lt;BR /&gt;
$20: s4=00000000 s5=fffffbff s6=812012b0 s7=8b994b24&lt;BR /&gt;
$24: t8=00000000 t9=2aac18fc&lt;BR /&gt;
$28: gp=8062e000 sp=8062fee8 s8=00000000 ra=c340e42c&lt;BR /&gt;
Hi : 00000025&lt;BR /&gt;
Lo : 999999a3&lt;BR /&gt;
epc   : c37e3290 sal_splhi+0x30/0x8c [linux_bcm_diag_full] Tainted: P          &lt;BR /&gt;
Status: 10001f03&lt;BR /&gt;
Cause : 00808008&lt;BR /&gt;
 8062fee8: 0001869f c41e5470 00000000 0000000d 00000180 0001869f 83baee40 c340e42c&lt;BR /&gt;
 8062ff08: 00000000 83ac4000 00000000 c38d530c 03bc654d 0e860aca 03bc654d 00000000&lt;BR /&gt;
 8062ff28: 03bc654d 00000001 83baee40 00000000 00000039 00000001 00000000 fffffbff&lt;BR /&gt;
 8062ff48: 812012b0 8b994b24 00000000 c163514c 83ac5b62 8010ce60 10001f03 00000000&lt;BR /&gt;
 8062ff68: c163c358 00000001 00809000 801645f4 804bec60 00000039 804bec94 83baee40&lt;BR /&gt;
 8062ff88: 804bec60 00000039 804bec94 83baee40 80650000 80164810 00000000 00000000&lt;BR /&gt;
 8062ffa8: 00000000 00000000 00000000 8062ffd0 2add7000 00400000 8b994b20 812012b0&lt;BR /&gt;
 8062ffc8: ffffffbf 80104a98 00000000 00000000 00000000 00000000 00000000 00000000&lt;BR /&gt;
 8062ffe8: 00000000 00000000 00000000 8062e000 89897c70 80106520 1bad2bad 1bad2bad&lt;BR /&gt;
 80630008: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad&lt;BR /&gt;
 80630028: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad&lt;BR /&gt;
 80630048: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad&lt;BR /&gt;
 80630068: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad&lt;BR /&gt;
 80630088: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 806300a8: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad&lt;BR /&gt;
 806300c8: 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad 1bad2bad&lt;BR /&gt;
log: ... 00:18:63:01:0d:66&lt;BR /&gt;
log: &amp;lt;1&amp;gt;CPU 0 Unable to handle kernel paging request at virtual address 00000008, epc == c37e3290, ra == c340e42c&lt;BR /&gt;
&lt;BR /&gt;
Version #1 SMP Tue Jan 21 18:10:57 EST 2 by release-manager@biltmore.extrem Release 2.6.28.9cougar&lt;BR /&gt;
Call Trace:&lt;BR /&gt;
@[&lt;C37E3290&gt;] sal_splhi+0x30/0x8c [linux_bcm_diag_full]&lt;BR /&gt;
@[&lt;C340E42C&gt;] soc_intr+0x44/0x724 [linux_bcm_diag_full]&lt;BR /&gt;
@[&lt;C163514C&gt;] gmodule_get+0x14c/0x174 [linux_kernel_bde]&lt;BR /&gt;
&lt;BR /&gt;
 [&amp;lt;8010ce60&amp;gt;] sibyte_counter_handler+0x84/0xa4&lt;BR /&gt;
 [&amp;lt;801645f4&amp;gt;] handle_IRQ_event+0x6c/0xd8&lt;BR /&gt;
 [&amp;lt;80164810&amp;gt;] __do_IRQ+0x1b0/0x260&lt;BR /&gt;
 [&amp;lt;80104a98&amp;gt;] call_handle_irq+0x20/0x48&lt;BR /&gt;
 [&amp;lt;80106520&amp;gt;] do_IRQ+0x9c/0x138&lt;BR /&gt;
Build directory: /data2/release-manager/v15_3_1_4-patch1-30/cougar&lt;BR /&gt;
--------------------------------&lt;BR /&gt;
Kernel Panic.&lt;BR /&gt;
time: Thu Feb 18 06:26:47 2016&lt;BR /&gt;
Reason: Fatal exception in interrupt&lt;BR /&gt;
Caller: 0x8010b004 (die+0x124/0x144)&lt;BR /&gt;
Version #1 SMP Tue Jan 21 18:10:57 EST 2 by release-manager@biltmore.extrem Release 2.6.28.9cougar&lt;BR /&gt;
Build directory: /data2/release-manager/v15_3_1_4-patch1-30/cougar&lt;BR /&gt;
&lt;BR /&gt;&lt;/C163514C&gt;&lt;/C340E42C&gt;&lt;/C37E3290&gt;</description>
      <pubDate>Thu, 18 Feb 2016 18:55:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x-450-switch-rebooted-suddenly-without-any-log/m-p/24088#M2566</guid>
      <dc:creator>hasan_issa</dc:creator>
      <dc:date>2016-02-18T18:55:00Z</dc:date>
    </item>
    <item>
      <title>RE: summit X-450 switch rebooted suddenly without any log</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x-450-switch-rebooted-suddenly-without-any-log/m-p/24089#M2567</link>
      <description>Hello Hasan,&lt;BR /&gt;
&lt;BR /&gt;
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:&lt;BR /&gt;
&lt;BR /&gt;
show tech&lt;BR /&gt;
show log messages nvram&lt;BR /&gt;
&lt;BR /&gt;
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:&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-upload-debug-information-to-a-TFTP-server" target="_blank" rel="nofollow noreferrer noopener"&gt;How to upload debug information to a TFTP server&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
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...</description>
      <pubDate>Thu, 18 Feb 2016 20:40:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x-450-switch-rebooted-suddenly-without-any-log/m-p/24089#M2567</guid>
      <dc:creator>Hernandez__Josh</dc:creator>
      <dc:date>2016-02-18T20:40:00Z</dc:date>
    </item>
  </channel>
</rss>

