We have problem like described you on two HiPer chassis (four ARC). And long way with open case on 3Com. Last events on that case is "possible memory corruption" and if problem still present on our newest code (V5.1.94/Non-Encr) we start to build the fix. :(( === cut I was able to have our developers look at the crash dumps and for them,it seems like this is a memory corruption. They are suggesting to have you try our Emergency code of 5.1.94-1 which addressed many of these kinds of issues. However, you must understand that this code may not fix your particular problem. If, for some reason, this code does not fix the memory issue, I will escalate this case. ==== After loading this code on one from our ARCs (4 days ago) we do not have reboots. We wait and look. At the monday I load this code on the other three of our ARCs and look again. (14 days without reboot after loading new code usual situation for this case) Good luck ! ====================== Andrey Zimin | AVZ7-RIPE MTU-Intel ISP Moscow, Russia ====================== ----- Original Message ----- From: "ROC Services" <roc@itol.com> To: <usr-tc@lists.xmission.com> Sent: 25 ц▒ц▌ц≈ц│ц▓ц▒ 2001 ц┤. 18:57 Subject: (usr-tc) Crashing HiperARC - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.