Bridge only working on second netcard - be2net

Bug #1287157 reported by Søren Laursen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

This is reduced bug report for a bug similar to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213887

What we have done is to make a simple network and basic installation af 14.04 daily build from 2014-03-03.

The error is also in 12.04 and later kernels.

If we use the first network card a a bridge:
/etc/network/interfaces:
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto p5p1
iface p5p1 inet manual

auto vlan280
iface vlan280 inet static
      address 10.230.80.26
      netmask 255.255.255.0
      gateway 10.230.80.1
      dns-search 10.230.80.11 10.230.80.12
      bridge_ports p5p1
      bridge_maxwait 0
      bridge_fd 0
      bridge stp_off

auto p5p2
iface p5p2 inet static
      mtu 9000
      address 10.230.92.26
      network 10.230.92.0
      netmask 255.255.255.0
      post-up ifconfig p5p2 txqueuelen 10000

You begin to lose pings and the connection to 10.230.80.26 becomes very unstable. The connection to 10.230.92.26 i running without problems all the time.

We get some messages in syslog vlan280: received packet on p5p1 with own address as source address

If we switch the bridge to the second networkcard the bridge works:
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto p5p2
iface p5p2 inet manual

auto vlan280
iface vlan280 inet static
      address 10.230.80.26
      netmask 255.255.255.0
      gateway 10.230.80.1
      dns-search 10.230.80.11 10.230.80.12
      bridge_ports p5p2
      bridge_maxwait 0
      bridge_fd 0
      bridge stp_off

auto p5p1
iface p5p1 inet static
      mtu 9000
      address 10.230.92.26
      network 10.230.92.0
      netmask 255.255.255.0
      post-up ifconfig p5p1 txqueuelen 10000

A normal network setup does not give any problems at all on p5p1

lsb_release -rd:
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04

lsmod:
Module Size Used by
drbd 323103 0
lru_cache 15442 1 drbd
libcrc32c 12644 1 drbd
bridge 110702 0
stp 12976 1 bridge
llc 14552 2 stp,bridge
intel_rapl 18773 0
x86_pkg_temp_thermal 14162 0
intel_powerclamp 14705 0
coretemp 13435 0
kvm_intel 143060 0
kvm 451519 1 kvm_intel
crct10dif_pclmul 14289 0
crc32_pclmul 13113 0
ghash_clmulni_intel 13259 0
aesni_intel 55624 0
aes_x86_64 17131 1 aesni_intel
lrw 13286 1 aesni_intel
gf128mul 14951 1 lrw
glue_helper 13990 1 aesni_intel
ablk_helper 13597 1 aesni_intel
cryptd 20359 3 ghash_clmulni_intel,aesni_intel,ablk_helper
gpio_ich 13476 0
microcode 23656 0
psmouse 101945 0
serio_raw 13462 0
joydev 17381 0
sb_edac 22344 0
edac_core 62291 1 sb_edac
ioatdma 63447 0
lpc_ich 21080 0
hpilo 17381 0
hpwdt 14242 0
dca 15130 1 ioatdma
ipmi_si 53257 0
acpi_power_meter 18058 0
mac_hid 13205 0
lp 17759 0
parport 42348 1 lp
hid_generic 12548 0
tg3 166442 0
usbhid 52616 0
ptp 18933 1 tg3
hid 106148 2 hid_generic,usbhid
be2net 104514 0
hpsa 67363 2
pps_core 19382 1 ptp

 ethtool -i p5p1
driver: be2net
version: 10.0.600.0u
firmware-version: 4.6.247.5
bus-info: 0000:24:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: no
supports-priv-flags: no

Revision history for this message
John Kim (kotux) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop ISO of the development release - Trusty Tahr. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Søren Laursen (sl-6) wrote :

The link http://www.ubuntu.com/testing/ is 404.

I can see that there are some errors in my copy-and-paste.

It should read:
dns-search foo.com
dns-nameservers 10.230.80.11 10.230.80.12

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc5-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: trusty
Revision history for this message
Søren Laursen (sl-6) wrote :

Testet latest v3.14-rc4 it still exist.

HP had issued a firmware upgrade to the network card, it did not help:
driver: be2net
version: 10.0.600.0u
firmware-version: 4.9.311.20
It did not solve the problem

tags:kernel-bug-exists-upstream

tags: added: kernel-bug-exists-upstream
removed: trusty
Søren Laursen (sl-6)
tags: added: trust
Revision history for this message
Søren Laursen (sl-6) wrote :

Tried the 10.0.800.0 driver from emulex:
http://www.emulex.com/downloads/emulex/drivers/linux/ubuntu/drivers/

on ubuntu 13.04

This did not solve the problem

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

tags: added: trusty
removed: trust
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Søren Laursen (sl-6) wrote :

Submitted bugreport upstream. Verified that the error also exist in Fedora.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.