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/.
Alexander Chemeris alexander.chemeris at gmail.comHi Max, On Mon, Jun 13, 2016 at 6:15 PM, Max <msuraev at sysmocom.de> wrote: > While running osmo-trx with B200 I've noticed following log messages > repeated multiple times: > > 1) WARNING 3011271488 16:59:00.1 Transceiver.cpp:674:pullRadioVector: > Clipping detected on received RACH or Normal Burst This means that your phone transmit at a level which saturates BTS's receive chain. Osmo-trx can't demodulate the signal and prints this message. I don't have much experience with USRPs, but general way to avoid this is: 1) Decrease "ms max power", so that phone starts with lower power, 2) Reduce "rxgain" in osmo-bts config 3) Add an attenuator to your Tx/Rx chains. > 2) ERR 3011304256 16:58:12.9 UHDDevice.cpp:1512:write: Skipping buffer > data: timestamp=210353475 time_end=202360063 This means that you're loosing samples between the device and UHD. Can't help you much here, because it's device specific. May be Thomas can suggest something. This is not the end of the world, but it may lead to all kinds of unstable behavior similar to when you have really bad radio link and bursts are dropped randomly. -- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co