https://osmocom.org/https://osmocom.org/favicon.ico?16647414092020-06-08T19:01:58ZOpen Source Mobile CommunicationsOsmoSGSN - Bug #4604: Lots of "Unusual event"https://osmocom.org/issues/4604?journal_id=186192020-06-08T19:01:58Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>lynxis</i></li></ul><p>Together with various other SGSN issues, I'm seeing quite a number of 'unusual events' here:</p>
<pre>
<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.
</pre> OsmoSGSN - Bug #4604: Lots of "Unusual event"https://osmocom.org/issues/4604?journal_id=186212020-06-08T19:02:07Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-4 priority-2 priority-default" href="/issues/4602">Bug #4602</a>: SGSN crash with "Assert failed mm->gb.llme == NULL gprs_sgsn.c:358"</i> added</li></ul> OsmoSGSN - Bug #4604: Lots of "Unusual event"https://osmocom.org/issues/4604?journal_id=186232020-06-08T19:02:12Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-4 priority-2 priority-default" href="/issues/4601">Bug #4601</a>: gmm_fsm{Registered.SUSPENDED}: Event E_GMM_COMMON_PROC_INIT_REQ not permitted</i> added</li></ul> OsmoSGSN - Bug #4604: Lots of "Unusual event"https://osmocom.org/issues/4604?journal_id=186252020-06-08T19:02:18Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-4 priority-2 priority-default" href="/issues/4600">Bug #4600</a>: gmm_fsm{CommonProcedureInitiated}: Event E_GMM_COMMON_PROC_INIT_REQ not permitted</i> added</li></ul> OsmoSGSN - Bug #4604: Lots of "Unusual event"https://osmocom.org/issues/4604?journal_id=186272020-06-08T19:02:24Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-2 priority-default" href="/issues/4599">Bug #4599</a>: counter group sgsn:pdpctx already exists for index X, instead using Y</i> added</li></ul> OsmoSGSN - Bug #4604: Lots of "Unusual event"https://osmocom.org/issues/4604?journal_id=186282020-06-08T19:02:30Zlaforge
<ul></ul> OsmoSGSN - Bug #4604: Lots of "Unusual event"https://osmocom.org/issues/4604?journal_id=186912020-06-11T19:03:59Zlynxis
<ul><li><strong>Assignee</strong> changed from <i>lynxis</i> to <i>laforge</i></li></ul><p>A pcap would help here. My random guess it's related to RAUs.</p>
<p>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.</p> OsmoSGSN - Bug #4604: Lots of "Unusual event"https://osmocom.org/issues/4604?journal_id=187172020-06-13T18:19:22Zlaforge
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>New</i></li><li><strong>Assignee</strong> changed from <i>laforge</i> to <i>lynxis</i></li></ul><p>lynxis wrote:</p>
<blockquote>
<p>A pcap would help here. My random guess it's related to RAUs.</p>
<p>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.</p>
</blockquote>
<p>Acknowleged. Feel free to work on those FSMs as part of your work for sysmocom.</p>