Preview Tool

Cisco Bug: CSCur19886 - Sessmgr crash sess/mme/mme-app/app/mme_egtp_fw.c:1014

Last Modified

Feb 05, 2017

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases


Description (partial)

Session manager task restarts sometimes with the following assertion failure signature

Assertion failure at sess/mme/mme-app/app/mme_egtp_fw.c:1048
  Function: mme_app_egtpc_abort_low_priority_trans()
  Expression: status==SN_STATUS_SUCCESS
  Proclet: sessmgr (f=87000,i=14)
  Process: card=8 cpu=1 arch=X pid=7552 cpu=~3% argv0=sessmgr
  Crash time: 2014-Nov-13+07:11:26 UTC
  Recent errno: 11 Resource temporarily unavailable
  Stack (68376@0xfffed000):
    [ffffe430/X] __kernel_vsyscall() sp=0xfffed6a8
    [0aeca84f/X] sn_assert() sp=0xfffed6e8
    [07fb2bc0/X] mme_app_egtpc_abort_low_priority_trans() sp=0xfffed748
    [07feea61/X] mme_app_send_egtp_msg() sp=0xfffed7c8
    [08074c5e/X] mme_im_entry_send_s11_message() sp=0xffff9ed8
    [08075350/X] mme_im_entry_state_idle_handle_s1_rls_req() sp=0xffff9f28
    [0809ca02/X] mme_fsm_event_handler() sp=0xffffa3d8
    [080cbca9/X] mme_start_im_entry_procedure() sp=0xffffa418
    [07f9dc1a/X] mme_start_procedure() sp=0xffffa4b8
    [080ce4f6/X] mme_disp_handle_emm_evt() sp=0xffffa5b8
    [080d0753/X] mme_disp_attached_handle_s1ap_ue_event() sp=0xffffa608
    [0809ca02/X] mme_fsm_event_handler() sp=0xffffaab8
    [07f6ce1e/X] UzLiSztStaInd() sp=0xffffafa8
    [0cdf3087/X] SzUiSztStaInd() sp=0xffffafc8
    [0cdea11e/X] szProcessAssocSteChngEvnt() sp=0xffffb1f8
    [0cde51fa/X] SzPiMdtInbMsg() sp=0xffffb348
    [0435ffe8/X] S1apMD_handle_InbMsg() sp=0xffffb4f8
    [0af837a8/X] sn_msg_arriving_handle() sp=0xffffd5e8
    [0af687c9/X] sn_loop_run() sp=0xffffda98
    [0acdb1ed/X] main() sp=0xffffdb08

MME-SGSN-SAEGW-GGSN combo system test running in Ares with 1million 4g & 1million+ 2g & 3g  subscribers . 

After few hours of run, to perfrom aysnc tests saegw-service is removed from the system which results in following crash .

Note: before hitting this crash some other crashes as well observed.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.