https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092017-12-08T17:46:49ZOpen Source Mobile CommunicationsOsmoTRX - Bug #2723: osmo-trx-uhd: failure to update CLOCK IND, timeout with LimeSDRhttps://projects.osmocom.org/issues/2723?journal_id=66202017-12-08T17:46:49Zpespin
<ul></ul><p>I forge to add that after a while (even after I already stopped osmo-bts-trx), I get the following lines in the output:</p>
<pre>
INFO 140737354032896 17:52:48.6 /home/pespin/dev/sysmocom/git/osmo-trx/Transceiver52M/Transceiver.cpp:880:driveReceiveRadio: ClockInterface: skipping clock ind: force=0 3:1786262 > 3:1786337
ERR 140737354032896 17:52:48.7 /home/pespin/dev/sysmocom/git/osmo-trx/Transceiver52M/UHDDevice.cpp:844:check_rx_md_err: No packet received, implementation timed-out at 27.0777 sec.
ALERT 140737354032896 17:52:48.7 /home/pespin/dev/sysmocom/git/osmo-trx/Transceiver52M/UHDDevice.cpp:848:check_rx_md_err: UHD: Receive timed out
[New Thread 0x7fffeb7fe700 (LWP 14511)]
ALERT 140737354032896 17:52:48.7 /home/pespin/dev/sysmocom/git/osmo-trx/Transceiver52M/radioInterface.cpp:320:pullBuffer: Receive error 0
INFO 140737354032896 17:52:48.7 /home/pespin/dev/sysmocom/git/osmo-trx/Transceiver52M/Transceiver.cpp:880:driveReceiveRadio: ClockInterface: skipping clock ind: force=0 3:1786262 > 3:1786337
[New Thread 0x7fffe155e700 (LWP 14512)]
[New Thread 0x7fffe0d5d700 (LWP 14513)]
ALERT 140737354032896 17:52:48.7 /home/pespin/dev/sysmocom/git/osmo-trx/Transceiver52M/UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time
[Thread 0x7fffe155e700 (LWP 14512) exited]
[Thread 0x7fffe0d5d700 (LWP 14513) exited]
[Thread 0x7fffeb7fe700 (LWP 14511) exited]
[New Thread 0x7fffeb7fe700 (LWP 14517)]
[New Thread 0x7fffe155e700 (LWP 14519)]
[New Thread 0x7fffe0d5d700 (LWP 14518)]
[Thread 0x7fffe0d5d700 (LWP 14518) exited]
[Thread 0x7fffe155e700 (LWP 14519) exited]
[Thread 0x7fffeb7fe700 (LWP 14517) exited]
[New Thread 0x7fffeb7fe700 (LWP 14520)]
[New Thread 0x7fffe155e700 (LWP 14521)]
[New Thread 0x7fffe0d5d700 (LWP 14522)]
ALERT 140737354032896 17:52:48.7 /home/pespin/dev/sysmocom/git/osmo-trx/Transceiver52M/UHDDevice.cpp:868:check_rx_md_err: Current time: 0, Previous time: 27.0758
INFO 140737354098432 17:52:50.2 /home/pespin/dev/sysmocom/git/osmo-trx/Transceiver52M/UHDDevice.cpp:473:setTxGain: Set TX gain to 44dB (asked for 44dB)
INFO 140737354098432 17:52:50.2 /home/pespin/dev/sysmocom/git/osmo-trx/Transceiver52M/Transceiver.cpp:685:driveControl: command is CMD SETPOWER 20
ALERT 140737354065664 17:52:50.4 /home/pespin/dev/sysmocom/git/osmo-trx/Transceiver52M/UHDDevice.cpp:1022:writeSamples: UHD: Device send timed out
</pre> OsmoTRX - Bug #2723: osmo-trx-uhd: failure to update CLOCK IND, timeout with LimeSDRhttps://projects.osmocom.org/issues/2723?journal_id=67672017-12-12T03:01:18Zttsou
<ul></ul><pre>
UHDDevice.cpp:844:check_rx_md_err: No packet received, implementation timed-out at 27.0777 sec.
UHDDevice.cpp:848:check_rx_md_err: UHD: Receive timed out
UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time
UHDDevice.cpp:1022:writeSamples: UHD: Device send timed out
</pre>
<p>The above truncated sequence of errors indicates that the device has stopped (or never started) sending sample packets to the host. The cause is device specific, but similar issues are often associated with flow control and/or overrun handling.</p>
<p>The receive sample packet stream from the device drives the TRX internal clock loop that drives both the CLK IND messages and the TRX transmit path.</p>
<p>To resolve this issue, determine why the LimeSDR is not sending samples to the host.</p> OsmoTRX - Bug #2723: osmo-trx-uhd: failure to update CLOCK IND, timeout with LimeSDRhttps://projects.osmocom.org/issues/2723?journal_id=69972018-01-04T10:36:26Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-2 priority-default closed" href="/issues/2816">Bug #2816</a>: osmo-trx-uhd: bug with limesdr send timed out</i> added</li></ul> OsmoTRX - Bug #2723: osmo-trx-uhd: failure to update CLOCK IND, timeout with LimeSDRhttps://projects.osmocom.org/issues/2723?journal_id=70432018-01-04T11:10:35Zlaforge
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul> OsmoTRX - Bug #2723: osmo-trx-uhd: failure to update CLOCK IND, timeout with LimeSDRhttps://projects.osmocom.org/issues/2723?journal_id=75642018-02-09T21:02:21Zlaforge
<ul><li><strong>Category</strong> set to <i>LimeSDR</i></li></ul> OsmoTRX - Bug #2723: osmo-trx-uhd: failure to update CLOCK IND, timeout with LimeSDRhttps://projects.osmocom.org/issues/2723?journal_id=92242018-05-09T09:36:55Zpespin
<ul><li><strong>Subject</strong> changed from <i>osmo-trx: failure to update CLOCK IND, timeout with LimeSDR</i> to <i>osmo-trx-uhd: failure to update CLOCK IND, timeout with LimeSDR</i></li></ul> OsmoTRX - Bug #2723: osmo-trx-uhd: failure to update CLOCK IND, timeout with LimeSDRhttps://projects.osmocom.org/issues/2723?journal_id=92252018-05-09T09:39:11Zpespin
<ul></ul><p>Using latest LimeSuite b1f38113328fa5128adf11fc6e54898cbfea4a78.</p>
<p>Running latest master osmo-trx-uhd I can still see this issue.<br />However, using latest osmo-trx-lms (branch laforge/lime), the clock is far more stable, with similar error values than when running osmo-trx-uhd with an ettus b200. osmo-bts-trx doesn't exit prematurely in this case.</p> OsmoTRX - Bug #2723: osmo-trx-uhd: failure to update CLOCK IND, timeout with LimeSDRhttps://projects.osmocom.org/issues/2723?journal_id=93702018-05-17T11:41:18Zlaforge
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Low</i></li></ul><p>reclassifying as "Low" as we are working on osmo-bts-lms to address this.</p> OsmoTRX - Bug #2723: osmo-trx-uhd: failure to update CLOCK IND, timeout with LimeSDRhttps://projects.osmocom.org/issues/2723?journal_id=98662018-06-12T16:30:28Zpespin
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-3 status-5 priority-2 priority-default closed" href="/issues/3316">Support #3316</a>: osmo-trx-uhd fails after OpenBTS starts, LimeSDR</i> added</li></ul> OsmoTRX - Bug #2723: osmo-trx-uhd: failure to update CLOCK IND, timeout with LimeSDRhttps://projects.osmocom.org/issues/2723?journal_id=98732018-06-12T16:43:55Zpespin
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-2 priority-default closed" href="/issues/3039">Bug #3039</a>: LimeSDR: Lots of lost signalling blocks ends voice call with "Connection Failure" after a few seconds</i> added</li></ul> OsmoTRX - Bug #2723: osmo-trx-uhd: failure to update CLOCK IND, timeout with LimeSDRhttps://projects.osmocom.org/issues/2723?journal_id=150132019-06-27T16:13:34Zroh
<ul></ul><p>i think this can be closed - we do not support limesdr via UHD anymore in osmo-trx.</p> OsmoTRX - Bug #2723: osmo-trx-uhd: failure to update CLOCK IND, timeout with LimeSDRhttps://projects.osmocom.org/issues/2723?journal_id=157142019-08-27T08:53:26Zpespin
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul>