Project

General

Profile

Bug #4873

BSC trying to activate TS while still in avail=dependency

Added by fixeria about 2 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
A-bis OML
Target version:
-
Start date:
11/28/2020
Due date:
% Done:

100%

Spec Reference:

Description

I am getting these warnings when starting osmo-bts-trx:

DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx0-ts0)[0x6120000036a0]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx0-ts1)[0x612000003820]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx0-ts2)[0x6120000039a0]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx0-ts3)[0x612000003b20]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx0-ts4)[0x612000003ca0]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx0-ts5)[0x612000003e20]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx0-ts6)[0x612000003fa0]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx0-ts7)[0x612000004120]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx1-ts0)[0x6120000048a0]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx1-ts1)[0x612000004a20]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx1-ts2)[0x612000004ba0]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx1-ts3)[0x612000004d20]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx1-ts4)[0x612000004ea0]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx1-ts5)[0x612000005020]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx1-ts6)[0x6120000051a0]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
DOML NOTICE nm_channel_fsm.c:84 NM_CHAN_OP(bts0-trx1-ts7)[0x612000005320]{DISABLED_DEPENDENCY}:
    BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.

Given that I am using up to date osmo-bsc and osmo-bts-trx, why is this happening? Another race condition?

bsc_is_wrong.pcapng.gz bsc_is_wrong.pcapng.gz 66.9 KB Who is wrong? fixeria, 11/28/2020 07:13 PM
osmo-bts-trx.cfg osmo-bts-trx.cfg 1.09 KB fixeria, 11/29/2020 02:48 PM
osmo-bsc.cfg osmo-bsc.cfg 3.09 KB fixeria, 11/29/2020 02:49 PM

History

#1 Updated by pespin about 2 months ago

In which scenario are you receiving this? Cold startup of all the processes? or after doing something specific like restarting osmo-bts-trx after everything was set up?

Please provide pcap so that all the OML/RSL negotiation can be seen, together with gsmtap log of bsc or bts.

#2 Updated by fixeria about 2 months ago

In which scenario are you receiving this?

Basically, every time I start osmo-bts-trx.

Cold startup of all the processes?

I have not tried to restart all processed, but restarting the BSC does not change anything - I still see the warnings.

or after doing something specific like restarting osmo-bts-trx after everything was set up?

Starting and restarting gives the same warnings.

Please provide pcap so that all the OML/RSL negotiation can be seen, together with gsmtap log of bsc or bts.

Please find it attached.

#3 Updated by pespin about 2 months ago

First analysis after looking only at OML so far:

I see the trace has 2 TRX, that may be something important to take into consideration when looking at the issue. Do you see the same issues when running with 1 TRX?

  • First thing I don't understand and I never saw: Why is BSC sending "BTS Get Attributes" even before the BTS sends the Activated Report? (frame #133).
  • Similarly, Get Attributes for both Transceivers are sent too early, when they are in "Power off" state. BSC should wait for them to be in "Offline" before attempting it. It can be seen that Software Activate report is sent afterwards. Still, we'd need to check how that behaves when running against nanobts.
  • GPRS-related MO still not using new FSMs. See #4870.

#4 Updated by fixeria about 2 months ago

Hi Pau,

I see the trace has 2 TRX, that may be something important to take into consideration when looking at the issue. Do you see the same issues when running with 1 TRX?

just tested - yes, I also see the warnings with a single-trx configuration. Please see the config files attached.

#5 Updated by pespin about 1 month ago

  • Status changed from New to Feedback
  • Assignee changed from pespin to fixeria
  • % Done changed from 0 to 30

The multiple issues I spotted (not sure if they really provoke the issues you are seeing) should be fixed once https://gerrit.osmocom.org/c/osmo-bsc/+/21451 and previous patches are merged.

Please once they are merged give it another try, if possible with only 1 TRX and provide feedback again.

#6 Updated by fixeria about 1 month ago

  • Assignee changed from fixeria to pespin

Hi Pau,

Please once they are merged give it another try, if possible with only 1 TRX and provide feedback again.

unfortunately, this has not been resolved. I still see those warnings, even with only 1 TRX.

You can reproduce them by running ttcn3-bts-test, see for example:

https://jenkins.osmocom.org/jenkins/view/TTCN3-centos/job/TTCN3-centos-bts-test/206/artifact/logs/bts/osmo-bts.log

20201208110048649 DRSL <0000> rsl.c:278 Tx RSL RF RESource INDication
20201208110048649 DOML <0001> nm_channel_fsm.c:85 NM_CHAN_OP(bts0-trx0-ts2)[0x1408420]{DISABLED_DEPENDENCY}:
BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
20201208110048651 DOML <0001> nm_channel_fsm.c:85 NM_CHAN_OP(bts0-trx0-ts3)[0x1408a60]{DISABLED_DEPENDENCY}:
BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.
20201208110048651 DOML <0001> nm_channel_fsm.c:85 NM_CHAN_OP(bts0-trx0-ts4)[0x14090a0]{DISABLED_DEPENDENCY}:
BSC trying to activate TS while still in avail=dependency. Allowing it to stay backward-compatible with older osmo-bts versions, but BSC is wrong.

#7 Updated by pespin about 1 month ago

Thanks. It seems the Dependency -> Offline path is triggered before those messages but apparently the FSM doesn't change the state, there's most probably a bug in related code. I'll look into it soon.

#8 Updated by pespin about 1 month ago

  • % Done changed from 30 to 90

Should be fixed by:
https://gerrit.osmocom.org/c/osmo-bts/+/21625 nm_channel_fsm: Fix several FSM internal transitions not being made

#9 Updated by fixeria about 1 month ago

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

I am happy to confirm that the fix works.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)