Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nullpointer exception when calling uhd_tx_streamer_send #134

Closed
FabianEckermann opened this issue Oct 24, 2017 · 5 comments
Closed

Nullpointer exception when calling uhd_tx_streamer_send #134

FabianEckermann opened this issue Oct 24, 2017 · 5 comments

Comments

@FabianEckermann
Copy link

FabianEckermann commented Oct 24, 2017

When using a URSP B210 via USB (srslte) we infrequently get the following error message when calling uhd_tx_streamer_send:

T* boost::intrusive_ptr<T>::operator->() const [with T = uhd::transport::managed_send_buffer]: Assertion `px != 0' failed.

We're guessing this could be related to an unhandled timeout in libusb1_zero_copy, but we couldn't verify it yet.

@mbr0wn
Copy link
Contributor

mbr0wn commented Oct 24, 2017

Interesting -- if you can point us to a way to reproduce this, that would certainly be very helpful. Thanks for reporting!

@FabianEckermann
Copy link
Author

We use the latest version of srsLTE with an USRP B210.
When starting the srsenb or srsue the error infrequently occurs. A precise reproduction is not possible from what we inspected so far.

@michael-west
Copy link
Contributor

@FabianEckermann I tried to reproduce the issue by repeatedly starting srsenb with the example configuration, but I was unable to reproduce it.

For us to be able to troubleshoot any further, we need a bit more information. Please provide the output of uhd_config_info --print-all and a stack trace of the failure as well as steps needed to reproduce the failure. Having your srsenb configuration files and host system specifications (especially the USB Host Controller information) might also be helpful.

I don't suspect an unhandled timeout, but it could be an uhandled USB error that is only seen on some systems in very certain circumstances.

@michael-west
Copy link
Contributor

We are closing this because we were unable to reproduce the issue and no additional information has been provided. If the issue persists, please re-open the issue and provide more details on how to reproduce it. Thank you.

@michael-west
Copy link
Contributor

Root cause identified in #171.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants