FATAL ERROR on SG300

cisco.com · ‎10-09-2012

We have several SG300 Series Switches (8, 20, 28 and 52-Port Versions) running. All Switches do reboot from time to time: Some after a week or so, others several times a day and then run again happily. In the log I see:

%SYSLOG-F-OSFATAL:

FATAL ERROR: tExcTask: ABORT DATA exception

***** FATAL ERROR *****

SW Version: 1.2.7.76

Version Date: 19-Jul-2012 Version

Time: 17:54:43

Instruction 0x2C

Exception vector 0x10

Program state register 0x80000092

***** END OF FATAL ERROR *****

This happens with FW Version 1.2.7.76 as well as under Version 1.1.1.8.

I do not know if this is related to FUGU, but it usually happens, when I try to open a connection with FUGU to some other host in the network. Where can I get help on this? I cannot find a place to report bugs to cisco. Thanx for your help.

Regards, Adrian.

cisco.com · ‎10-09-2012

This seems related:

https://supportforums.cisco.com/message/3726269#3726269

Tom Watts · ‎10-09-2012

Hi Adrian, can you post the entire flash memory log error?

-Tom
Please rate helpful posts

-Tom Please mark answered for helpful posts http://blogs.cisco.com/smallbusiness/

cisco.com · ‎10-10-2012

2147469364 2012-Oct-10 01:20:50 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.2.7.76 Version Date: 19-Jul-2012 Version Time: 17:54:43 Instruction 0x2C Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

2147470191 2012-Oct-01 19:39:52 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.1.1.8 Version Date: 30-Aug-2011 Version Time: 10:46:34 Instruction 0x2C Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

2147471024 2012-Sep-18 20:12:29 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.1.1.8 Version Date: 30-Aug-2011 Version Time: 10:46:34 Instruction 0xFF1B6D44 Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

2147471857 2012-Sep-18 20:04:58 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.1.1.8 Version Date: 30-Aug-2011 Version Time: 10:46:34 Instruction 0xFF1B6D44 Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

2147472690 2012-Sep-18 19:39:40 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.1.1.8 Version Date: 30-Aug-2011 Version Time: 10:46:34 Instruction 0xFF1B6D44 Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

2147473523 2012-Sep-18 18:10:22 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.1.1.8 Version Date: 30-Aug-2011 Version Time: 10:46:34 Instruction 0xFF1B6D44 Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

2147474356 2012-Sep-18 17:56:19 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.1.1.8 Version Date: 30-Aug-2011 Version Time: 10:46:34 Instruction 0xFF1B6D44 Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

2147475189 2012-Sep-18 17:52:42 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.1.1.8 Version Date: 30-Aug-2011 Version Time: 10:46:34 Instruction 0xFF1B6D44 Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

2147476022 2012-Sep-08 12:55:29 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.1.1.8 Version Date: 30-Aug-2011 Version Time: 10:46:34 Instruction 0xFF1B6D44 Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

2147476855 2012-Sep-07 02:41:45 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.1.1.8 Version Date: 30-Aug-2011 Version Time: 10:46:34 Instruction 0xFF1B6D44 Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

2147477688 2012-Sep-07 01:58:15 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.1.1.8 Version Date: 30-Aug-2011 Version Time: 10:46:34 Instruction 0xFF1B6D44 Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

2147478521 2012-Sep-07 00:59:42 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.1.1.8 Version Date: 30-Aug-2011 Version Time: 10:46:34 Instruction 0xFF1B6D44 Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

2147479354 2012-Sep-06 23:09:19 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.1.1.8 Version Date: 30-Aug-2011 Version Time: 10:46:34 Instruction 0xFF1B6D44 Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

2147480187 2012-Sep-06 23:01:15 Emergency %SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.1.1.8 Version Date: 30-Aug-2011 Version Time: 10:46:34 Instruction 0xFF1B6D44 Exception vector 0x10 Program state register 0x80000092 ***** END OF FATAL ERROR *****

I pasted all flash log entries back to Sep, 6th.

Thank you for looking at this.

Regards, Adrian.

Tom Watts · ‎10-10-2012

Adrian, thank you. These error messages are separate than the other topic. So I think it is a different problem although the register error is the same number which likely means it is the same resolution.

If you really want to persue this, we need a whole lot of data. I will notify the L2 team and the development team of your post and see if there is something we can do for you.

-Tom
Please rate helpful posts

-Tom Please mark answered for helpful posts http://blogs.cisco.com/smallbusiness/

cisco.com · ‎10-10-2012

Hi Tom

Since I'm doing nothing really very special with these Switches I think, I'm not the only one concerned on this planet. I can't do the testing for cisco since I do not have a spare Switch, but I can provide all data needed including the config. Just tell me by email, what information you need to open a case. Do you use GPG?

Thanks for your help.

Regards, Adrian.

Tom Watts · ‎10-10-2012

Hi Adrian, as promised, I have reached out to the development team. Can you please provide the following;

1) config file (for each affected switch)

2) NW diagram (network topology)

3) Full RAM and flash file

4) Does issue happen only on 1 switch or on a few. If on a few switches – do they reboot at the same time

5) Information on devices connected to switch and protocol running on network.

6) From log file on case I can see that Sep 6-8 there are quite a few reboots. Then no reboots until Sep 18^th. On sep 18^th there are again many reboots (around 6) – and then no reboots until Oct 1^st. Can customer check if this correlates with any activity in his NW for these dates (was there a specific device or protocol connected on the “rebooting” days and not on others?

Can customer elaborate on the FUGU usage or send packet capture?

Also, I do have a special debug command for you (I will not post this publically). Please send me an email all of this information. Once I receive all this information, I will provide a special debug command we can run before the switch error to help isolate the incidents.

Thank you.

-Tom
Please rate helpful posts

-Tom Please mark answered for helpful posts http://blogs.cisco.com/smallbusiness/

cisco.com · ‎10-10-2012

I sent you the infos by mail.

Tom Watts · ‎10-10-2012

Adrian, I have forwarded your information to the development and L2 team. Additionally, I've emailed you a detailed debug instruction. Please perform this and collect the data.

-Tom
Please rate helpful posts

-Tom Please mark answered for helpful posts http://blogs.cisco.com/smallbusiness/

bbp5401ag · ‎03-26-2013

I am seeing a similar issue - is there a fix for this yet?

SG300SW04#show logging file

Logging is enabled.

Console Logging: Level info. Console Messages: 2 Dropped.

Buffer Logging: Level info. Buffer Messages: 44 Logged, 42 Displayed, 1000 Max.

File Logging: Level error. File Messages: 192 Logged, 46 Dropped.

4 messages were not logged

Application filtering control

Application Event Status

-------------------- -------------------- ---------

AAA Login Enabled

File system Copy Enabled

File system Delete-Rename Enabled

Management ACL Deny Enabled

Aggregation: Enabled

Aggregation aging time: 300 Sec

26-Mar-2013 15:02:14 :%SYSLOG-F-OSFATAL:

FATAL ERROR: tExcTask: ABORT DATA exception

***** FATAL ERROR *****

SW Version : 1.2.9.44

Version Date: 30-Sep-2012

Version Time: 01:33:07

Instruction 0xFF90FFE0

Exception vector 0x10

Program state register 0x80000092

***** END OF FATAL ERROR *****

26-Mar-2013 14:38:08 :%SYSLOG-F-OSFATAL:

FATAL ERROR: tExcTask: ABORT DATA exception

***** FATAL ERROR *****

SW Version : 1.2.9.44

Version Date: 30-Sep-2012

Version Time: 01:33:07

Instruction 0xFF90FFE0

Exception vector 0x10

Program state register 0x80000092

***** END OF FATAL ERROR *****

26-Mar-2013 14:34:08 :%SYSLOG-F-OSFATAL:

FATAL ERROR: tExcTask: ABORT DATA exception

***** FATAL ERROR *****

SW Version : 1.2.9.44

Version Date: 30-Sep-2012

Version Time: 01:33:07

Instruction 0xFF90FFE0

Exception vector 0x10

Program state register 0x80000092

***** END OF FATAL ERROR *****

26-Mar-2013 14:09:41 :%SYSLOG-F-OSFATAL:

FATAL ERROR: tExcTask: ABORT DATA exception

cisco.com · ‎03-26-2013

Hi bbp

Cisco Support wrote me:

On 11/30/12 1:57 AM, Marcelo Demello wrote:

> Hello Adrian,

>

> Unfortunately, I have now way to track the release date with the case

> closed. I think we should have a new code coming in the next 2 months, the

> 1.3.xxxx, that will include the fix.

>

> Thank you,

>

> Marcelo

So just check the Firmware Update Page of sg300. Or to work around: Switch off bonjour on your switches.

Regards, Adrian.

FATAL ERROR on SG300

Cisco Business Product Family

Cisco Switching Product Family