Closed dominikheinz closed 3 months ago
A full system reboot did also not resolve the issue.
Logs: gnb-debug.log
sync: external
? do you use an external clock?
sync: external
? do you use an external clock?
I do not, thats a good point. I will change it to sync: internal
and see if that helps.
Also, did you have a chance to check the logs, maybe there is something else, that causes this?
@dominikheinz any update on this issue?
@dominikheinz any update on this issue?
Closed for now. For the future: I believe the issue had to do with the USB Controller being overloaded. After unplugging as many unnecessary devices as I could, especially from other USB3 ports, the issue seemingly went away.
I have the same issue and I am using n310 (so the connection of the radio with the server is not via USB).
==== gNB started ===
Type <h> to view help
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Error: exceeded maximum number of timed out transmissions.
Error: exceeded maximum number of timed out transmissions.
Error: exceeded maximum number of timed out transmissions.
Error: exceeded maximum number of timed out transmissions.
Error: exceeded maximum number of timed out transmissions.
Error: exceeded maximum number of timed out transmissions.
Error: exceeded maximum number of timed out transmissions.
Error: exceeded maximum number of timed out transmissions.
Error: exceeded maximum number of timed out transmissions.
Issue Description
After the GNB starts, a few seconds later, I see
Error: exceeded maximum number of timed out transmissions.
And it appears that the UE can not connect anymore either.Setup Details
Everything default. Ubuntu 22.04 install, system is very powerful (Intel 14900k) so this shouldnt be a performance issue. The HF Frontend is a USRP B210. All The exact same setup worked perfectly fine yesterday, and today, for some reason, I get this error even tho no changes were made.
Expected Behavior
The GNB starts without this error and UEs can connect.
Actual Behaviour
I see this error:
Steps to reproduce the problem
I don't know how it can be reproduced. The error appeared seemingly random.
Additional Information
This is the config I am using: