[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2014-12-18 Thread khuanglim
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Precise:
  Confirmed
Status in linux source package in Quantal:
  Won't Fix
Status in linux source package in Raring:
  Won't Fix
Status in linux source package in Saucy:
  Won't Fix
Status in linux source package in Trusty:
  Confirmed

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame:0
TX packets:1333 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:102784 (102.7 KB)  TX bytes:102784 (102.7 KB)

  vlan888   

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2014-01-22 Thread Alexander List
** 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 = New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Incomplete
Status in “linux” source package in Trusty:
  Confirmed

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame:0
TX 

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2014-01-22 Thread Alexander List
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
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996369/+attachment/3954680/+files/dmesg

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Incomplete
Status in “linux” source package in Trusty:
  Confirmed

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX 

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2013-10-21 Thread Metin de Vreugd
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 - working bond0 with both slaves up - with 
different kernels.

Symptoms after boot:
- Bond0 down with no slaves
- Bond0 comes up with only 1 slave
- Bond0 comes up with 2 slaves with 1 interface marked down

Hardware:
Dell M610-II
01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709S Gigabit 
Ethernet (rev 20)
01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709S Gigabit 
Ethernet (rev 20)

Network configuration:
root@test:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual
  bond-master bond0
  bond-primary eth0 eth1

auto eth1
iface eth1 inet manual
  bond-master bond0
  bond-primary eth0 eth1

auto bond0
iface bond0 inet static
  address 10.1.1.2
  netmask 255.255.255.0
  broadcast 10.1.1.255
  gateway 10.1.1.1
  bond_arp_validate 3
  bond_mode active-backup
  bond_arp_interval 200
  bond_arp_ip_target 10.1.1.1
  bond_slaves none

root@test:~# cat /etc/modprobe.d/bonding.conf
alias bond0 bonding
options bonding mode=1 arp_interval=200 arp_ip_target=10.1.1.1

Test results:
Ubuntu 12.04.3 LTS with linux-image-3.2.0-54-generic (3.2.0-54.82) - Failed 
several boots with the listed symptoms
Ubuntu 12.04.3 LTS with linux-image-3.5.0-41-generic (3.5.0-41.64~precise1) - 
300+ boots
Ubuntu 12.04.3 LTS with linux-image-3.8.0-31-generic (3.8.0-31.46~precise1) - 
300+ boots

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Incomplete
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Incomplete

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link 

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2013-09-21 Thread Daniel Lynes
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Incomplete
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Incomplete

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame:0
TX packets:1333 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:102784 (102.7 KB)  TX bytes:102784 (102.7 KB)

  vlan888   Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet addr:1.1.0.50 

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2013-09-02 Thread Christopher M. Penalver
** Tags added: regression-potential

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Confirmed

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame:0
TX packets:1333 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:102784 (102.7 KB)  TX bytes:102784 (102.7 KB)

  vlan888   Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet addr:1.1.0.50  Bcast:1.1.0.63  Mask:255.255.255.240
inet6 addr: 

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2013-08-24 Thread Christopher M. Penalver
** Tags added: bios-outdated-2013.07.02

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Confirmed

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame:0
TX packets:1333 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:102784 (102.7 KB)  TX bytes:102784 (102.7 KB)

  vlan888   Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet addr:1.1.0.50  Bcast:1.1.0.63  Mask:255.255.255.240
inet6 addr: 

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2013-08-21 Thread Chris J Arges
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Confirmed

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame:0
TX packets:1333 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:102784 (102.7 KB)  TX 

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2013-08-20 Thread Joseph Salisbury
** Tags removed: kernel-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Confirmed

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame:0
TX packets:1333 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:102784 (102.7 KB)  TX bytes:102784 (102.7 KB)

  vlan888   Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet addr:1.1.0.50  Bcast:1.1.0.63  Mask:255.255.255.240
inet6 addr: ::::11/124 

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2013-08-13 Thread Joseph Salisbury
** 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)
   Importance: High
   Status: Confirmed

** Changed in: linux (Ubuntu Raring)
   Status: New = Confirmed

** Changed in: linux (Ubuntu Quantal)
   Status: New = Confirmed

** Changed in: linux (Ubuntu Precise)
   Status: New = Confirmed

** Changed in: linux (Ubuntu Raring)
   Importance: Undecided = High

** Changed in: linux (Ubuntu Quantal)
   Importance: Undecided = High

** Changed in: linux (Ubuntu Precise)
   Importance: Undecided = High

** Tags added: quantal raring saucy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “linux” source package in Saucy:
  Confirmed

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2013-08-09 Thread Chris J Arges
** Tags removed: kernel-da-key
** Tags added: kernel-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame:0
TX packets:1333 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:102784 (102.7 KB)  TX bytes:102784 (102.7 KB)

  vlan888   Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet addr:1.1.0.50  Bcast:1.1.0.63  Mask:255.255.255.240
inet6 addr: ::::11/124 Scope:Global
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:168250 errors:0 dropped:0 overruns:0 

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2013-08-09 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Medium = High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame:0
TX packets:1333 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:102784 (102.7 KB)  TX bytes:102784 (102.7 KB)

  vlan888   Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet addr:1.1.0.50  Bcast:1.1.0.63  Mask:255.255.255.240
inet6 addr: ::::11/124 Scope:Global
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:168250 errors:0 dropped:0 overruns:0 

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2013-08-06 Thread Chris J Arges
** Tags added: kernel-da-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame:0
TX packets:1333 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:102784 (102.7 KB)  TX bytes:102784 (102.7 KB)

  vlan888   Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet addr:1.1.0.50  Bcast:1.1.0.63  Mask:255.255.255.240
inet6 addr: ::::11/124 Scope:Global
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:168250 errors:0 dropped:0 overruns:0 frame:0
TX 

[Kernel-packages] [Bug 996369] Re: bond slave interface sometimes does not come up on boot

2013-08-06 Thread Chris J Arges
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 Everything is A-ok!
 reboot
else
 echo We have a problem.
fi
4) once the machine quits rebooting you will eventually find the one of the 
interfaces did not come up.

** Attachment added: interfaces.lp996369
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996369/+attachment/3762211/+files/interfaces.lp996369

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996369

Title:
  bond slave interface sometimes does not come up on boot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  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.
  I've got a bond on 4x10G where only eth4 and eth6 are patched.

  server01 ~ # ethtool -i eth4
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :0e:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  server01 ~ # ethtool -i eth6
  driver: be2net
  version: 4.0.100u
  firmware-version: 4.0.360.15
  bus-info: :15:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no

  After a reboot I expect to see a bond0 interface with 2 RUNNING SLAVE
  interfaces.

  However, sometimes I only see 1 interface coming up in the bond after
  a reboot and when I manually bring the other interface up (ifconfig
  eth6 up) it works:

  # cat /proc/net/bonding/bond0 
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0
  Aggregator selection policy (ad_select): stable
  Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 33
Partner Key: 32773
Partner Mac Address: 00:23:04:ee:be:01

  Slave Interface: eth6
  MII Status: down   SHOULD BE UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 1
  Permanent HW addr: 00:9c:02:3c:c9:70
  Aggregator ID: 1
  Slave queue ID: 0

  Slave Interface: eth4
  MII Status: up ONLY INTERFACE THAT IS UP
  Speed: 1 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:98
  Aggregator ID: 2
  Slave queue ID: 0

  Slave Interface: eth7
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:c9:74
  Aggregator ID: 3
  Slave queue ID: 0

  Slave Interface: eth5
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: 00:9c:02:3c:99:9c
  Aggregator ID: 4
  Slave queue ID: 0

  server01 ~ # ifconfig
  bond0 Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
inet6 addr: fe80::29c:2ff:fe3c:c970/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:54 overruns:0 frame:0
TX packets:1236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:18435358 (18.4 MB)  TX bytes:174727 (174.7 KB)

  eth4  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:169071 errors:0 dropped:45 overruns:0 frame:0
TX packets:1235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:18435358 (18.4 MB)  TX bytes:174637 (174.6 KB)

  eth5  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  eth7  Link encap:Ethernet  HWaddr 00:9c:02:3c:c9:70  
UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:1333 errors:0 dropped:0 overruns:0 frame:0