Closed davwheat closed 2 years ago
Hey,
hard to say. The segfault seems in the srsenb::sched::ue_rem
though, not when handling the UE caps. Can you share the workload and under what situation it happens. Right from the start? After a while?
Sorry about the delay in getting back to you.
I've recently swapped out my RF-customised Lubuntu distro with a stock Ubuntu 20.04 install and haven't noticed any issues since, but I've also made some code changes.
At the moment, I'm instead trying to work out why srsRAN seems to not be sending signalling reliably, but that's in my attempts to rewrite the native bladeRF driver to work with 2x2 MIMO since the SoapySDR has a number of issues when attempting to run the bladeRF as reported in #504 and #552. That'd be a different issue, though.
I'll close this, but will come back if I still encounter issues.
Issue Description
Hey! I'm trying to customise srsRAN to send custom UE capability requests to determine the carrier aggregation capabilities of various LTE/NR devices.
I've managed to do so, to the point where COTS UEs are reliably interpreting and responding to the requests, but at some point afterwards, srsRAN encounters a segmentation fault, which I assume is due to the large capability message from the UE.
Where could I go about fixing this? Presumably by increasing the size of some buffer somewhere within the source of srsRAN, but I'm not even sure where to look.
If you'd like to see the changes I have made: https://github.com/srsran/srsRAN/compare/master...davwheat:srsRAN-22.04
Setup Details
[Specify details of the test setup. This would help us reproduce the problem reliably] e.g. Network configuration, Operation System, Hardware, RF front-end, library and driver versions
Error