Cellular Network Infrastructure » Radio Access Network » OsmoBTS

comparing the failing run.2018-08-21_17-42-15 to the osmo dyn ts run.2018-08-21_17-52-16:

The succeeding PCU BTS log, on startup, says, for each dyn TS:

20180821175236319 DOML <0001> oml.c:76 Sending PCU version report to BSC: 0.5.1.1-54af
20180821175236319 DPCU <0009> pcu_sock.c:608 Activate request received: TRX=0 TX=2
20180821175236319 DL1C <0006> l1sap.c:1401 activating channel chan_nr=0xc2 trx=0
20180821175236319 DL1C <0006> scheduler.c:621 Activating PDTCH on trx=0 ts=2
20180821175236319 DL1C <0006> scheduler.c:621 Activating PTCCH on trx=0 ts=2
20180821175236319 DL1C <0006> l1sap.c:573 activate confirm chan_nr=0xc2 trx=0
20180821175236319 DRSL <0000> rsl.c:812 (bts=0,trx=0,ts=2,ss=0) not sending CHAN ACT ACK

The failing one lacks the "Activating PxxCH":

20180821174235089 DOML <0001> oml.c:76 Sending PCU version report to BSC: 0.5.1.1-54af
20180821174235096 DPCU <0009> pcu_sock.c:608 Activate request received: TRX=0 TX=2
20180821174235096 DL1C <0006> l1sap.c:1401 activating channel chan_nr=0x0a trx=0
20180821174235097 DL1C <0006> l1sap.c:573 activate confirm chan_nr=0x0a trx=0
20180821174235097 DRSL <0000> rsl.c:812 (bts=0,trx=0,ts=2,ss=0) not sending CHAN ACT ACK

looking now why TCH/F_PDCH fails to activate PDTCH and PTCCH SAPIs...

the sysmoBTS version that works has the same chan_nr and still succeeds to activate PDTCH:

20180629135302135 DOML <0001> oml.c:76 Sending PCU version report to BSC: 0.5.1.1-54af
20180629135302137 DPCU <0009> pcu_sock.c:608 Activate request received: TRX=0 TX=2
20180629135302137 DL1C <0006> l1sap.c:1401 activating channel chan_nr=0x0a trx=0
20180629135302137 DL1C <0006> oml.c:1083 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.req (hL2=0x000200bb, PDTCH TxDL)
20180629135302140 DL1C <0006> oml.c:816 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.conf (PDTCH TxDL)
20180629135302141 DL1C <0006> oml.c:1083 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.req (hL2=0x000200bb, PDTCH RxUL)
20180629135302145 DL1C <0006> oml.c:816 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.conf (PDTCH RxUL)
20180629135302145 DL1C <0006> oml.c:1083 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.req (hL2=0x000200bb, PTCCH TxDL)
20180629135302150 DL1C <0006> oml.c:816 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.conf (PTCCH TxDL)
20180629135302150 DL1C <0006> oml.c:1083 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.req (hL2=0x000200bb, PRACH RxUL)
20180629135302155 DL1C <0006> oml.c:816 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.conf (PRACH RxUL)
20180629135302155 DL1C <0006> l1sap.c:573 activate confirm chan_nr=0x0a trx=0
20180629135302155 DRSL <0000> rsl.c:812 (bts=0,trx=0,ts=2,ss=0) not sending CHAN ACT ACK

pespin , can you try an osmo-gsm-tester run of at least osmo-bts-trx for the suites that do

• osmocom style dyn ts
• ipa style dyn ts
• non-dyn ts

with this patch plz: osmo-bts branch neels/trx_dyn_ipa

I hope that fixes it but I have no SDR hardware to test with...
thx!

Run the 3 tests as requested. The 3 of them pass with branch "neels/trx_dyn_ipa".
https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_manual-run/141

Hm wait, I actually run the voice ones. I'll try now with the gprs ones just in case something is wrong there.

The 3 gprs tests pass now too, so your commit fixes the isse: https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_manual-run/144

https://gerrit.osmocom.org/#/c/osmo-bts/+/10598