Project

General

Profile

Bug #3981

osmo-trx-lms: Overruns appear from time to time

Added by pespin about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
sysmocom
Category:
LimeSDR
Target version:
-
Start date:
05/07/2019
Due date:
% Done:

0%

Spec Reference:

Description

It was spotted that from time to time osmo-trx-lms tends to not provide data quick enough and some samples are lost. It should be investigated why that happens and find some way to fix this behavior.
Those overruns appear despite rt-prio being enabled (#3971), so let's track this issue here in a separate ticket.
Thanks to fix from #3339, now this kind of overruns are not fatal and osmo-trx sends garbage during those lost samples, but still it's not fine to run into this situation.

This kind of overrun has been seen on high end laptops. It could be related to PM or other processes disturbing the scheduler. It has also been said that it may be related to USB controllers being used.
It could be that we don't see this anymore once we can use rt-prio with LMS (#3971).


Related issues

Related to OsmoTRX - Bug #3971: osmo-trx-lms: makes kernel eat all system memory when run under realtime priorityNew05/03/2019

Related to OsmoTRX - Bug #3339: osmo-trx-lms "expect ... got ... diff ff0" error messageFeedback06/13/2018

History

#1 Updated by pespin about 1 month ago

  • Related to Bug #3971: osmo-trx-lms: makes kernel eat all system memory when run under realtime priority added

#2 Updated by pespin about 1 month ago

  • Related to Bug #3339: osmo-trx-lms "expect ... got ... diff ff0" error message added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)