Thank you Stanislav, here's what I got:
=========================================================================================
Member 1
Master -- Saved Crash Information (most recent first):
======================================================
ID: a70f63d7
Active/Commander system went down: 11/24/21 11:52:47 WC.16.09.0003 516
NMI event SW:PC=0x00000001 LR:0x034d1200 SP:0xf7 Task='mDsnoopCtrl' Task ID=0x2ab47298
ID: 65511af6
Standby system went down: 05/23/20 15:33:31 WC.16.09.0003 516
Reboot of Member ID 1, User reboot
ID: e96a2479
Active/Commander system went down: 05/23/20 15:07:17 WC.16.09.0003 516
Reboot of Member ID 1, User reboot
ID: 2fa30217
Active/Commander system went down: 05/23/20 15:06:50 WC.16.09.0003 516
Operator cold reboot from TELNET session.
Member 2
Master -- Saved Crash Information (most recent first):
======================================================
ID: bf71b16b
Standby system went down: 11/24/21 11:52:46 WC.16.09.0003 516
NMI event SW:PC=0x2d0001e5 LR:0xfffffee5 SP:0x9ff08cea Task='mDsnoopCtrl' Task ID=0x2ab4f5bc
ID: 1274e100
Member system went down: 05/23/20 14:33:32 WC.16.09.0003 516
Reboot of Member ID 2, User reboot
ID: f54fc839
Standby system went down: 05/23/20 15:07:12 WC.16.09.0003 516
Reboot of Member ID 2, User reboot
ID: 1b222aa2
Standby system went down: 04/24/20 21:10:40 WC.16.09.0003 516
Reboot of Member ID 2, User reboot
Member 3
Master -- Saved Crash Information (most recent first):
======================================================
ID: 416f5476
Member system went down: 11/24/21 11:52:50 WC.16.09.0003 516
Reboot of Member ID 3, Lost commander and standby
ID: 9ff582b1
Member system went down: 05/23/20 14:33:32 WC.16.09.0003 516
Reboot of Member ID 3, User reboot
ID: 08962632
Member system went down: 05/23/20 14:07:11 WC.16.09.0003 516
Reboot of Member ID 3, User reboot
ID: 4a0845ec
Member system went down: 04/24/20 21:10:40 WC.16.09.0003 516
Reboot of Member ID 3, User reboot
Member 4
Master -- Saved Crash Information (most recent first):
======================================================
ID: 19e479ad
Member system went down: 11/24/21 11:52:54 WC.16.09.0003 516
Reboot of Member ID 4, Lost commander and standby
ID: f925da10
Active/Commander system went down: 05/23/20 15:33:37 WC.16.09.0003 516
Reboot of Member ID 4, User reboot
ID: cd1dd7fa
Active/Commander system went down: 05/23/20 15:33:10 WC.16.09.0003 516
Operator cold reboot from TELNET session.
ID: a352b8c4
Member system went down: 05/23/20 14:07:11 WC.16.09.0003 516
Reboot of Member ID 4, User reboot
Ports 1/1-48,A -- Saved Crash Information (most recent first):
=======================================================
ID: 313f20f1
Ports 1/1-48,A subsystem went down: 11/24/21 15:22:47 WC.16.09.0003 608
Software exception at bsp_interrupts.c:90 -- in 'fault_handler', task ID = 0x10d0d200
-> Master Induced Crash. IGNORE!
Ports 2/1-48,A -- Saved Crash Information (most recent first):
=======================================================
ID: b9469f2f
Ports 2/1-48,A subsystem went down: 11/24/21 15:22:47 WC.16.09.0003 608
Software exception at bsp_interrupts.c:90 -- in 'fault_handler', task ID = 0x10d0d200
-> Master Induced Crash. IGNORE!
----------------------------------------------------------------------------
MM:Management Module, IM: Interface Module
----------------------------------------------------------------------------
TimeStamp Type Core Dump File Name Role Build Version
----------------- ------ ---------------------------- ---------- ----------
11-24-21 15:22:51 IM 1 I_03003821_SG91JQP52Y.cor Standby WC.16.09.0003
11-24-21 11:52:47 MM 1 M_03003821_SG91JQP52Y.cor Standby WC.16.09.0003
11-24-21 15:22:50 IM 2 I_03003821_SG93JQP6WP.cor Member WC.16.09.0003
11-24-21 11:52:46 MM 2 M_03003821_SG93JQP6WP.cor Member WC.16.09.0003
11-24-21 11:52:46 IM 3 I_03003821_SG87JQNW79.cor Member WC.16.09.0003
------------------------------
Manny Taveroff
------------------------------
Original Message:
Sent: Nov 26, 2021 10:08 AM
From: Stanislav Naydenov
Subject: 2930m crash: Software exception at bsp_interrupts.c:90
Hi Manny,
Can you please check the boot history (show boot-history) - there should be more information regarding the SW exception and it will give you more insight regarding the reboot of the stack.
After confirming the SW exception you can take a look at the release notes for the newer versions for your device - if there are any similar already known bugs that are already fixed.
------------------------------
Stanislav Naydenov
Original Message:
Sent: Nov 25, 2021 09:58 AM
From: Manny Taveroff
Subject: 2930m crash: Software exception at bsp_interrupts.c:90
Anyone know what triggers this? I can't find any information on this software exception. I believe it could be the cause of a random stack reboot yesterday and I'm trying to figure out why.
switch stack: 2930m
Firmware: WC.16.09.0003
Thanks!
------------------------------
Manny Taveroff
------------------------------