[Group.of.nepali.translators] [Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

2018-06-04 Thread dann frazier
Thanks Manoj & Bob - I'll take a look at sponsoring your upload. Do you
mind filing a bug in Debian as well, and linking that bug to this one
using "Also affects distribution/package"? That way we'll know when we
can drop our diff & resync w/ Debian.

** Also affects: iperf (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: iperf (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: iperf (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: iperf (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

Status in iperf package in Ubuntu:
  New
Status in iperf source package in Xenial:
  New
Status in iperf source package in Artful:
  New
Status in iperf source package in Bionic:
  New
Status in iperf source package in Cosmic:
  New

Bug description:
  ubuntu@recht:~$ iperf -c 192.168.121.2 -P10 -w 130k -t 3600
  
  Client connecting to 192.168.121.2, TCP port 5001
  TCP window size:  254 KByte (WARNING: requested  127 KByte)
  
  [ 10] local 192.168.121.3 port 40756 connected with 192.168.121.2 port 5001
  [ 12] local 192.168.121.3 port 40760 connected with 192.168.121.2 port 5001
  [ 11] local 192.168.121.3 port 40758 connected with 192.168.121.2 port 5001
  [  8] local 192.168.121.3 port 40754 connected with 192.168.121.2 port 5001
  [  9] local 192.168.121.3 port 40752 connected with 192.168.121.2 port 5001
  [  7] local 192.168.121.3 port 40750 connected with 192.168.121.2 port 5001
  [  6] local 192.168.121.3 port 40746 connected with 192.168.121.2 port 5001
  [  5] local 192.168.121.3 port 40748 connected with 192.168.121.2 port 5001
  [  3] local 192.168.121.3 port 40744 connected with 192.168.121.2 port 5001
  [  4] local 192.168.121.3 port 40742 connected with 192.168.121.2 port 5001
  Segmentation fault (core dumped)

  Will report more information with gdb attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

2018-06-05 Thread Manoj Iyer
** Bug watch added: Debian Bug tracker #900793
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900793

** Also affects: iperf (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900793
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

Status in iperf package in Ubuntu:
  New
Status in iperf source package in Xenial:
  New
Status in iperf source package in Artful:
  New
Status in iperf source package in Bionic:
  New
Status in iperf source package in Cosmic:
  New
Status in iperf package in Debian:
  Unknown

Bug description:
  ubuntu@recht:~$ iperf -c 192.168.121.2 -P10 -w 130k -t 3600
  
  Client connecting to 192.168.121.2, TCP port 5001
  TCP window size:  254 KByte (WARNING: requested  127 KByte)
  
  [ 10] local 192.168.121.3 port 40756 connected with 192.168.121.2 port 5001
  [ 12] local 192.168.121.3 port 40760 connected with 192.168.121.2 port 5001
  [ 11] local 192.168.121.3 port 40758 connected with 192.168.121.2 port 5001
  [  8] local 192.168.121.3 port 40754 connected with 192.168.121.2 port 5001
  [  9] local 192.168.121.3 port 40752 connected with 192.168.121.2 port 5001
  [  7] local 192.168.121.3 port 40750 connected with 192.168.121.2 port 5001
  [  6] local 192.168.121.3 port 40746 connected with 192.168.121.2 port 5001
  [  5] local 192.168.121.3 port 40748 connected with 192.168.121.2 port 5001
  [  3] local 192.168.121.3 port 40744 connected with 192.168.121.2 port 5001
  [  4] local 192.168.121.3 port 40742 connected with 192.168.121.2 port 5001
  Segmentation fault (core dumped)

  Will report more information with gdb attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

2018-06-06 Thread Launchpad Bug Tracker
This bug was fixed in the package iperf - 2.0.10+dfsg1-1ubuntu1

---
iperf (2.0.10+dfsg1-1ubuntu1) cosmic; urgency=medium

  * fix for: iperf2 long time run on 40Gb/s NIC crashes (LP: #1771283)

 -- Manoj Iyer   Mon, 04 Jun 2018 18:10:31
-0500

** Changed in: iperf (Ubuntu Cosmic)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

Status in iperf package in Ubuntu:
  Fix Released
Status in iperf source package in Xenial:
  New
Status in iperf source package in Artful:
  New
Status in iperf source package in Bionic:
  New
Status in iperf source package in Cosmic:
  Fix Released
Status in iperf package in Debian:
  New

Bug description:
  ubuntu@recht:~$ iperf -c 192.168.121.2 -P10 -w 130k -t 3600
  
  Client connecting to 192.168.121.2, TCP port 5001
  TCP window size:  254 KByte (WARNING: requested  127 KByte)
  
  [ 10] local 192.168.121.3 port 40756 connected with 192.168.121.2 port 5001
  [ 12] local 192.168.121.3 port 40760 connected with 192.168.121.2 port 5001
  [ 11] local 192.168.121.3 port 40758 connected with 192.168.121.2 port 5001
  [  8] local 192.168.121.3 port 40754 connected with 192.168.121.2 port 5001
  [  9] local 192.168.121.3 port 40752 connected with 192.168.121.2 port 5001
  [  7] local 192.168.121.3 port 40750 connected with 192.168.121.2 port 5001
  [  6] local 192.168.121.3 port 40746 connected with 192.168.121.2 port 5001
  [  5] local 192.168.121.3 port 40748 connected with 192.168.121.2 port 5001
  [  3] local 192.168.121.3 port 40744 connected with 192.168.121.2 port 5001
  [  4] local 192.168.121.3 port 40742 connected with 192.168.121.2 port 5001
  Segmentation fault (core dumped)

  Will report more information with gdb attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

2018-07-02 Thread Launchpad Bug Tracker
This bug was fixed in the package iperf - 2.0.10+dfsg1-1ubuntu0.18.04.1

---
iperf (2.0.10+dfsg1-1ubuntu0.18.04.1) bionic; urgency=medium

  * fix for: iperf2 long time run on 40Gb/s NIC crashes (LP: #1771283)

 -- Manoj Iyer   Tue, 05 Jun 2018 11:48:25
-0500

** Changed in: iperf (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

Status in iperf package in Ubuntu:
  Fix Released
Status in iperf source package in Xenial:
  Fix Released
Status in iperf source package in Artful:
  Fix Released
Status in iperf source package in Bionic:
  Fix Released
Status in iperf source package in Cosmic:
  Fix Released
Status in iperf package in Debian:
  New

Bug description:
  [Impact]
  Running iperf2 across 40GB connection for a long period of time causes iperf 
to segfault.

  [Test]
  ubuntu@recht:~$ iperf -c 192.168.121.2 -P10 -w 130k -t 3600
  
  Client connecting to 192.168.121.2, TCP port 5001
  TCP window size:  254 KByte (WARNING: requested  127 KByte)
  
  [ 10] local 192.168.121.3 port 40756 connected with 192.168.121.2 port 5001
  [ 12] local 192.168.121.3 port 40760 connected with 192.168.121.2 port 5001
  [ 11] local 192.168.121.3 port 40758 connected with 192.168.121.2 port 5001
  [  8] local 192.168.121.3 port 40754 connected with 192.168.121.2 port 5001
  [  9] local 192.168.121.3 port 40752 connected with 192.168.121.2 port 5001
  [  7] local 192.168.121.3 port 40750 connected with 192.168.121.2 port 5001
  [  6] local 192.168.121.3 port 40746 connected with 192.168.121.2 port 5001
  [  5] local 192.168.121.3 port 40748 connected with 192.168.121.2 port 5001
  [  3] local 192.168.121.3 port 40744 connected with 192.168.121.2 port 5001
  [  4] local 192.168.121.3 port 40742 connected with 192.168.121.2 port 5001
  Segmentation fault (core dumped)

  [Fix]
  This is fixed latest iperf2
  git clone https://git.code.sf.net/p/iperf2/code

  commit fce3254827eb05fee56aa6a2e9f0d69cbe599a69
  Author: Robert McMahon 
  Date:   Sat Jun 2 11:48:22 2018 -0700

  fix for: iperf2 long time run on 40Gb/s NIC crashes, found ubuntu
  Bug #1771283, reported by Ike Panhc, increase format support to Peta
  as well

  [Regression Potential]
  This patch was tested on ARM64 Cavium ThunderX2 systems and no regressions 
were found.
  iperf calculates the sum of all bytes transferred and prints this sum like 
'Sum: 100Mbytes'. For example if total data transferred was (simplified) 
100,000,000 Bytes, iperf would print Sum: 100 Mbytes. The suffix Mbytes is 
stored in a static array and it uses the number of time it had to divide the 
sum by 1000 to determine the index to that array. iperf only accounted for Sums 
up to GBytes, causing it to segfault on Sums of +TBytes. Currently the patch 
extends this array to Peta Bytes, but you will segfault again if the sum is in 
the order of Exabyte or larger. This might be achievable by using 100G 
connections between server-client (Mellanox 100G nic & switch) and running 
iperf at max throughput for a long long long periods of time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

2018-07-02 Thread Launchpad Bug Tracker
This bug was fixed in the package iperf - 2.0.10+dfsg1-1ubuntu0.17.10.1

---
iperf (2.0.10+dfsg1-1ubuntu0.17.10.1) artful; urgency=medium

  * fix for: iperf2 long time run on 40Gb/s NIC crashes (LP: #1771283)

 -- Manoj Iyer   Tue, 05 Jun 2018 12:01:28
-0500

** Changed in: iperf (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** Changed in: iperf (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

Status in iperf package in Ubuntu:
  Fix Released
Status in iperf source package in Xenial:
  Fix Released
Status in iperf source package in Artful:
  Fix Released
Status in iperf source package in Bionic:
  Fix Released
Status in iperf source package in Cosmic:
  Fix Released
Status in iperf package in Debian:
  New

Bug description:
  [Impact]
  Running iperf2 across 40GB connection for a long period of time causes iperf 
to segfault.

  [Test]
  ubuntu@recht:~$ iperf -c 192.168.121.2 -P10 -w 130k -t 3600
  
  Client connecting to 192.168.121.2, TCP port 5001
  TCP window size:  254 KByte (WARNING: requested  127 KByte)
  
  [ 10] local 192.168.121.3 port 40756 connected with 192.168.121.2 port 5001
  [ 12] local 192.168.121.3 port 40760 connected with 192.168.121.2 port 5001
  [ 11] local 192.168.121.3 port 40758 connected with 192.168.121.2 port 5001
  [  8] local 192.168.121.3 port 40754 connected with 192.168.121.2 port 5001
  [  9] local 192.168.121.3 port 40752 connected with 192.168.121.2 port 5001
  [  7] local 192.168.121.3 port 40750 connected with 192.168.121.2 port 5001
  [  6] local 192.168.121.3 port 40746 connected with 192.168.121.2 port 5001
  [  5] local 192.168.121.3 port 40748 connected with 192.168.121.2 port 5001
  [  3] local 192.168.121.3 port 40744 connected with 192.168.121.2 port 5001
  [  4] local 192.168.121.3 port 40742 connected with 192.168.121.2 port 5001
  Segmentation fault (core dumped)

  [Fix]
  This is fixed latest iperf2
  git clone https://git.code.sf.net/p/iperf2/code

  commit fce3254827eb05fee56aa6a2e9f0d69cbe599a69
  Author: Robert McMahon 
  Date:   Sat Jun 2 11:48:22 2018 -0700

  fix for: iperf2 long time run on 40Gb/s NIC crashes, found ubuntu
  Bug #1771283, reported by Ike Panhc, increase format support to Peta
  as well

  [Regression Potential]
  This patch was tested on ARM64 Cavium ThunderX2 systems and no regressions 
were found.
  iperf calculates the sum of all bytes transferred and prints this sum like 
'Sum: 100Mbytes'. For example if total data transferred was (simplified) 
100,000,000 Bytes, iperf would print Sum: 100 Mbytes. The suffix Mbytes is 
stored in a static array and it uses the number of time it had to divide the 
sum by 1000 to determine the index to that array. iperf only accounted for Sums 
up to GBytes, causing it to segfault on Sums of +TBytes. Currently the patch 
extends this array to Peta Bytes, but you will segfault again if the sum is in 
the order of Exabyte or larger. This might be achievable by using 100G 
connections between server-client (Mellanox 100G nic & switch) and running 
iperf at max throughput for a long long long periods of time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes

2018-11-18 Thread Bug Watch Updater
** Changed in: iperf (Debian)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1771283

Title:
  iperf2 long time run on 40Gb/s NIC crashes

Status in iperf package in Ubuntu:
  Fix Released
Status in iperf source package in Xenial:
  Fix Released
Status in iperf source package in Artful:
  Fix Released
Status in iperf source package in Bionic:
  Fix Released
Status in iperf source package in Cosmic:
  Fix Released
Status in iperf package in Debian:
  Fix Released

Bug description:
  [Impact]
  Running iperf2 across 40GB connection for a long period of time causes iperf 
to segfault.

  [Test]
  ubuntu@recht:~$ iperf -c 192.168.121.2 -P10 -w 130k -t 3600
  
  Client connecting to 192.168.121.2, TCP port 5001
  TCP window size:  254 KByte (WARNING: requested  127 KByte)
  
  [ 10] local 192.168.121.3 port 40756 connected with 192.168.121.2 port 5001
  [ 12] local 192.168.121.3 port 40760 connected with 192.168.121.2 port 5001
  [ 11] local 192.168.121.3 port 40758 connected with 192.168.121.2 port 5001
  [  8] local 192.168.121.3 port 40754 connected with 192.168.121.2 port 5001
  [  9] local 192.168.121.3 port 40752 connected with 192.168.121.2 port 5001
  [  7] local 192.168.121.3 port 40750 connected with 192.168.121.2 port 5001
  [  6] local 192.168.121.3 port 40746 connected with 192.168.121.2 port 5001
  [  5] local 192.168.121.3 port 40748 connected with 192.168.121.2 port 5001
  [  3] local 192.168.121.3 port 40744 connected with 192.168.121.2 port 5001
  [  4] local 192.168.121.3 port 40742 connected with 192.168.121.2 port 5001
  Segmentation fault (core dumped)

  [Fix]
  This is fixed latest iperf2
  git clone https://git.code.sf.net/p/iperf2/code

  commit fce3254827eb05fee56aa6a2e9f0d69cbe599a69
  Author: Robert McMahon 
  Date:   Sat Jun 2 11:48:22 2018 -0700

  fix for: iperf2 long time run on 40Gb/s NIC crashes, found ubuntu
  Bug #1771283, reported by Ike Panhc, increase format support to Peta
  as well

  [Regression Potential]
  This patch was tested on ARM64 Cavium ThunderX2 systems and no regressions 
were found.
  iperf calculates the sum of all bytes transferred and prints this sum like 
'Sum: 100Mbytes'. For example if total data transferred was (simplified) 
100,000,000 Bytes, iperf would print Sum: 100 Mbytes. The suffix Mbytes is 
stored in a static array and it uses the number of time it had to divide the 
sum by 1000 to determine the index to that array. iperf only accounted for Sums 
up to GBytes, causing it to segfault on Sums of +TBytes. Currently the patch 
extends this array to Peta Bytes, but you will segfault again if the sum is in 
the order of Exabyte or larger. This might be achievable by using 100G 
connections between server-client (Mellanox 100G nic & switch) and running 
iperf at max throughput for a long long long periods of time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp