osmo-bts-trx: "CHAN RQD: no resources for SDCCH" on master

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Max msuraev at sysmocom.de
Tue Jun 14 17:23:26 UTC 2016


I see. Will give it a shot tomorrow. If you have any patches/branches I
can use as a starting point - let me know.

On 06/14/2016 07:19 PM, Tom Tsou wrote:
> Hi Max,
>
> On Tue, Jun 14, 2016 at 1:07 AM, Max <msuraev at sysmocom.de> wrote:
>> Which branch is used in practice? I've looked at gerrit/fairwaves/master
>> and the difference seems pretty small so I'm puzzled as to which commit
>> fixes it.
> The issue is command timing and improperly handled order of events.
> Some time back I checked the diff's between fairwaves/master and
> master, but wasn't able to find where the difference in sequencing was
> taking place. I'm puzzled about this as well, but, as Harald says, the
> real solution is not resolving the differences between fairwaves and
> master branches, but properly handling the OML initialization in
> master.
>
> The workaround for osmo-bts-trx master is as follows:
>
> 1. Remove CLK IND from the osmo-trx control loop
> 2. Start osmo-trx
> 3. Start osmo-bts-trx
> 4. Externally Issue the POWERON command to osmo-trx
>
> This delays CLK IND packets from prematurely reaching osmo-bts and
> allows the OML sequencing to take place. This is obviously a hack I
> suspect a real fix will involve some modification to the osmo-trx
> socket interface.
>
>   -TT

-- 
Max Suraev <msuraev at sysmocom.de> http://www.sysmocom.de/
======================================================================= 
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93 
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B 
* Geschaeftsfuehrer / Managing Director: Harald Welte 




More information about the OpenBSC mailing list