Preview Tool

Cisco Bug: CSCuq56851 - Sessmgr crash: Asser failure at sess-mme-mme-app-access-access_s1.c5814

Last Modified

Dec 25, 2016

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases


Description (partial)

Sessmgr crash:
2014-Aug-25+08:55:22.761 [sitmain 4027 critical] [6/0/3428 <sitmain:60> crash_mini.c:824] [software internal system callhome-crash] Process Crash Info: time 2014-Aug-24+22:55:21(hex time 53fa6d59) card 06 cpu 00 pid 04057 procname sessmgr crash_details
Assertion failure at sess/mme/mme-app/access/access_s1.c:5814
Function: send_connection_response()
Expression: x
Proclet: sessmgr (f=87000,i=27)
Process: card=6 cpu=0 arch=X pid=4057 cpu=~11% argv0=sessmgr
Crash time: 2014-Aug-24+22:55:21 UTC
Recent errno: 11 Resource temporarily unavailable
Stack (79992@0xfffea000):
[f7e285a1/X] sp=0xfffea9d8
[0a2005a3/X] sn_assert() sp=0xfffeaa08
[07062b18/X] send_connection_response() sp=0xfffeaa98
[0707f7c5/X] mme_app_send_s1_msg() sp=0xfffeaad8
[0717afb7/X] mme_app_tau_common_process_hss_ulr() sp=0xfffeb568
[071577ad/X] mme_tau_process_ulr() sp=0xfffec018
[07070459/X] mme_fsm_event_handler() sp=0xfffec478
[0715e56a/X] mme_event_handler_tau_procedure() sp=0xfffec4b8
[07071674/X] mme_procedure_handle_event() sp=0xfffec4f8
[070b8c25/X] mme_disp_attached_handle_s6a_msg() sp=0xfffec598
[07070459/X] mme_fsm_event_handler() sp=0xfffec9f8
[07079307/X] mme_app_hss_if_cb_func() sp=0xfffeca88
[0504e664/X] mme_hss_request_cb_pending_request_success() sp=0xffff2f98
[0504d223/X] mme_hss_request_run_int() sp=0xffff2fc8
[0504d13e/X] mme_hss_request_run() sp=0xffff3288
[0504b908/X] mme_hss_diabase_message_cb() sp=0xffff9ec8
[09d2d72a/X] sn_diam_process_inbound_message() sp=0xffffab38
[09ce2458/X] diabase_inbound_msg_from_peer() sp=0xffffabe8
[0a29842b/X] sn_msg_arriving_handle() sp=0xffffd298
[0a275fe5/X] sn_loop_run() sp=0xffffd828
[0a09e3f4/X] main() sp=0xffffd868

Collision with an S1 Handover followed by a TAU Request, followed by a Path Switch Request triggering an X2 Handover before the Modify Bearer Request for the S1 Handover is completed.
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.