Project

General

Profile

Bug #3000

OsmoBSC issues "RSL Connect" command too early -> race conditions

Added by laforge almost 2 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
A-bis OML
Target version:
-
Start date:
02/25/2018
Due date:
% Done:

0%

Spec Reference:

Description

The "IPA RSL CONNECT" is issued before OML has even configured the individual timeslots with their channel mode. This introduces race conditions where RSL might be attempting to use the timeslots before they are configured in the BTS, which creates all kinds of errors like

DRSL <0000> rsl.c:164 (bts=0,trx=0,ts=6,pchan=NONE) RSL rx IPACC: mismatching chan_nr=0x6e

Related issues

Related to OsmoBSC - Feature #2470: Proper OML MO (managed object) using osmo_fsmNew08/29/2017

Related to OsmoBTS - Bug #4179: Race condition: OsmoBTS sends empty INFO_ind to PCU socket, if not all SI arrived from BSC via RSLNew08/29/2019

History

#1 Updated by laforge almost 2 years ago

  • Subject changed from OsmoBTS issues "RSL Connect" command too early -> race conditions to OsmoBSC issues "RSL Connect" command too early -> race conditions

#2 Updated by laforge almost 2 years ago

Added https://gerrit.osmocom.org/6899 work-around in the TTCN-3 test suite for OsmoBTS to avoid running into that race condition.

#3 Updated by laforge almost 2 years ago

  • Related to Feature #2470: Proper OML MO (managed object) using osmo_fsm added

#4 Updated by osmith 3 months ago

  • Related to Bug #4179: Race condition: OsmoBTS sends empty INFO_ind to PCU socket, if not all SI arrived from BSC via RSL added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)