<?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 SecureStack Reset with Fault(0x00001x00) and BackTraces in current.log in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/securestack-reset-with-fault-0x00001x00-and-backtraces-in/m-p/47861#M484</link>
    <description>Article ID: 12664 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3, C2, B3, B2, A2 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Discussion&lt;/B&gt;&lt;BR /&gt;
The "Fault(0x00001&lt;I&gt;x&lt;/I&gt;00)" diagnostics are the occasional result of a reset event, as may be seen in the output of a 'show support' or in a current.log file (&lt;A href="http://bit.ly/1pOU3VK" target="_blank" rel="nofollow noreferrer noopener"&gt;5487&lt;/A&gt;&lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; &lt;BR /&gt;
&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;A Fault(0x00001000) is caused by an attempt to execute invalid machine instructions. 
&lt;/LI&gt;&lt;LI&gt;A Fault(0x00001100) is caused when the effective address for a data load operation cannot be translated to a value within legal DRAM boundaries. This is due to stack/register or data corruption, as a result of a bad pointer or something over-running an array or buffer. 
&lt;/LI&gt;&lt;LI&gt;A Fault(0x00001200) is caused by a write exception.&lt;/LI&gt;&lt;/UL&gt;
With firmware released prior to 2007 (C3 f/w 1.00.37 and lower, C2 f/w 4.00.55 and lower, B3 f/w 1.00.31 and lower, B2 f/w 3.01.27 and lower, A2 f/w 1.03.24 and lower) that is the only level of diagnostic detail available, making it difficult to glean anything more from such a reset event. &lt;BR /&gt;
&lt;BR /&gt;
However, with firmware released since then (C3 f/w 1.00.40 and higher, C2 f/w 5.00.28 and higher, B3 f/w 1.00.34 and higher, B2 f/w 4.00.22 and higher, A2 f/w 1.04.12 and higher), any given reset event, whether containing these Faults or not, is accompanied by more diagnostically useful BackTrace data, which appears as in this example:&amp;lt;57&amp;gt; NOV 29 10:11:11 2007 STK1 BOOT[268430848]: bootos.c(640) 295 %%&lt;BR /&gt;
 Start of Code - Build:05.00.28 Date:Tue Dec 26 09:07:37 2006 &lt;BR /&gt;
  BackTrace-&lt;ADDRESS&gt;: &lt;SUBROUTINE_NAME&gt; (&lt;ADDRESS&gt;) + &lt;DISPLACEMENT&gt;&lt;BR /&gt;
   . . .&lt;BR /&gt;
  BackTrace-&lt;ADDRESS&gt;: &lt;SUBROUTINE_NAME&gt; (&lt;ADDRESS&gt;) + &lt;DISPLACEMENT&gt;&lt;BR /&gt;
  BackTrace-symbol not found for 0x0&lt;BR /&gt;
&amp;lt;110&amp;gt; NOV 29 10:11:31 2007 STK1 BOOT[185147968]: edb_bxs.c(736) 300 %%&lt;BR /&gt;
 Last switch reset caused by Fault(0x00001100) SRR0(0x006a78e4) SRR1(0x8000b030) MSR(0x00001030) DMISS(0xccccccd8) IMISS(0x00000000)&lt;BR /&gt;
BackTrace data is implemented in the current.log only, though it is expected to soon (early 2010) also appear in the '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;show support&lt;/PRE&gt;&lt;/DIV&gt;' output for the manager unit only. For this reason it is frequently helpful to review the current.log in order to make a diagnosis on a reset event.&lt;BR /&gt;
&lt;BR /&gt;
After retrieving both the '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;show support&lt;/PRE&gt;&lt;/DIV&gt;' and current.log data (&lt;A href="http://bit.ly/1pOU3VK" target="_blank" rel="nofollow noreferrer noopener"&gt;5487&lt;/A&gt;), please &lt;A href="http://www.enterasys.com/support/contact-support.aspx" target="_blank" rel="nofollow noreferrer noopener"&gt;contact the GTAC&lt;/A&gt; for assistance in analyzing and resolving the problem.&lt;/DISPLACEMENT&gt;&lt;/ADDRESS&gt;&lt;/SUBROUTINE_NAME&gt;&lt;/ADDRESS&gt;&lt;/DISPLACEMENT&gt;&lt;/ADDRESS&gt;&lt;/SUBROUTINE_NAME&gt;&lt;/ADDRESS&gt;</description>
    <pubDate>Fri, 08 Nov 2013 02:49:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-11-08T02:49:00Z</dc:date>
    <item>
      <title>SecureStack Reset with Fault(0x00001x00) and BackTraces in current.log</title>
      <link>https://community.extremenetworks.com/t5/faqs/securestack-reset-with-fault-0x00001x00-and-backtraces-in/m-p/47861#M484</link>
      <description>Article ID: 12664 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3, C2, B3, B2, A2 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Discussion&lt;/B&gt;&lt;BR /&gt;
The "Fault(0x00001&lt;I&gt;x&lt;/I&gt;00)" diagnostics are the occasional result of a reset event, as may be seen in the output of a 'show support' or in a current.log file (&lt;A href="http://bit.ly/1pOU3VK" target="_blank" rel="nofollow noreferrer noopener"&gt;5487&lt;/A&gt;&lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; &lt;BR /&gt;
&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;A Fault(0x00001000) is caused by an attempt to execute invalid machine instructions. 
&lt;/LI&gt;&lt;LI&gt;A Fault(0x00001100) is caused when the effective address for a data load operation cannot be translated to a value within legal DRAM boundaries. This is due to stack/register or data corruption, as a result of a bad pointer or something over-running an array or buffer. 
&lt;/LI&gt;&lt;LI&gt;A Fault(0x00001200) is caused by a write exception.&lt;/LI&gt;&lt;/UL&gt;
With firmware released prior to 2007 (C3 f/w 1.00.37 and lower, C2 f/w 4.00.55 and lower, B3 f/w 1.00.31 and lower, B2 f/w 3.01.27 and lower, A2 f/w 1.03.24 and lower) that is the only level of diagnostic detail available, making it difficult to glean anything more from such a reset event. &lt;BR /&gt;
&lt;BR /&gt;
However, with firmware released since then (C3 f/w 1.00.40 and higher, C2 f/w 5.00.28 and higher, B3 f/w 1.00.34 and higher, B2 f/w 4.00.22 and higher, A2 f/w 1.04.12 and higher), any given reset event, whether containing these Faults or not, is accompanied by more diagnostically useful BackTrace data, which appears as in this example:&amp;lt;57&amp;gt; NOV 29 10:11:11 2007 STK1 BOOT[268430848]: bootos.c(640) 295 %%&lt;BR /&gt;
 Start of Code - Build:05.00.28 Date:Tue Dec 26 09:07:37 2006 &lt;BR /&gt;
  BackTrace-&lt;ADDRESS&gt;: &lt;SUBROUTINE_NAME&gt; (&lt;ADDRESS&gt;) + &lt;DISPLACEMENT&gt;&lt;BR /&gt;
   . . .&lt;BR /&gt;
  BackTrace-&lt;ADDRESS&gt;: &lt;SUBROUTINE_NAME&gt; (&lt;ADDRESS&gt;) + &lt;DISPLACEMENT&gt;&lt;BR /&gt;
  BackTrace-symbol not found for 0x0&lt;BR /&gt;
&amp;lt;110&amp;gt; NOV 29 10:11:31 2007 STK1 BOOT[185147968]: edb_bxs.c(736) 300 %%&lt;BR /&gt;
 Last switch reset caused by Fault(0x00001100) SRR0(0x006a78e4) SRR1(0x8000b030) MSR(0x00001030) DMISS(0xccccccd8) IMISS(0x00000000)&lt;BR /&gt;
BackTrace data is implemented in the current.log only, though it is expected to soon (early 2010) also appear in the '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;show support&lt;/PRE&gt;&lt;/DIV&gt;' output for the manager unit only. For this reason it is frequently helpful to review the current.log in order to make a diagnosis on a reset event.&lt;BR /&gt;
&lt;BR /&gt;
After retrieving both the '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;show support&lt;/PRE&gt;&lt;/DIV&gt;' and current.log data (&lt;A href="http://bit.ly/1pOU3VK" target="_blank" rel="nofollow noreferrer noopener"&gt;5487&lt;/A&gt;), please &lt;A href="http://www.enterasys.com/support/contact-support.aspx" target="_blank" rel="nofollow noreferrer noopener"&gt;contact the GTAC&lt;/A&gt; for assistance in analyzing and resolving the problem.&lt;/DISPLACEMENT&gt;&lt;/ADDRESS&gt;&lt;/SUBROUTINE_NAME&gt;&lt;/ADDRESS&gt;&lt;/DISPLACEMENT&gt;&lt;/ADDRESS&gt;&lt;/SUBROUTINE_NAME&gt;&lt;/ADDRESS&gt;</description>
      <pubDate>Fri, 08 Nov 2013 02:49:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/securestack-reset-with-fault-0x00001x00-and-backtraces-in/m-p/47861#M484</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-11-08T02:49:00Z</dc:date>
    </item>
  </channel>
</rss>

