17 Jan
2018
17 Jan
'18
12:40 a.m.
Hi,
I am using LimeSDR and I would like to setup a mini GSM base station. I am
following this instructions:
https://discourse.myriadrf.org/t/limesdr-osmo-trx-no-work/1938/27
However, I am getting trouble starting tranceiver:
*TERMINAL 1:*
ronan@ronan-MS-N014:~/Downloads$ osmo-nitb -c openbsc.cfg -l hlr.sqlite3 -P
-C
<0005> abis_nm.c:2800 (bts=0,trx=0) Changing adm. state Unlocked ->
Unlocked [vty]
<001e> telnet_interface.c:104 telnet at 127.0.0.1 4242
<0005> bsc_init.c:465
WARNING: You are running an 'accept-all' network on a BTS that is not
barred. This configuration is likely to interfere with production GSM
networks and should only be used in a RF shielded environment such as a
faraday cage!
<0020> input/ipaccess.c:848 enabling ipaccess BSC mode on 0.0.0.0 with OML
3002 and RSL 3003 TCP ports
<0017> smpp_smsc.c:1001 SMPP at 0.0.0.0 2775
<0025> control_if.c:854 CTRL at 127.0.0.1 4249
DB: Database initialized.
DB: Database prepared.
<0020> input/ipa.c:263 accept()ed new link from 127.0.0.1 to port 3002
<0005> abis_nm.c:507 BTS0 feature 'EGPRS' reported via OML does not match
statically set feature: 0 != 1. Please fix.
<0005> abis_nm.c:507 BTS0 feature 'OML Alerts' reported via OML does not
match statically set feature: 1 != 0. Please fix.
<0005> abis_nm.c:573 BTS0: ARI reported sw[0/2]: sysmobts is 0.7.0.20180115
<0005> abis_nm.c:446 BTS0 reported variant: omso-bts-trx
<0005> abis_nm.c:468 BTS0 Attribute Manufacturer Dependent State is
unreported
<0005> abis_nm.c:573 BTS0: ARI reported sw[0/1]: TRX_PHY_VERSION is Unknown
<0020> input/ipa.c:263 accept()ed new link from 127.0.0.1 to port 3003
<0004> bsc_init.c:311 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 514
using MCC=1 MNC=1 LAC=1 CID=0 BSIC=63
<0020> input/ipaccess.c:243 Sign link vanished, dead socket
<0020> input/ipaccess.c:71 Forcing socket shutdown with no signal link set
*TERMINAL 2:*
ronan@ronan-MS-N014:~/Downloads$ osmo-bts-trx -c osmo-bts.cfg
((*))
|
/ \ OsmoBTS
<0017> control_if.c:854 CTRL at 127.0.0.1 4238
<0010> telnet_interface.c:104 telnet at 127.0.0.1 4241
<0012> input/ipaccess.c:886 enabling ipaccess BTS mode, OML connecting to
127.0.0.1:3002
<000b> trx_if.c:599 Open transceiver for phy0.0
<0012> input/ipa.c:129 connection done.
<0012> input/ipaccess.c:707 received ID get
<0001> oml.c:229 O&M Get Attributes [0], Manufacturer Dependent State is
unsupported by TRX.
<0001> oml.c:680 Ignoring T200[0] (150 ms) as sent by BSC due to suspected
LAPDm bug!
<0001> oml.c:680 Ignoring T200[1] (180 ms) as sent by BSC due to suspected
LAPDm bug!
<0001> oml.c:680 Ignoring T200[2] (180 ms) as sent by BSC due to suspected
LAPDm bug!
<0001> oml.c:680 Ignoring T200[3] (1680 ms) as sent by BSC due to suspected
LAPDm bug!
<0001> oml.c:680 Ignoring T200[4] (520 ms) as sent by BSC due to suspected
LAPDm bug!
<0001> oml.c:680 Ignoring T200[5] (165 ms) as sent by BSC due to suspected
LAPDm bug!
<0001> oml.c:680 Ignoring T200[6] (1680 ms) as sent by BSC due to suspected
LAPDm bug!
<0001> oml.c:1049 ADM state already was Unlocked
<0012> input/ipa.c:129 connection done.
<0012> input/ipaccess.c:707 received ID get
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1108205-0=1108205 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1108421-1108300=121 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1108638-1108435=203 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1108855-1108652=203 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1109072-1108870=202 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1109289-1109086=203 > 1!
<0001> bts.c:210 Shutting down BTS 0, Reason No clock from osmo-trx
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1112227-1109693=2534 > 1!
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> bts.c:205 BTS is already being shutdown.
<000b> trx_if.c:172 No response from transceiver for phy0.0
Shutdown timer expired
ronan@ronan-MS-N014:~/Downloads$
*TERMINAL 3:*
ronan@ronan-MS-N014:~/Downloads$ sudo osmo-trx -e
[sudo] password for ronan:
linux; GNU C++ version 5.4.0 20160609 <%2802%29%20016%200609>;
Boost_105800; UHD_003.010.002.000-release
Info: SSE3 support compiled in and supported by CPU
Info: SSE4.1 support compiled in, but not supported by CPU
Config Settings
Log Level............... NOTICE
Device args.............
TRX Base Port........... 5700
TRX Address............. 127.0.0.1
GSM Core Address.........127.0.0.1
Channels................ 1
Tx Samples-per-Symbol... 4
Rx Samples-per-Symbol... 4
EDGE support............ Enabled
Reference............... Internal
C0 Filler Table......... Disabled
Multi-Carrier........... Disabled
Tuning offset........... 0
RSSI to dBm offset...... 0
Swap channels........... 0
-- Make connection: 'LimeSDR-USB [USB 2.0] 9060B00470E28'
-- Reference clock 30.720 MHz
-- Device name: LimeSDR-USB
-- Reference: 30.72 MHz
-- Init LMS7002M(0)
-- Ver=7, Rev=1, Mask=1
-- LMS7002M calibration values caching Disable
-- Transceiver active with 1 channel(s)
NOTICE 139639362156288 07:03:23.5 Transceiver.cpp:791:driveControl:
Changing TSC from 0 to 7
NOTICE 139639362156288 07:03:23.5 Transceiver.cpp:244:start: Starting the
transceiver
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=174420 time_end=171360
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=174420 time_end=171360
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=179520 time_end=176460
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=179520 time_end=176460
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=184620 time_end=181560
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=184620 time_end=181560
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=190740 time_end=186660
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=190740 time_end=186660
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=196860 time_end=192780
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=196860 time_end=192780
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=201960 time_end=198900
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=201960 time_end=198900
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=207060 time_end=204000
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=207060 time_end=204000
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=213180 time_end=209100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=213180 time_end=209100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=217260 time_end=215220
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=217260 time_end=215220
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=224400 time_end=219300
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=224400 time_end=219300
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=229500 time_end=226440
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=229500 time_end=226440
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=234600 time_end=231540
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=234600 time_end=231540
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=239700 time_end=236640
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=239700 time_end=236640
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=245820 time_end=241740
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=245820 time_end=241740
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=251940 time_end=247860
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=251940 time_end=247860
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=258060 time_end=253980
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=258060 time_end=253980
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=263160 time_end=260100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=263160 time_end=260100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=268260 time_end=265200
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=268260 time_end=265200
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=273360 time_end=270300
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=273360 time_end=270300
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=279480 time_end=275400
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=279480 time_end=275400
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=285600 time_end=281520
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=285600 time_end=281520
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=290700 time_end=287640
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=290700 time_end=287640
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=322320 time_end=292740
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=322320 time_end=292740
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=328440 time_end=324360
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=328440 time_end=324360
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=333540 time_end=330480
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=333540 time_end=330480
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=338640 time_end=335580
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=338640 time_end=335580
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=343740 time_end=340680
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=343740 time_end=340680
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=349860 time_end=345780
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=349860 time_end=345780
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=355980 time_end=351900
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=355980 time_end=351900
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=360060 time_end=358020
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=360060 time_end=358020
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=367200 time_end=362100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=367200 time_end=362100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=372300 time_end=369240
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=372300 time_end=369240
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=378420 time_end=374340
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=378420 time_end=374340
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=383520 time_end=380460
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=383520 time_end=380460
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=389640 time_end=385560
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=389640 time_end=385560
ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:867:check_rx_md_err: UHD:
Loss of monotonic time
ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:867:check_rx_md_err: UHD:
Loss of monotonic time
ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:868:check_rx_md_err: Current
time: 0, Previous time: 0.359668
ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:868:check_rx_md_err: Current
time: 0, Previous time: 0.359668
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD:
Loss of monotonic time
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD:
Loss of monotonic time
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err: Current
time: 0.120517, Previous time: 0.359668
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err: Current
time: 0.120517, Previous time: 0.359668
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=399840 time_end=391680
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=399840 time_end=391680
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=410040 time_end=408000
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=410040 time_end=408000
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=415140 time_end=412080
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=415140 time_end=412080
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD:
Loss of monotonic time
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD:
Loss of monotonic time
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err: Current
time: 0, Previous time: 0.383206
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err: Current
time: 0, Previous time: 0.383206
ERR 139639362090752 07:03:24.8 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=440640 time_end=417180
ERR 139639362090752 07:03:24.8 UHDDevice.cpp:1383:write: Skipping
17 Jan
17 Jan
12:55 a.m.
Hi,
have a look at https://osmocom.org/issues/2723, seems similar to what I
have been experiencing recently. Today I spent some more time looking
into it and I found out most issues in osmo-trx seem to come from
Limesuite layer, in my case returning SOAPY_SDR_TIMEOUT and outputing
timeout errors in osmo-trx log.
I started writing and testing some improvements into osmo-trx and
osmo-bts-trx, which hopefully will make the startup more stable. I think
I'll be able to push the changeset tomorrow to gerrit.
--
- Pau Espin Pedrol <pespin(a)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
3:27 a.m.
Hi Pau
Thanks a lot on this. Hopefully this will fix our problem
Thanks
Ronan
On Wed, Jan 17, 2018 at 7:55 AM, Pau Espin Pedrol <pespin(a)sysmocom.de>
wrote:
Hi,
have a look at https://osmocom.org/issues/2723, seems similar to what I
have been experiencing recently. Today I spent some more time looking into
it and I found out most issues in osmo-trx seem to come from Limesuite
layer, in my case returning SOAPY_SDR_TIMEOUT and outputing timeout errors
in osmo-trx log.
I started writing and testing some improvements into osmo-trx and
osmo-bts-trx, which hopefully will make the startup more stable. I think
I'll be able to push the changeset tomorrow to gerrit.
--
- Pau Espin Pedrol <pespin(a)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
6:43 a.m.
Yesss...
Hopefully it will be fix soon cause im gonna test more with osno-bsc
osmo-hlr osmo-msc which osno-trx has problem with limesdr.
Thanks Pespin. :)
Regards,
DUO
On Jan 17, 2018 9:27 AM, "Ronan Empig" <ronemp(a)gmail.com> wrote:
Hi Pau
Thanks a lot on this. Hopefully this will fix our problem
Thanks
Ronan
On Wed, Jan 17, 2018 at 7:55 AM, Pau Espin Pedrol <pespin(a)sysmocom.de>
wrote:
Hi,
have a look at https://osmocom.org/issues/2723, seems similar to what I
have been experiencing recently. Today I spent some more time looking into
it and I found out most issues in osmo-trx seem to come from Limesuite
layer, in my case returning SOAPY_SDR_TIMEOUT and outputing timeout errors
in osmo-trx log.
I started writing and testing some improvements into osmo-trx and
osmo-bts-trx, which hopefully will make the startup more stable. I think
I'll be able to push the changeset tomorrow to gerrit.
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
<https://maps.google.com/?q=Alt-Moabit+93+%0D+*+10559+Berlin,+Germany&entry=gmail&source=g>
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
19 Jan
19 Jan
2:20 a.m.
Hi Pau
Any updates on this one?
Thanks
Ronan
On Wed, Jan 17, 2018 at 10:27 AM, Ronan Empig <ronemp(a)gmail.com> wrote:
Hi Pau
Thanks a lot on this. Hopefully this will fix our problem
Thanks
Ronan
On Wed, Jan 17, 2018 at 7:55 AM, Pau Espin Pedrol <pespin(a)sysmocom.de>
wrote:
Hi,
have a look at https://osmocom.org/issues/2723, seems similar to what I
have been experiencing recently. Today I spent some more time looking into
it and I found out most issues in osmo-trx seem to come from Limesuite
layer, in my case returning SOAPY_SDR_TIMEOUT and outputing timeout errors
in osmo-trx log.
I started writing and testing some improvements into osmo-trx and
osmo-bts-trx, which hopefully will make the startup more stable. I think
I'll be able to push the changeset tomorrow to gerrit.
--
- Pau Espin Pedrol <pespin(a)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
6:16 a.m.
Hi Jimmy
I am copying you on our mailing list. Here is the updates so far on our
installation. It is still not working.
Ronan
On Fri, Jan 19, 2018 at 9:20 AM, Ronan Empig <ronemp(a)gmail.com> wrote:
Hi Pau
Any updates on this one?
Thanks
Ronan
On Wed, Jan 17, 2018 at 10:27 AM, Ronan Empig <ronemp(a)gmail.com> wrote:
Hi Pau
Thanks a lot on this. Hopefully this will fix our problem
Thanks
Ronan
On Wed, Jan 17, 2018 at 7:55 AM, Pau Espin Pedrol <pespin(a)sysmocom.de>
wrote:
Hi,
have a look at https://osmocom.org/issues/2723, seems similar to what I
have been experiencing recently. Today I spent some more time looking into
it and I found out most issues in osmo-trx seem to come from Limesuite
layer, in my case returning SOAPY_SDR_TIMEOUT and outputing timeout errors
in osmo-trx log.
I started writing and testing some improvements into osmo-trx and
osmo-bts-trx, which hopefully will make the startup more stable. I think
I'll be able to push the changeset tomorrow to gerrit.
--
- Pau Espin Pedrol <pespin(a)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
12:14 p.m.
Hi Ronan,
I did some work to fix some stability problems I saw in osmo-bts-trx
while testing osmo-trx with limesdr. They are in gerrit [1] but haven't
been reviewed yet and jenkins validation failed due to issue being
addressed in [2] which in turn was not merged yet neither.
However, while these patches clear a bit the mess in the logs and may
fix some eventual issues, the reality is that the problem is still
there, and as far as I understand they come from the limesuite layer. It
seems it fails to retrieve packets when asked from upper layers, which
means the clock is not updated and then osmo-bts-trx stops. I so far
went down through the layers to see the paths being used but got lost
around the point in which it reads from the fifo in limesuite. I
couldn't find yet who is populating that fifo from the device.
As a reminder, the issue is being tracked in [3].
[1] https://gerrit.osmocom.org/#/c/5856
[2] https://gerrit.osmocom.org/#/c/5818/
[3] https://osmocom.org/issues/2723
--
- Pau Espin Pedrol <pespin(a)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
21 Jan
21 Jan
7:06 p.m.
Hi Pau
I will try the one in gerrit but just to let you know, I have not run the
osmo-trx successfully even for a small while. Other people have run it and
had some success early on though will encounter errors after some time.
I am using an MSI notebook ang am wondering if it has something to do with
it as it has AMD chip.
Let me know if you can think of something about this.
PS:
Also, are you guys having the same version/changes in
https://github.com/osmocom/osmo-trx ?
I use install.sh in the link I sent so if you have updated the github then
I will not need to update the files that will be automatically downloaded
here.
Please let me know.
Thanks
Ronan
On Fri, Jan 19, 2018 at 7:14 PM, Pau Espin Pedrol <pespin(a)sysmocom.de>
wrote:
Hi Ronan,
I did some work to fix some stability problems I saw in osmo-bts-trx while
testing osmo-trx with limesdr. They are in gerrit [1] but haven't been
reviewed yet and jenkins validation failed due to issue being addressed in
[2] which in turn was not merged yet neither.
However, while these patches clear a bit the mess in the logs and may fix
some eventual issues, the reality is that the problem is still there, and
as far as I understand they come from the limesuite layer. It seems it
fails to retrieve packets when asked from upper layers, which means the
clock is not updated and then osmo-bts-trx stops. I so far went down
through the layers to see the paths being used but got lost around the
point in which it reads from the fifo in limesuite. I couldn't find yet who
is populating that fifo from the device.
As a reminder, the issue is being tracked in [3].
[1] https://gerrit.osmocom.org/#/c/5856
[2] https://gerrit.osmocom.org/#/c/5818/
[3] https://osmocom.org/issues/2723
--
- Pau Espin Pedrol <pespin(a)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
22 Jan
22 Jan
12:02 a.m.
Hi Ronan,
On 21/01/18 19:06, Ronan Empig wrote:
I am using an MSI notebook ang am wondering if it has
something to do
with it as it has AMD chip.
I don't think it's going to have any relation with that fact.
By the way, I had the same issues whiles running it being detected as a
usb3 device as well as for the usb2 case, so that specific factor
doesn't seem to be important regarding the clock issues I am seeing.
Also, are you guys having the same version/changes in
https://github.com/osmocom/osmo-trx ?
As far as I know, that github repo is a mirror from the official one:
https://git.osmocom.org/osmo-trx/
I guess it becomes synced every few hours or so.
The patches I did a few days ago in osmo-trx have been already merged
and are also already available in the osmo-trx hithub mirror you
described. However, as I already stated, the patches may help a bit with
some stability issues but won't definitely solve the clocking issues
appearing most of the time.
--
- Pau Espin Pedrol <pespin(a)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
17 Jan
17 Jan
2:01 p.m.
Hi,
I don't know if its coincidence, but when trying osmo-trx with a USRP2
in a computer without SSE4.1, osmo-trx was aborting very often, but when
working in a computer with SSE4.1, it got much more stable.
Best regards,
Rafael Diniz
On 01/16/2018 09:40 PM, Ronan Empig wrote:
Hi,
I am using LimeSDR and I would like to setup a mini GSM base station. I
am following this instructions:
https://discourse.myriadrf.org/t/limesdr-osmo-trx-no-work/1938/27
<https://discourse.myriadrf.org/t/limesdr-osmo-trx-no-work/1938/27>
However, I am getting trouble starting tranceiver:
*TERMINAL 1:*
ronan@ronan-MS-N014:~/Downloads$ osmo-nitb -c openbsc.cfg -l hlr.sqlite3
-P -C
<0005> abis_nm.c:2800 (bts=0,trx=0) Changing adm. state Unlocked ->
Unlocked [vty]
<001e> telnet_interface.c:104 telnet at 127.0.0.1 4242
<0005> bsc_init.c:465
WARNING: You are running an 'accept-all' network on a BTS that is not
barred. This configuration is likely to interfere with production GSM
networks and should only be used in a RF shielded environment such as a
faraday cage!
<0020> input/ipaccess.c:848 enabling ipaccess BSC mode on 0.0.0.0 with
OML 3002 and RSL 3003 TCP ports
<0017> smpp_smsc.c:1001 SMPP at 0.0.0.0 2775
<0025> control_if.c:854 CTRL at 127.0.0.1 4249
DB: Database initialized.
DB: Database prepared.
<0020> input/ipa.c:263 accept()ed new link from 127.0.0.1 to port 3002
<0005> abis_nm.c:507 BTS0 feature 'EGPRS' reported via OML does not
match statically set feature: 0 != 1. Please fix.
<0005> abis_nm.c:507 BTS0 feature 'OML Alerts' reported via OML does not
match statically set feature: 1 != 0. Please fix.
<0005> abis_nm.c:573 BTS0: ARI reported sw[0/2]: sysmobts is 0.7.0.20180115
<0005> abis_nm.c:446 BTS0 reported variant: omso-bts-trx
<0005> abis_nm.c:468 BTS0 Attribute Manufacturer Dependent State is
unreported
<0005> abis_nm.c:573 BTS0: ARI reported sw[0/1]: TRX_PHY_VERSION is Unknown
<0020> input/ipa.c:263 accept()ed new link from 127.0.0.1 to port 3003
<0004> bsc_init.c:311 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 514
using MCC=1 MNC=1 LAC=1 CID=0 BSIC=63
<0020> input/ipaccess.c:243 Sign link vanished, dead socket
<0020> input/ipaccess.c:71 Forcing socket shutdown with no signal link set
*TERMINAL 2:*
*
*
ronan@ronan-MS-N014:~/Downloads$ osmo-bts-trx -c osmo-bts.cfg
((*))
|
/ \ OsmoBTS
<0017> control_if.c:854 CTRL at 127.0.0.1 4238
<0010> telnet_interface.c:104 telnet at 127.0.0.1 4241
<0012> input/ipaccess.c:886 enabling ipaccess BTS mode, OML connecting
to 127.0.0.1:3002 <http://127.0.0.1:3002/>
<000b> trx_if.c:599 Open transceiver for phy0.0
<0012> input/ipa.c:129 connection done.
<0012> input/ipaccess.c:707 received ID get
<0001> oml.c:229 O&M Get Attributes [0], Manufacturer Dependent State is
unsupported by TRX.
<0001> oml.c:680 Ignoring T200[0] (150 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[1] (180 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[2] (180 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[3] (1680 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[4] (520 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[5] (165 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[6] (1680 ms) as sent by BSC due to
suspected LAPDm bug!
<0001> oml.c:1049 ADM state already was Unlocked
<0012> input/ipa.c:129 connection done.
<0012> input/ipaccess.c:707 received ID get
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1108205-0=1108205 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1108421-1108300=121 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1108638-1108435=203 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1108855-1108652=203 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1109072-1108870=202 > 1!
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1109289-1109086=203 > 1!
<0001> bts.c:210 Shutting down BTS 0, Reason No clock from osmo-trx
<0007> l1sap.c:462 Invalid condition detected: Frame difference is
1112227-1109693=2534 > 1!
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> oml.c:1049 ADM state already was Unlocked
<0001> bts.c:205 BTS is already being shutdown.
<000b> trx_if.c:172 No response from transceiver for phy0.0
Shutdown timer expired
ronan@ronan-MS-N014:~/Downloads$*
*
*TERMINAL 3:*
*
*
ronan@ronan-MS-N014:~/Downloads$ sudo osmo-trx -e
[sudo] password for ronan:
linux; GNU C++ version 5.4.0 20160609 <tel:%2802%29%20016%200609>;
Boost_105800; UHD_003.010.002.000-release
Info: SSE3 support compiled in and supported by CPU
Info: SSE4.1 support compiled in, but not supported by CPU
Config Settings
Log Level............... NOTICE
Device args.............
TRX Base Port........... 5700
TRX Address............. 127.0.0.1
GSM Core Address.........127.0.0.1
Channels................ 1
Tx Samples-per-Symbol... 4
Rx Samples-per-Symbol... 4
EDGE support............ Enabled
Reference............... Internal
C0 Filler Table......... Disabled
Multi-Carrier........... Disabled
Tuning offset........... 0
RSSI to dBm offset...... 0
Swap channels........... 0
-- Make connection: 'LimeSDR-USB [USB 2.0] 9060B00470E28'
-- Reference clock 30.720 MHz
-- Device name: LimeSDR-USB
-- Reference: 30.72 MHz
-- Init LMS7002M(0)
-- Ver=7, Rev=1, Mask=1
-- LMS7002M calibration values caching Disable
-- Transceiver active with 1 channel(s)
NOTICE 139639362156288 07:03:23.5 Transceiver.cpp:791:driveControl:
Changing TSC from 0 to 7
NOTICE 139639362156288 07:03:23.5 Transceiver.cpp:244:start: Starting
the transceiver
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=174420 time_end=171360
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=174420 time_end=171360
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=179520 time_end=176460
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=179520 time_end=176460
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=184620 time_end=181560
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=184620 time_end=181560
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=190740 time_end=186660
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=190740 time_end=186660
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=196860 time_end=192780
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=196860 time_end=192780
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=201960 time_end=198900
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=201960 time_end=198900
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=207060 time_end=204000
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=207060 time_end=204000
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=213180 time_end=209100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=213180 time_end=209100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=217260 time_end=215220
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=217260 time_end=215220
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=224400 time_end=219300
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=224400 time_end=219300
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=229500 time_end=226440
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=229500 time_end=226440
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=234600 time_end=231540
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=234600 time_end=231540
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=239700 time_end=236640
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=239700 time_end=236640
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=245820 time_end=241740
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=245820 time_end=241740
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=251940 time_end=247860
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=251940 time_end=247860
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=258060 time_end=253980
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=258060 time_end=253980
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=263160 time_end=260100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=263160 time_end=260100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=268260 time_end=265200
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=268260 time_end=265200
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=273360 time_end=270300
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=273360 time_end=270300
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=279480 time_end=275400
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=279480 time_end=275400
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=285600 time_end=281520
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=285600 time_end=281520
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=290700 time_end=287640
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=290700 time_end=287640
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=322320 time_end=292740
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=322320 time_end=292740
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=328440 time_end=324360
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=328440 time_end=324360
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=333540 time_end=330480
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=333540 time_end=330480
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=338640 time_end=335580
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=338640 time_end=335580
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=343740 time_end=340680
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=343740 time_end=340680
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=349860 time_end=345780
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=349860 time_end=345780
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=355980 time_end=351900
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=355980 time_end=351900
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=360060 time_end=358020
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=360060 time_end=358020
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=367200 time_end=362100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=367200 time_end=362100
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=372300 time_end=369240
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=372300 time_end=369240
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=378420 time_end=374340
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=378420 time_end=374340
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=383520 time_end=380460
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=383520 time_end=380460
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=389640 time_end=385560
ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=389640 time_end=385560
ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:867:check_rx_md_err: UHD:
Loss of monotonic time
ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:867:check_rx_md_err: UHD:
Loss of monotonic time
ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:868:check_rx_md_err:
Current time: 0, Previous time: 0.359668
ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:868:check_rx_md_err:
Current time: 0, Previous time: 0.359668
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD:
Loss of monotonic time
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD:
Loss of monotonic time
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err:
Current time: 0.120517, Previous time: 0.359668
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err:
Current time: 0.120517, Previous time: 0.359668
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=399840 time_end=391680
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=399840 time_end=391680
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=410040 time_end=408000
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=410040 time_end=408000
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=415140 time_end=412080
ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=415140 time_end=412080
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD:
Loss of monotonic time
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD:
Loss of monotonic time
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err:
Current time: 0, Previous time: 0.383206
ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err:
Current time: 0, Previous time: 0.383206
ERR 139639362090752 07:03:24.8 UHDDevice.cpp:1383:write: Skipping buffer
data: timestamp=440640 time_end=417180
ERR 139639362090752 07:03:24.8 UHDDevice.cpp:1383:write: Skipping
2:31 p.m.
On Wed, Jan 17, 2018 at 11:01:19AM -0200, Rafael Diniz wrote:
I don't know if its coincidence, but when trying
osmo-trx with a USRP2
in a computer without SSE4.1, osmo-trx was aborting very often, but when
working in a computer with SSE4.1, it got much more stable.
Which version of osmo-trx were you using? We used to have a bug in this
area, see http://osmocom.org/issues/2386 fixed in https://gerrit.osmocom.org/#/c/4892/
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
3:21 p.m.
Im using 14/01/2018 nightly build on Debian 9, but I need to investigate
further the problem.
On 01/17/2018 11:31 AM, Harald Welte wrote:
On Wed, Jan 17, 2018 at 11:01:19AM -0200, Rafael Diniz
wrote:
I don't know if its coincidence, but when
trying osmo-trx with a USRP2
in a computer without SSE4.1, osmo-trx was aborting very often, but when
working in a computer with SSE4.1, it got much more stable.
Which version of osmo-trx were you using? We used to have a bug in this
area, see http://osmocom.org/issues/2386 fixed in https://gerrit.osmocom.org/#/c/4892/
2294
days inactive
2299
days old
11 comments
5 participants
participants (5)
-
Harald Welte -
Pau Espin Pedrol -
Rafael Diniz -
Ronan Empig -
Sandi Suhendro