36fa0bd079
Previously it could be possible that the attribute request comes from BSC before the TRX is properly initialized which would lead to SIGABRT caused by OSMO_ASSERT() in PHY instantiation. Workaround this by explicitly checking for TRX availability before handling TRX-specific attributes. This only happens with osmo-bts-trx and is hard to reproduce. Ideal fix would be to defer attribute response until we have TRX connected but that would make corresponding code more complex because we'll need to save the attribute request and properly hook response routine into TRX connection handler. Alternatively we can postpone osmo-bts-trx connection to BSC until TRX is available: it's not very useful without it anyway. Change-Id: Id36885e507c4a3203b5662c0fde12c5206174d82 Fixes: OS#2560 |
||
|---|---|---|
| .. | ||
| common | ||
| osmo-bts-litecell15 | ||
| osmo-bts-octphy | ||
| osmo-bts-sysmo | ||
| osmo-bts-trx | ||
| osmo-bts-virtual | ||
| Makefile.am | ||