802.3ad interface bonding fails if started too early
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifenslave-2.6 (Debian) |
Fix Released
|
Unknown
|
|||
ifenslave-2.6 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Lucid |
Fix Released
|
Medium
|
Stéphane Graber |
Bug Description
Impact: see original report below
How the patch fixes it: pre-up sets up master before attempting to enslave and setup slaves
Patch: https:/
Reproducing: http://
Regression potential: none known
== Original report ==
802.3ad bonding configurations that formerly worked on jaunty are now failing on startup under karmic. After the system has started, restarting networking will bring the bond up correctly. This only applies to bond_mode 4 / 802.3ad, I've tested that switching to bond_mode 0 corrects the issue, and other users experiencing this bug all were using bond_mode 4 as well.
dmesg output fills with "bonding: bond0: Warning: Found an uninitialized port", even after the system starts up and the port should be "initialized"
It appears to occur on multiple drivers (bnx2, e1000 confirmed).
One initially wants to blame the startup ordering due to the switch to upstart, but I believe it is an edge case that hasn't been seen before because we haven't been starting up so quickly that the hardware hasn't had time to fully initialized.
Configuration and output from multiple users is in this thread:
http://
Related branches
description: | updated |
description: | updated |
affects: | ubuntu → linux (Ubuntu) |
tags: | added: kernel-series-unknown |
tags: |
added: karmic removed: kernel-series-unknown |
affects: | linux (Ubuntu) → ifenslave-2.6 (Ubuntu) |
Changed in ifenslave-2.6 (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in ifenslave-2.6 (Ubuntu Lucid): | |
status: | New → Triaged |
importance: | Undecided → Medium |
description: | updated |
Changed in ifenslave-2.6 (Ubuntu Lucid): | |
assignee: | nobody → Neil Wilson (neil-aldur) |
Changed in ifenslave-2.6 (Ubuntu Lucid): | |
assignee: | Neil Wilson (neil-aldur) → nobody |
status: | Triaged → Incomplete |
Changed in ifenslave-2.6 (Ubuntu Lucid): | |
assignee: | Steve Langasek (vorlon) → Stéphane Graber (stgraber) |
tags: | added: verification-done |
Changed in ifenslave-2.6 (Debian): | |
status: | Unknown → Fix Released |
I'm also seeing this with e1000e driver on an intel s5000psl motherboard
iface bond0 inet dhcp
bond-lacp- rate fast
bond-xmit_ hash_policy layer2+3
slaves eth0 eth1
bond-mode 4
bond-miimon 10
after boot up bonding/ bond0 has
/proc/net/
MII Status: down
i can bring the bond up if i do
sudo ifdown bond0; sudo ifup bond0
i tried playing with the bonding updelay, just for kicks, but no change
04:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)
Capabilities: [c8] Power Management version 2
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting <?>
Subsystem: Intel Corporation Device 3476
Flags: bus master, fast devsel, latency 0, IRQ 57
Memory at b8820000 (32-bit, non-prefetchable) [size=128K]
Memory at b8400000 (32-bit, non-prefetchable) [size=4M]
I/O ports at 3020 [size=32]
Kernel driver in use: e1000e
Kernel modules: e1000e
04:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)
Capabilities: [c8] Power Management version 2
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting <?>
Subsystem: Intel Corporation Device 3476
Flags: bus master, fast devsel, latency 0, IRQ 58
Memory at b8800000 (32-bit, non-prefetchable) [size=128K]
Memory at b8000000 (32-bit, non-prefetchable) [size=4M]
I/O ports at 3000 [size=32]
Kernel driver in use: e1000e
Kernel modules: e1000e