Cisco Bug: CSCuw48799 - Fatal Signal 11: Segmentation fault:sessmgr_handle_get_ggsn_table()
Nov 28, 2017
- Cisco ASR 5000 Series
Known Affected Releases
14.0(55) 19.2.d0 19.3.v0 20.0.0 20.0.v0
Symptom: A sessmgr crash is seen with the following stack trace: Fatal Signal 11: Segmentation fault PC: [03d60568/X] sessmgr_handle_get_ggsn_table() Faulty address: 0x24 Signal from: kernel Signal detail: address not mapped to object Process: card=8 cpu=0 arch=X pid=4910 cpu=~26% argv0=sessmgr Crash time: 2015-Sep-25+05:29:23 UTC Recent errno: 11 Resource temporarily unavailable Stack (15304@0xffffa000): [03d60568/X] sessmgr_handle_get_ggsn_table() sp=0xffffaf38 [0a29842b/X] sn_msg_arriving_handle() sp=0xffffd5e8 [0a275fe5/X] sn_loop_run() sp=0xffffdb78 [0a09e3f4/X] main() sp=0xffffdbb8 Conditions: This is observed whenever an SGSN specific CLI "show sgtp-service ggsn-table smgr-instance <>" is executed on a GGSN-only node (has license for SGSN too), which is not SGTP service configured.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases