Actions
Bug #5238
closedTCH/F_PDCH is not properly deactivated in scheduler
Start date:
09/25/2021
Due date:
% Done:
100%
Spec Reference:
Description
Configure at least one ip.access style dynamic timeslot (TCH/F_PDCH) and start the network. Then kill osmo-pcu.
DPCU NOTICE pcu_sock.c:994 PCU socket has LOST connection DOML NOTICE oml.c:90 OC=GPRS-CELL INST=(00,ff,ff): Sending PCU version report to BSC: PCU socket has LOST connection DPCU NOTICE sysinfo.c:202 Disabling GPRS Indicator in SI (No PCU connected) DTRX INFO trx_if.c:255 phy0.0: Enqueuing TRX control command 'CMD NOHANDOVER 5 0' DRSL NOTICE rsl.c:1286 (bts=0,trx=0,ts=5,ss=0) (bts=0,trx=0,ts=5,ss=0) not sending REL ACK DTRX INFO trx_if.c:255 phy0.0: Enqueuing TRX control command 'CMD NOHANDOVER 6 0' DL1C NOTICE scheduler.c:1097 (bts=0,trx=0,ts=6,ss=0) Deactivating PDTCH DL1C NOTICE scheduler.c:1097 (bts=0,trx=0,ts=6,ss=0) Deactivating PTCCH DRSL NOTICE rsl.c:1286 (bts=0,trx=0,ts=6,ss=0) (bts=0,trx=0,ts=6,ss=0) not sending REL ACK DTRX INFO trx_if.c:255 phy0.0: Enqueuing TRX control command 'CMD NOHANDOVER 7 0' DL1C NOTICE scheduler.c:1097 (bts=0,trx=0,ts=7,ss=0) Deactivating PDTCH DL1C NOTICE scheduler.c:1097 (bts=0,trx=0,ts=7,ss=0) Deactivating PTCCH DRSL NOTICE rsl.c:1286 (bts=0,trx=0,ts=7,ss=0) (bts=0,trx=0,ts=7,ss=0) not sending REL ACK DTRX INFO trx_if.c:672 phy0.0: Response message: 'RSP NOHANDOVER 0 5 0' DTRX INFO trx_if.c:672 phy0.0: Response message: 'RSP NOHANDOVER 0 6 0' DTRX INFO trx_if.c:672 phy0.0: Response message: 'RSP NOHANDOVER 0 7 0' DL1P NOTICE l1sap.c:126 (bts=0,trx=0,ts=5,ss=0) assuming active lchan, but state is NONE DL1P ERROR l1sap.c:732 1583426/1194/00/29/14 No lchan for DATA MEAS IND (chan_nr=PDCH on TS5) DPCU NOTICE pcu_sock.c:973 PCU socket not connected, dropping message DL1P NOTICE l1sap.c:126 (bts=0,trx=0,ts=5,ss=0) assuming active lchan, but state is NONE DPCU NOTICE pcu_sock.c:973 PCU socket not connected, dropping message DL1P NOTICE l1sap.c:126 (bts=0,trx=0,ts=5,ss=0) assuming active lchan, but state is NONE DL1P ERROR l1sap.c:732 1583430/1194/04/33/18 No lchan for DATA MEAS IND (chan_nr=PDCH on TS5) DPCU NOTICE pcu_sock.c:973 PCU socket not connected, dropping message DL1P NOTICE l1sap.c:126 (bts=0,trx=0,ts=5,ss=0) assuming active lchan, but state is NONE DPCU NOTICE pcu_sock.c:973 PCU socket not connected, dropping message DL1P NOTICE l1sap.c:126 (bts=0,trx=0,ts=5,ss=0) assuming active lchan, but state is NONE DL1P ERROR l1sap.c:732 1583434/1194/08/37/22 No lchan for DATA MEAS IND (chan_nr=PDCH on TS5) DPCU NOTICE pcu_sock.c:973 PCU socket not connected, dropping message DL1P NOTICE l1sap.c:126 (bts=0,trx=0,ts=5,ss=0) assuming active lchan, but state is NONE DPCU NOTICE pcu_sock.c:973 PCU socket not connected, dropping message DL1P NOTICE l1sap.c:126 (bts=0,trx=0,ts=5,ss=0) assuming active lchan, but state is NONE DL1P ERROR l1sap.c:732 1583439/1194/13/42/27 No lchan for DATA MEAS IND (chan_nr=PDCH on TS5) DPCU NOTICE pcu_sock.c:973 PCU socket not connected, dropping message DL1P NOTICE l1sap.c:126 (bts=0,trx=0,ts=5,ss=0) assuming active lchan, but state is NONE DPCU NOTICE pcu_sock.c:973 PCU socket not connected, dropping message
As can be seen from the logs, TS5/PDCH is not being deactivated in the scheduler:
DTRX INFO trx_if.c:255 phy0.0: Enqueuing TRX control command 'CMD NOHANDOVER 5 0' DRSL NOTICE rsl.c:1286 (bts=0,trx=0,ts=5,ss=0) (bts=0,trx=0,ts=5,ss=0) not sending REL ACK DTRX INFO trx_if.c:255 phy0.0: Enqueuing TRX control command 'CMD NOHANDOVER 6 0' DL1C NOTICE scheduler.c:1097 (bts=0,trx=0,ts=6,ss=0) Deactivating PDTCH DL1C NOTICE scheduler.c:1097 (bts=0,trx=0,ts=6,ss=0) Deactivating PTCCH DRSL NOTICE rsl.c:1286 (bts=0,trx=0,ts=6,ss=0) (bts=0,trx=0,ts=6,ss=0) not sending REL ACK
So AFAIU, the lower layers keep trying to decode Uplink blocks on TS5 and therefore produce L1SAP DATA.ind, which in turn cause the errors/warnings.
Actions
