Bug #6214
Updated by pespin 7 months ago
Since 27th September 2023 22:48h, osmo-gsm-tester_virtual's massive registration test is failing due to some MS failing to register: https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_virtual/ We expect >=99% of MS to register, but we get 97%. we need to find out if it's due to some change in CNI or in osmocom-bb. Some hints after looking at log files below. osmo-bsc: <pre> Timeout of T3101 </pre> This seems to be cancelling the LU. T3101 is "RR Immediate Assignment (default: 3 s)". osmo-bts: <pre> "DRSL ERROR Early IA check: unknown chan_nr=0x04 (rsl.c:382) </pre> osmocom-bb: <pre> "follow-on proceed not supported. (gsm48_mm.c:2714) </pre> <pre> Event EVENT_REG_SUCCESS unhandled in state A2 on PLMN. (gsm322.c:3783) (gsm322.c:3783 </pre> My bet is there's a regression in any of your osmocom-bb patches in 975351e2508683c7c7b18958b8248cd157400fb0..d95c8f4fa693c4e34bbbdde171fe1ba096e23825
