Package: iperf
Version: 2.0.12+dfsg1-2
Severity: important
Tags: upstream patch

When attempting an iperf run with 24 threads, I either hit a
hang [*] or a bunch of "write failed: Connection reset by peer"
errors [**]. These are both resolved by the following upstream commit:

https://sourceforge.net/p/iperf2/code/ci/4565c2ce318318a8a1d4578bab78c0e03fb49437/

[*]
$ iperf -c 192.168.86.2 -P 24 
^C^Cconnect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
connect failed: Operation now in progress
^C^C^Z
[1]+  Stopped                 iperf -c 192.168.86.2 -P 24
$ bg
[1]+ iperf -c 192.168.86.2 -P 24 &
$ killall -9 iperf
$ fg
-bash: fg: job has terminated
[1]+  Killed                  iperf -c 192.168.86.2 -P 24

[**]
$ iperf -c 192.168.86.2 -P 24 
------------------------------------------------------------
Client connecting to 192.168.86.2, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
write failed: Connection reset by peer
write failed: Connection reset by peer
write failed: Connection reset by peer
write failed: Connection reset by peer
[ 21] local 192.168.86.1 port 47950 connected with 192.168.86.2 port 5001
[ ID] Interval       Transfer     Bandwidth
[ 21]  0.0- 0.0 sec   107 KBytes  0.00 bits/sec
[ 16] local 192.168.86.1 port 47940 connected with 192.168.86.2 port 5001
[ 16]  0.0- 0.0 sec   107 KBytes  0.00 bits/sec
[  4] local 192.168.86.1 port 47914 connected with 192.168.86.2 port 5001
[  8] local 192.168.86.1 port 47918 connected with 192.168.86.2 port 5001
[  3] local 192.168.86.1 port 47916 connected with 192.168.86.2 port 5001
[  5] local 192.168.86.1 port 47920 connected with 192.168.86.2 port 5001
[  6] local 192.168.86.1 port 47922 connected with 192.168.86.2 port 5001
[  7] local 192.168.86.1 port 47924 connected with 192.168.86.2 port 5001
[ 22] local 192.168.86.1 port 47952 connected with 192.168.86.2 port 5001
[  9] local 192.168.86.1 port 47926 connected with 192.168.86.2 port 5001
[ 20] local 192.168.86.1 port 47948 connected with 192.168.86.2 port 5001
[ 26] local 192.168.86.1 port 47960 connected with 192.168.86.2 port 5001
[ 19] local 192.168.86.1 port 47946 connected with 192.168.86.2 port 5001
[ 15] local 192.168.86.1 port 47938 connected with 192.168.86.2 port 5001
[ 15]  0.0- 0.0 sec   107 KBytes  0.00 bits/sec
[ 10] local 192.168.86.1 port 47930 connected with 192.168.86.2 port 5001
[ 25] local 192.168.86.1 port 47958 connected with 192.168.86.2 port 5001
[ 12] local 192.168.86.1 port 47928 connected with 192.168.86.2 port 5001
[ 17] local 192.168.86.1 port 47944 connected with 192.168.86.2 port 5001
[ 14] local 192.168.86.1 port 47936 connected with 192.168.86.2 port 5001
[ 13] local 192.168.86.1 port 47934 connected with 192.168.86.2 port 5001
[ 11] local 192.168.86.1 port 47932 connected with 192.168.86.2 port 5001
[ 11]  0.0- 0.0 sec   107 KBytes  0.00 bits/sec
[ 24] local 192.168.86.1 port 47956 connected with 192.168.86.2 port 5001
[ 23] local 192.168.86.1 port 47954 connected with 192.168.86.2 port 5001
[ 18] local 192.168.86.1 port 47942 connected with 192.168.86.2 port 5001
write failed: Connection reset by peer
write failed: Connection reset by peer
[ 12]  0.0- 0.0 sec   107 KBytes  73.0 Mbits/sec
[ 18]  0.0- 0.0 sec   107 KBytes  73.3 Mbits/sec
[  4]  0.0-10.0 sec  4.19 GBytes  3.60 Gbits/sec
[  8]  0.0-10.0 sec  2.87 GBytes  2.47 Gbits/sec
[  3]  0.0-10.0 sec  2.04 GBytes  1.75 Gbits/sec
[  5]  0.0-10.0 sec  2.00 GBytes  1.72 Gbits/sec
[  6]  0.0-10.0 sec  2.71 GBytes  2.33 Gbits/sec
[  7]  0.0-10.0 sec  4.10 GBytes  3.52 Gbits/sec
[ 22]  0.0-10.0 sec  2.00 GBytes  1.72 Gbits/sec
[  9]  0.0-10.0 sec  2.71 GBytes  2.33 Gbits/sec
[ 20]  0.0-10.0 sec  2.82 GBytes  2.42 Gbits/sec
[ 26]  0.0-10.0 sec  2.71 GBytes  2.32 Gbits/sec
[ 19]  0.0-10.0 sec  4.58 GBytes  3.94 Gbits/sec
[ 10]  0.0-10.0 sec  2.92 GBytes  2.51 Gbits/sec
[ 25]  0.0-10.0 sec  4.15 GBytes  3.57 Gbits/sec
[ 17]  0.0-10.0 sec  2.74 GBytes  2.35 Gbits/sec
[ 14]  0.0-10.0 sec  2.78 GBytes  2.39 Gbits/sec
[ 13]  0.0-10.0 sec  2.00 GBytes  1.72 Gbits/sec
[ 24]  0.0-10.0 sec  2.81 GBytes  2.41 Gbits/sec
[ 23]  0.0-10.0 sec  4.13 GBytes  3.55 Gbits/sec
[SUM]  0.0-10.0 sec  54.3 GBytes  46.6 Gbits/sec


-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.0.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages iperf depends on:
ii  libc6       2.28-10
ii  libgcc1     1:8.3.0-7
ii  libstdc++6  8.3.0-7

iperf recommends no packages.

iperf suggests no packages.

-- no debconf information

  • Bug#930386: hangs and connection resets w/ high thread count dann frazier

Reply via email to