diff options
author | Harald Welte <laforge@gnumonks.org> | 2018-02-23 23:25:56 +0100 |
---|---|---|
committer | Harald Welte <laforge@gnumonks.org> | 2018-02-23 23:29:34 +0100 |
commit | fc169ba7bba831f00de3490c49d0e2583c29db8a (patch) | |
tree | a41c86b131ed9dc8c14d8e397a310418b1d55059 /src | |
parent | 815ff00d239b5b20bb077e210b533c7ff32cb102 (diff) |
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
Diffstat (limited to 'src')
-rw-r--r-- | src/common/scheduler.c | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/src/common/scheduler.c b/src/common/scheduler.c index 4e48160b..e6e7eafd 100644 --- a/src/common/scheduler.c +++ b/src/common/scheduler.c @@ -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); } |