Project

General

Profile

Bug #4696

osmo-bts-trx keeps sending dummy bursts after being RF-locked

Added by fixeria about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
osmo-bts-trx
Target version:
-
Start date:
08/06/2020
Due date:
% Done:

100%

Spec Reference:

Description

I noticed that RF-locking does not make osmo-bts-trx stop sending bursts as expected. What I see on the spectrum appears to be a constant stream of dummy bursts, and the TRXD traces confirm that. After looking at the actual implementation, I am not surprised at all: we merely reset the burst scheduler by calling trx_sched_exit() and then trx_sched_init().


Related issues

Related to OsmoBTS - Bug #4695: RF-locking makes osmo-bts-trx lose all per-timeslot rate countersResolved08/06/2020

Related to OsmoBTS - Bug #4694: Radio link timeout would never expire after RF-lock (resource leak)Resolved08/06/2020

History

#1 Updated by fixeria about 1 year ago

  • Related to Bug #4695: RF-locking makes osmo-bts-trx lose all per-timeslot rate counters added

#2 Updated by fixeria about 1 year ago

  • Related to Bug #4694: Radio link timeout would never expire after RF-lock (resource leak) added

#3 Updated by pespin about 1 year ago

  • Status changed from New to Feedback
  • Assignee set to fixeria

This should be fixed after the inclusion of the TRXC RFMUTE feature, since we don't reset the scheduler anymore. Please give a try and mark as resolved if that's the case.

#4 Updated by fixeria about 1 year ago

  • Status changed from Feedback to Resolved
  • % Done changed from 0 to 100

I confirm that the problem has been fixed.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)