Project

General

Profile

Bug #4604

Lots of "Unusual event"

Added by laforge 5 months ago. Updated 4 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
06/08/2020
Due date:
% Done:

0%

Spec Reference:

Related issues

Related to OsmoSGSN - Bug #4602: SGSN crash with "Assert failed mm->gb.llme == NULL gprs_sgsn.c:358"Feedback06/08/2020

Related to OsmoSGSN - Bug #4601: gmm_fsm{Registered.SUSPENDED}: Event E_GMM_COMMON_PROC_INIT_REQ not permittedFeedback06/08/2020

Related to OsmoSGSN - Bug #4600: gmm_fsm{CommonProcedureInitiated}: Event E_GMM_COMMON_PROC_INIT_REQ not permittedFeedback06/08/2020

Related to OsmoSGSN - Bug #4599: counter group sgsn:pdpctx already exists for index X, instead using YNew06/08/2020

History

#1 Updated by laforge 5 months ago

  • Status changed from New to Feedback
  • Assignee set to lynxis

Together with various other SGSN issues, I'm seeing quite a number of 'unusual events' here:

<0002> gprs_gmm_attach.c:216 MM(901700000040779/f2fb5402) Unusual event: if MS got no data connection, check that it has APN configured.
<0002> gprs_gmm_attach.c:216 MM(901700000040777/df099190) Unusual event: if MS got no data connection, check that it has APN configured.
<0002> gprs_gmm_attach.c:216 MM(901700000040778/e3464a00) Unusual event: if MS got no data connection, check that it has APN configured.

#2 Updated by laforge 5 months ago

  • Related to Bug #4602: SGSN crash with "Assert failed mm->gb.llme == NULL gprs_sgsn.c:358" added

#3 Updated by laforge 5 months ago

  • Related to Bug #4601: gmm_fsm{Registered.SUSPENDED}: Event E_GMM_COMMON_PROC_INIT_REQ not permitted added

#4 Updated by laforge 5 months ago

  • Related to Bug #4600: gmm_fsm{CommonProcedureInitiated}: Event E_GMM_COMMON_PROC_INIT_REQ not permitted added

#5 Updated by laforge 5 months ago

  • Related to Bug #4599: counter group sgsn:pdpctx already exists for index X, instead using Y added

#6 Updated by laforge 5 months ago

#7 Updated by lynxis 5 months ago

  • Assignee changed from lynxis to laforge

A pcap would help here. My random guess it's related to RAUs.

However I think the same as for OS#4600 and OS#4604: It would be the best way is to remove the gmm_authorized() and implementing RAU as fsm and authentication as fsm. We're otherwise only working towards the symptoms and not problem itself.

#8 Updated by laforge 4 months ago

  • Status changed from Feedback to New
  • Assignee changed from laforge to lynxis

lynxis wrote:

A pcap would help here. My random guess it's related to RAUs.

However I think the same as for OS#4600 and OS#4604: It would be the best way is to remove the gmm_authorized() and implementing RAU as fsm and authentication as fsm. We're otherwise only working towards the symptoms and not problem itself.

Acknowleged. Feel free to work on those FSMs as part of your work for sysmocom.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)