Preview Tool

Cisco Bug: CSCut64551 - Session Manager Restart: mme_app_is_proc_s1ho_to_4g()

Last Modified

Dec 26, 2016

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases


Description (partial)

The following session manager crash was observed on MME node:

Friday March 27 18:40:25 EST 2015
********************* CRASH #10 ***********************
Build: 14.0(59025)

Fatal Signal 11: Segmentation fault
  PC: [070dd148/X] mme_app_is_proc_s1ho_to_4g()
  Faulty address: 0x10
  Signal from: kernel
  Signal detail: address not mapped to object
  Process: card=14 cpu=0 arch=X pid=4160 cpu=~7% argv0=sessmgr
  Crash time: 2015-Mar-25+23:10:16 UTC
  Recent errno: 11 Resource temporarily unavailable
  Stack (30840@0xffff6000):
    [070dd148/X] mme_app_is_proc_s1ho_to_4g() sp=0xffff66e8
    [070a7205/X] mme_emm_common_proc_inited_handle_tau_req() sp=0xffff6738
    [07071819/X] mme_fsm_event_handler() sp=0xffff6b98
    [070b0e62/X] mme_disp_handle_emm_evt() sp=0xffff6c88
    [070b768f/X] mme_disp_attached_handle_s1nas_msg() sp=0xffff6d18
    [07071819/X] mme_fsm_event_handler() sp=0xffff7178
    [0706a812/X] nas_access_recv_init_ue() sp=0xffff81a8
    [0706c47f/X] nas_access_recv_msg() sp=0xffff81f8
    [070557ce/X] UzLiSztConInd() sp=0xffff8db8
    [0be1b8ef/X] SzUiSztConInd() sp=0xffff8dd8
    [0be221fe/X] szUiSndConInd() sp=0xffff8e08
    [0be1c976/X] szSmRcvIdleStMsg() sp=0xffff8e58
    [0be1d54a/X] szSmExcMt() sp=0xffff8e88
    [0be0a9d3/X] szLiCOMsgHandler() sp=0xffff8f08
    [0be0a551/X] szLiRcvFromLower() sp=0xffff90f8
    [0be0cd81/X] SzLiSctDatInd() sp=0xffff9258
    [062ad698/X] sn_ccpu_s1ap_handle_data_ind() sp=0xffff92e8
    [03ebeec6/X] sessmgr_mmemgr_data_ind() sp=0xffff9348
    [03ebed1c/X] sessmgr_handle_mmemgr_req_bulk_data_ind() sp=0xffffabe8
    [0a299a0b/X] sn_msg_arriving_handle() sp=0xffffd298
    [0a2775c5/X] sn_loop_run() sp=0xffffd828
    [0a09f9d4/X] main() sp=0xffffd868

If the subscriber attaches to 4G before the procedure is complete, another attach is received and before the ESM info response is received, the SGS paging gets triggered.
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.