cellular-infrastructure
/
osmo-bts
mirror of https://gerrit.osmocom.org/osmo-bts
9
0
Fork 0
Code Issues Releases Wiki Activity

scheduler.c: Print message when burst substitution happens 

Whenever we receive discontinuous frame numbers from the TRX socket,
osmo-bts-trx is substituting zero-filled bursts for those frame numbers
which we missed.  Don't just do this silently, but actually log about
it, as it is an error.

Note: This [currently] happens when using a virtual air interface with trxcon
as opposed to a real SDR receiver with osmo-trx.

Change-Id: If79eab37c80647c9ab64f399fa4676d97af3e9ad
This commit is contained in:
Harald Welte 2018-02-23 23:25:56 +01:00
parent 815ff00d23
commit fc169ba7bb
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/common/scheduler.c
View File

@ -1725,8 +1725,11 @@ int trx_sched_ul_burst(struct l1sched_trx *l1t, uint8_t tn, uint32_t current_fn,
func(l1t, tn, fn, chan, bid, bits, nbits, rssi, toa);
} else if (chan != TRXC_RACH && !l1cs->ho_rach_detect) {
sbit_t spare[GSM_BURST_LEN];
memset(spare, 0, GSM_BURST_LEN);
/* We missed a couple of frame numbers (system overload?) and are now
* substituting some zero-filled bursts for those bursts we missed */
LOGPFN(DL1P, LOGL_ERROR, fn, "Substituting all-zero burst (current_fn=%u, "
"elapsed=%u\n", current_fn, elapsed);
func(l1t, tn, fn, chan, bid, spare, GSM_BURST_LEN, -128, 0);
}