Actions
Bug #4872
closedBSC reports "abis_rsl.c:143 (bts=2,trx=0,ts=0,pchan_from_config=CCCH+SDCCH4,state=NOT_INITIALIZED) Abis RSL rx CCHAN: mismatching chan_nr=0x90"
Start date:
11/28/2020
Due date:
% Done:
100%
Spec Reference:
Description
When I'm testing my BSC with a centos BTS + fake trx I'm getting lots of the
messages
<0003> abis_rsl.c:143 (bts=2,trx=0,ts=0,pchan_from_config=CCCH+SDCCH4,state=NOT_INITIALIZED) Abis RSL rx CCHAN: mismatching chan_nr=0x90
It's not 100% reproducible, but it sounds like the BSC' fsm for the timeslot is in a wrong state.
My BSC is on 1.6.0-407-g55d7ee57cf57
My BTS is on 1.2.0.332.2edf
Files
Updated by pespin over 3 years ago
I have seen this locally today, it happens while BTS is not yet ON (because for instance osmo-trx is not available or still not in POWERON state, TS not configured, etc.)
Updated by pespin over 2 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 90
Should be fixed by:
https://gerrit.osmocom.org/c/osmo-bts/+/25691 load_indication.c: Avoid sending if CCCH is still not operational
Updated by pespin over 2 years ago
- Status changed from Feedback to Resolved
- % Done changed from 90 to 100
Merged, closing.
Actions