On 17/08/2016 23:35, Holger Freyther wrote:
>> OpenBSC# show lchan su
>> BTS 0, TRX 0, Timeslot 1, Lchan 0, Type NONE - L1 MS Power: 33 dBm
> type none? What OpenBSC version is that? So just the none already looks
> broken.
Sure, If you look at the non summary version of lchan, you see the likes of
BTS 1, TRX 0, Timeslot 7, Lchan 0: Type NONE
Connection: 0, State: BROKEN UNUSABLE Error reason: activation timeout
BS Power: 37 dBm, MS Power: 33 dBm
No Subscriber
Bound IP: 0.0.0.0 Port 0 RTP_TYPE2=0 CONN_ID=0
Measurement Report:
Flags: DLinval
RXL-FULL-ul: -110 dBm, RXL-SUB-ul: -110 dBm RXQ-FULL-ul: 0,
RXQ-SUB-ul: 0
osmo-nitb tells me it is
OpenBSC version 0.14.0-dirty
You mentioned off list about the sbts2050 software, yes I'm afraid it's
201208-testing.
>> Can I ask, What triggers the eventual calling of
>> rsl_rx_rf_chan_rel_ack(),
> the actual arrival of the REL_ACK message.
So it won't ever be called, once it's "lost"
What I don't understand is how it can get lost. Or arrive out of order
of something, that's not possible with tcp is it?
I have tried momentarily interrupting the connection BSC<->BTS with
iptables but I cannot as yet provoke the event that causes this.. ah
just now it happens again (meanwhile I am watching a straight ping to
the bts (for what it's worth) and I see nothing unusual there.
Maybe this actually has not got to do with the wifi link after all, and
that is just coincidence?
<0004> abis_rsl.c:717 (bts=0,trx=0,ts=1,ss=0) RF CHANNEL RELEASE ACK
<0004> abis_rsl.c:735 (bts=0,trx=0,ts=1,ss=0) CHAN REL ACK for broken
channel. Releasing it.
<0004> abis_rsl.c:211 (bts=1,trx=0,ts=1,ss=1) Timeout during activation.
Marked as broken.
<0004> abis_rsl.c:211 (bts=1,trx=0,ts=1,ss=0) Timeout during activation.
Marked as broken.
<0004> abis_rsl.c:211 (bts=1,trx=0,ts=1,ss=2) Timeout during activation.
Marked as broken.
<0004> abis_rsl.c:211 (bts=1,trx=0,ts=1,ss=3) Timeout during activation.
Marked as broken.
<0004> abis_rsl.c:211 (bts=1,trx=0,ts=1,ss=4) Timeout during activation.
Marked as broken.
<0004> abis_rsl.c:1464 (bts=1,trx=0,ts=1,ss=5) Activating ARFCN(251)
SS(5) lctype SDCCH r=LOCATION_UPDATE ra=0x0b ta=3
<0004> abis_rsl.c:1464 (bts=1,trx=0,ts=1,ss=6) Activating ARFCN(251)
SS(6) lctype SDCCH r=LOCATION_UPDATE ra=0x0f ta=3
<0004> abis_rsl.c:1464 (bts=1,trx=0,ts=1,ss=7) Activating ARFCN(251)
SS(7) lctype SDCCH r=LOCATION_UPDATE ra=0x0a ta=3
<0004> abis_rsl.c:1464 (bts=0,trx=0,ts=1,ss=0) Activating ARFCN(249)
SS(0) lctype SDCCH r=LOCATION_UPDATE ra=0x0c ta=2
<0004> abis_rsl.c:1464 (bts=0,trx=0,ts=1,ss=1) Activating ARFCN(249)
SS(1) lctype SDCCH r=OTHER ra=0x1c ta=1
<0004> abis_rsl.c:1464 (bts=0,trx=0,ts=1,ss=2) Activating ARFCN(249)
SS(2) lctype SDCCH r=LOCATION_UPDATE ra=0x0d ta=2
<0004> abis_rsl.c:1464 (bts=0,trx=0,ts=1,ss=3) Activating ARFCN(249)
SS(3) lctype SDCCH r=OTHER ra=0x10 ta=1
<0004> abis_rsl.c:1464 (bts=0,trx=0,ts=1,ss=4) Activating ARFCN(249)
SS(4) lctype SDCCH r=LOCATION_UPDATE ra=0x07 ta=2
<0004> abis_rsl.c:1464 (bts=0,trx=0,ts=1,ss=5) Activating ARFCN(249)
SS(5) lctype SDCCH r=OTHER ra=0x17 ta=1
<0004> abis_rsl.c:211 (bts=1,trx=0,ts=1,ss=5) Timeout during activation.
Marked as broken.
<0004> abis_rsl.c:211 (bts=1,trx=0,ts=1,ss=6) Timeout during activation.
Marked as broken.
<0004> abis_rsl.c:211 (bts=1,trx=0,ts=1,ss=7) Timeout during activation.
Marked as broken.
<0004> abis_rsl.c:211 (bts=0,trx=0,ts=1,ss=0) Timeout during activation.
Marked as broken.
<0004> abis_rsl.c:211 (bts=0,trx=0,ts=1,ss=1) Timeout during activation.
Marked as broken.
<0004> abis_rsl.c:211 (bts=0,trx=0,ts=1,ss=2) Timeout during activation.
Marked as broken.
<0004> abis_rsl.c:211 (bts=0,trx=0,ts=1,ss=3) Timeout during activation.
Marked as broken.
<0004> abis_rsl.c:211 (bts=0,trx=0,ts=1,ss=4) Timeout during activation.
Marked as broken.
<0004> abis_rsl.c:211 (bts=0,trx=0,ts=1,ss=5) Timeout during activation.
Marked as broken.
