Project

General

Profile

Bug #3299

osmo_ortp: scheduler is not started

Added by dexter over 1 year ago. Updated over 1 year ago.

Status:
Stalled
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
05/29/2018
Due date:
% Done:

10%

Spec Reference:

Description

Apparently the scheduler of ortp is not started. Presumably older versions did not require starting the scheduler explicitly, so we just do not call the relevant function:

Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(101600): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(80640): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(101760): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(80800): ERROR!
Tue May 29 15:41:00 2018 <0000> rsl.c:2633 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP
Tue May 29 15:41:00 2018 <0000> rsl.c:2550 (bts=0,trx=0,ts=3,ss=0) chan_num:11 Tx MEAS RES valid(2), flags(03)
Tue May 29 15:41:00 2018 <0000> rsl.c:2568 (bts=0,trx=0,ts=3,ss=0) Send Meas RES: NUM:20, RXLEV_FULL:63, RXLEV_SUB:63, RXQUAL_FULL:0, RXQUAL_SUB:0, MS_PWR:56, UL_TA:0, L3_LEN:18, TimingOff:0
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(101920): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:0 Cannot use the scheduled mode: the scheduler is not started. Call ortp_scheduler_init() at the begginning of the application.Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:0 can't guess current timestamp because session is not scheduled.Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:145 osmo-ortp(16386): timestamp_jump, new TS 0, resyncing
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(80960): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:0 Cannot use the scheduled mode: the scheduler is not started. Call ortp_scheduler_init() at the begginning of the application.Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:0 can't guess current timestamp because session is not scheduled.Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:145 osmo-ortp(16384): timestamp_jump, new TS 0, resyncing
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(102080): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(81120): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(102240): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(81280): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(102400): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(81440): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(102560): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(81600): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(102720): ERROR!
Tue May 29 15:41:00 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(82080): ERROR!

History

#1 Updated by dexter over 1 year ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 40

I now make sure that ortp_scheduler_init() is called at application start:

https://gerrit.osmocom.org/#/c/libosmo-abis/+/9360 ortp: make sure the ortp scheduler is started

Tue May 29 15:59:59 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(78080): ERROR!
Tue May 29 15:59:59 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(78240): ERROR!
Tue May 29 15:59:59 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(78400): ERROR!
Tue May 29 15:59:59 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(78560): ERROR!
Tue May 29 15:59:59 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(78720): ERROR!
Tue May 29 15:59:59 2018 <0015> trau/osmo_ortp.c:0 can't guess current timestamp because session is not scheduled.Tue May 29 15:59:59 2018 <0015> trau/osmo_ortp.c:145 osmo-ortp(16384): timestamp_jump, new TS 0, resyncing
Tue May 29 15:59:59 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(78880): ERROR!
Tue May 29 15:59:59 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(79040): ERROR!
Tue May 29 15:59:59 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(79200): ERROR!
Tue May 29 15:59:59 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(79360): ERROR!
Tue May 29 15:59:59 2018 <0015> trau/osmo_ortp.c:180 osmo_rtp_socket_poll(79520): ERROR!

The log now looks better, but there seem still to be problems.

See also OS#3297

#2 Updated by dexter over 1 year ago

  • % Done changed from 40 to 100

I have checked back if we do enable the scheduled mode or not. Apparently we never enable it. I have added now a call to rtp_session_set_scheduling_mode(rs->sess, TRUE); in osmo_rtp_socket_create(). There is no noticeable difference in the behaviour, but the log text now looks clean:

Wed May 30 14:27:18 2018 <0015> trau/osmo_ortp.c:178 osmo_rtp_socket_poll(79680): ERROR!
Wed May 30 14:27:18 2018 <0015> trau/osmo_ortp.c:178 osmo_rtp_socket_poll(102560): ERROR!
Wed May 30 14:27:18 2018 <0015> trau/osmo_ortp.c:178 osmo_rtp_socket_poll(79840): ERROR!
Wed May 30 14:27:18 2018 <0015> trau/osmo_ortp.c:178 osmo_rtp_socket_poll(102720): ERROR!
Wed May 30 14:27:18 2018 <0015> trau/osmo_ortp.c:178 osmo_rtp_socket_poll(80000): ERROR!
Wed May 30 14:27:18 2018 <0015> trau/osmo_ortp.c:143 osmo-ortp(16384): timestamp_jump, new TS 1212560905, resyncing
Wed May 30 14:27:18 2018 <0015> trau/osmo_ortp.c:178 osmo_rtp_socket_poll(102880): ERROR!
Wed May 30 14:27:18 2018 <0015> trau/osmo_ortp.c:178 osmo_rtp_socket_poll(80160): ERROR!
Wed May 30 14:27:18 2018 <0015> trau/osmo_ortp.c:178 osmo_rtp_socket_poll(103040): ERROR!
Wed May 30 14:27:18 2018 <0015> trau/osmo_ortp.c:178 osmo_rtp_socket_poll(80320): ERROR!
Wed May 30 14:27:18 2018 <0015> trau/osmo_ortp.c:178 osmo_rtp_socket_poll(103200): ERROR!

See also:
https://gerrit.osmocom.org/#/c/libosmo-abis/+/9388 ortp: enable scheduled mode on rtp socket creation

#3 Updated by dexter over 1 year ago

  • % Done changed from 100 to 90

There were reported problems that this patch causes problems on ARM. We will have to look closer into this.

#4 Updated by dexter over 1 year ago

  • Status changed from In Progress to Stalled

#5 Updated by dexter over 1 year ago

  • % Done changed from 90 to 10

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)