[Bug 890658] Re: Lost packets when using bonding (mode 6)

Stéphane Graber stgraber at stgraber.org
Fri Feb 3 18:57:50 UTC 2012


Would it be possible for you to test with the current development
release, Precise, currently at Alpha 2?

Quite a bit of work went into trying to solve a set of race conditions
in our userspace network stack in Precise, which may also fix your
issue. If it doesn't, I definitely want to dig into this and see what
needs fixing.

Thanks

** Changed in: ifenslave-2.6 (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifenslave-2.6 in Ubuntu.
https://bugs.launchpad.net/bugs/890658

Title:
  Lost packets when using bonding (mode 6)

Status in “ifenslave-2.6” package in Ubuntu:
  Incomplete

Bug description:
  Description:	Ubuntu 10.04.2 LTS
  Release:	10.04
  Arch: x86_64
  Kernel: 2.6.32-34-generic

  ifenslave-2.6:
    Installed: 1.1.0-14ubuntu2.2
    Candidate: 1.1.0-14ubuntu2.2
    Version table:
   *** 1.1.0-14ubuntu2.2 0
          500 http://fr.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
          100 /var/lib/dpkg/status
       1.1.0-14ubuntu2 0
          500 http://fr.archive.ubuntu.com/ubuntu/ lucid/main Packages

  
  Bonding configured with the following:

  # Bonding channel
  auto bond0
  iface bond0 inet static
          address 192.168.0.1
          network 192.168.0.0
          netmask 255.255.255.0
          post-up ifenslave bond0 eth0 eth1
          slaves eth0 eth1
          bond-mode 6
          bond-miimon 100
          bond-downdelay 200
          bond-updelay 200

  # List all interfaces
  auto eth0
  iface eth0 inet manual

  auto eth1
  iface eth1 inet manual

  I had no issue with the version 1.1.0-14ubuntu2.1 but since I updated
  to 1.1.0-14ubuntu2.2, if I ping anything through this bond0 interface,
  I get between 60 and 90% of packet lost.

  If I remove slave interfaces one by one from the bonding and re-
  enslave them, it solves the issue, but if I restart the computer, the
  issue happens again.

  If I downgrade to 1.1.0-14ubuntu2.1, I cannot reproduce the issue.

  I could confirm this behaviour with various Dell Poweredge (t710,
  r515) systems using different network interfaces numbers (from 2 to 8)
  and vendors (Broadcom, Intel).

  Best regards and thanks for any help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/890658/+subscriptions




More information about the foundations-bugs mailing list