You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe interesting to now, after a fault like this, the used cpu core to the interrupt-lane (4 of them) will change.
We currently don't know if this issue could also be hardwarerelated or a bug in iperf3.
Steps to Reproduce
Just connect two I226-IT on either the same, or to another system.
start iperf3 over and over again ~
server is started like this in network namespaces:
iperf3 --format m --bind 10.6.1.1 --server --port 5003
the client connets via tcp
It takes some time to appear but after that repeatedly.
Possible Solution
Not found yet..
The text was updated successfully, but these errors were encountered:
It takes some time to appear but after that repeatedly.
I assume that the problem is in the server, not the client. When the problem happens, does it happen immediately when starting the server? When the first test request from a client is received? During the first test? During a later test?
Also, when the problem happens, can you run the server using -d -V (debug and verbose) and send the output?
#Context
Version of iperf3: 3.16 (cJSON 1.7.15)
Hardware:
Operating system (and distribution, if any):
Bug Report
Expected Behavior
No segfault in libcc.so.6
Actual Behavior
Repeatedly
Maybe interesting to now, after a fault like this, the used cpu core to the interrupt-lane (4 of them) will change.
We currently don't know if this issue could also be hardwarerelated or a bug in iperf3.
Steps to Reproduce
Just connect two I226-IT on either the same, or to another system.
start iperf3 over and over again ~
server is started like this in network namespaces:
iperf3 --format m --bind 10.6.1.1 --server --port 5003
the client connets via tcp
It takes some time to appear but after that repeatedly.
Possible Solution
Not found yet..
The text was updated successfully, but these errors were encountered: