*** This bug is a duplicate of bug 1160490 ***
https://bugs.launchpad.net/bugs/1160490
@alexlist You can check the upstart logs for more on the cause of that.
For the key issue described in this bug (interfaces not coming up at
all) that does appear to be fixed.
** This bug has been marked
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = khuanglim (khuang0411)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can reproduce the delay problem on Trusty.
machine is pingable after around 8s, which means that bonding, vlans and
bridges all work.
However, startup is delayed by ~120s for unknown reasons. After that,
startup resumes and all services come up.
** Attachment added: dmesg
** Attachment added: /etc/network/interfaces
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996369/+attachment/3954681/+files/interfaces
** Also affects: linux (Ubuntu Trusty)
Importance: High
Status: Incomplete
** Changed in: linux (Ubuntu Trusty)
Status: Incomplete =
We can confirm similar issues with Precise. However, testing a default
Precise 12.04.3 installation with any generic Quantal or Raring LTS
kernel seems to work fine.
Tests preformed:
Continues looping boot using a similar script as mentioned by Chris J Arges.
Counted amount of successful boots -
Unfortunately I cannot test for this bug any longer. I no longer have
access to a switch with aggregation support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Title:
bond slave interface
Given the number of bugs that the Kernel Team receives during any
development cycle it is impossible for us to review them all. Therefore,
we occasionally resort to using automated bots to request further
testing. This is such a request.
We are approaching release and would like to confirm if
** Tags added: regression-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Title:
bond slave interface sometimes does not come up on boot
To manage notifications about this bug go
** Tags added: bios-outdated-2013.07.02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Title:
bond slave interface sometimes does not come up on boot
To manage notifications about this bug
I believe this issue is related to bug 1160490.
I have test ifupdown packages there that may eliminate a race condition based
on an upstream patch. Please give them a test and provide feedback. This solved
my issue in #35.
--
You received this bug notification because you are a member of
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Title:
bond slave interface sometimes does not come up on boot
To manage notifications about this bug go to:
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Saucy)
** Tags removed: kernel-da-key
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Title:
bond slave interface sometimes does not come up on boot
To manage notifications
** Changed in: linux (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Title:
bond slave interface sometimes does not come up on boot
To manage
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Title:
bond slave interface sometimes does not come up on boot
To manage notifications about this bug go to:
I've been able to reproduce a similar issue.
To test:
1) Create a VM with the latest image, and add 12 network interfaces.
2) Use the attached interfaces.lp996369
3) Add something like this to rc.local to reproduce the issue:
sleep 60
if [ `ifconfig | grep eth | wc -l` = 12 ]; then
echo
I am also experiencing issues on reboot. Secondary iP's won't come up
even though I can see then in ifconfig. I have to do service networking
restart after a reboot to get things working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Have had to make a few more adjustments. I realized the above still
wasn't putting it into aggregated mode (cat /proc/net/bonding/bond0),
and one of the links that was down was showing as being up.
Please find the new updates attached, and ignore all my other previous
files.
** Attachment
Updated interfaces file
** Attachment added: Updated interfaces file (/etc/network/interfaces)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996369/+attachment/3431345/+files/interfaces
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Updated /etc/modules file
This file is required so that the bonding driver gets preloaded, before
the networking subsystem starts up, and to make sure that the bonding
strategy chosen is actually applied.
** Attachment added: /etc/modules (use this instead of
/etc/modprobe.d/bonding.conf)
And, finally if you're using jumbo frames, you'll want to apply jumbo
frames for ipv6 as well (not sure if this is the recommended method, or
not), but here's my /etc/sysctl.conf as well.
** Attachment added: /etc/sysctl.conf
Is there anything else I need to advance the status of this ticket?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Title:
bond slave interface sometimes does not come up on boot
To manage
Problem solved.
It appears the way in which ifenslave is invoked has changed, and most
of the documentation on the net on how to configure it doesn't work
anymore.
Step by step instructions for getting it working are at the URL,
** Changed in: linux (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Title:
bond slave interface sometimes does not come up on boot
To manage
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Title:
bond slave interface sometimes does not come up on boot
To manage
Fwiw, our interfaces file is as follows:
auto lo
iface lo inet loopback
auto bond0 bond0:0 bond0:1
auto gb0
# Set up BONDed ports (link aggregation)
iface bond0 inet static
address 10.0.0.49
gateway 10.0.0.5
netmask 255.255.0.0
bond-slaves c10gb0 c10gb1
# LACP configuration
bond_mode
Upgrade to kernel 3.7.0-999.201210220405_amd64 doesn't fix anything.
The extreme delay of startup of the bonded interfaces is still there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Title:
Also, when it's in this state, the module 'bonding' is loaded, and when
I issue the command 'sudo ifenslave bond0 c10gb0 c10gb1', it reports
that c10gb0 and c10gb1 are already slaves.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If I wait long enough (2 minutes to 6 minutes), the interfaces will
eventually come up. If I issue a sudo /etc/init.d/networking restart
command, they'll come up as soon as the command has finished executing.
So, it seems maybe there's something getting locked up during startup,
because of a
Also, fwiw, the mac addresses of c10gb0 and c10gb1 have been changed to
reflect the mac address of bond0. So, there's definitely some bonding
of some sort happening. It's just not being reflected in bond0:0 and
bond0:1 showing up.
--
You received this bug notification because you are a member
I will be installing the latest mainline kernel on one of the machines
where we're having this problem this afternoon to see if it fixes the
problem. (We're having this problem on at least 7 machines, currently.)
If the latest mainline kernel fixes the problem, I will try the latest
stable
FWIW, all of the machines where we're running into this problem are
running the driver code as downloaded from Intel.com for both the Intel
1GbE drivers and the 10GbE drivers. The bonded interfaces are on a dual
port 10GbE Intel adapter.
The machines are not connected to the Internet, so I
Btw, this also affects the package ifenslave-2.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Title:
bond slave interface sometimes does not come up on boot
To manage notifications about
I just thought I'd point out that this problem occurs in 10.04.4 as
well.
What happens is not that the other interfaces don't come up, but that
they're taking an extended period of time to come up (sometimes as much
as 5 or 6 minutes for the :0 and :1 interfaces to come up.)
--
You received
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Just though I would add a comment that I am also seeing this behaviour. It
(might) be related to having a post-up command attached to the ethernet
configuration. Here is my interfaces file:
xfers ~ # cat /etc/network/interfaces
# This file describes the network interfaces available on your
Do you know if this issue happened in a previous version of Ubuntu, or
is this a new issue?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.4kernel[1] (Not a kernel in the daily directory). Once
** Package changed: ubuntu = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996369
Title:
bond slave interface sometimes does not come up on boot
To manage notifications about this
apport information
** Tags added: apport-collected
** Description changed:
bug report:
Hi guys,
I'm running ubuntu12.04 server on a HP DL380G7.
server01 ~ # lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04
I've got 2 ethernet cards with 4x 10G interfaces.
39 matches
Mail list logo
