SegV exceptions usually occur due to bugs, or when a process tries to access an invalid memory addrfess, or write to an invalid memory address,.
Give a " show stacks" command and paste the output either here, for further troubleshooting, or you can use Output Interpreter t display potential issues and fixes. Output Interpreter will tell you if there are any matching bugs, related to this issue.
If its not yet getting solved, the best thing to do would be to copy outputs of "show tech" and perhaps a crashinfo file (generated the next time a crash occurs) and contact Cisco TAC.
Error : No matching bug was found, probably a new bug
The stack trace decoded symbols are:
This crash, could be result of a new bug.So you would probably want to open a case with cisco, or your reseller, (you can contact cisco TAC if you have smartnet, or if you have purchased maintenance from reseller, then you need to contact their TAC, Make sure you have the contract number with them, before you call).
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...