Regression: Kernel Panic with bond0 & br0

[Robstarusa]

When using 2 intel pro/1000 nics that are bonding and adding them to a bridge, My new (entirely updated) jaunty box kernel panics at startup. I get the same error on a Precision 690 as well as an HP DL360 G6.

This worked perfectly in intrepid!!
========================================
more /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto bond0
  iface bond0 inet static
  address 10.1.13.163
  netmask 255.255.255.0
  gateway 10.1.13.1
  post-up ifenslave bond0 eth1 eth2
  pre-down ifenslave -d bond0 eth1 eth2

auto br0
   iface br0 inet static
   address 10.1.13.163
   netmask 255.255.255.0
   gateway 10.1.13.1
   broadcast 10.1.13.255
   network 10.1.13.0
   dns-servers 10.1.2.11 10.1.2.12 10.0.2.11
   bridge_ports bond0
   postdown brctl delbr br0

[Schorschi (schorschi)]

Actually this happened for me on 8.10, and it happens with broadcom NICs as well. Given this happens on 9.04 as well, and bridged bonds are key to KVM use, this needs to be upped in the priority queue or address sooner than later. VMware implements true layer-2 compliant virtual switches, maybe someone in the KVM community or Ubuntu community should consider this as an option.

[Andreas Moog (ampelbein)]

Thanks for your report. I changed the package to linux, so that a kernel-developer can see what information he needs from you. For now, please run the command apport-collect -p linux-image-`uname -r` <bug#> , which will include necessary information automatically.

[Robstarusa (rob-naseca)]

Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: linux-image-2.6.28-11-server 2.6.28-11.42
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Uname: Linux 2.6.28-11-server x86_64
UserGroups:

[Robstarusa (rob-naseca)]

Architecture: amd64
DistroRelease: Ubuntu 9.04
HalComputerInfo: Error: [Errno 2] No such file or directory
HibernationDevice: RESUME=UUID=7991553e-2202-48e0-b4b4-fd762b56a23f
Package: linux-image-2.6.28-11-server 2.6.28-11.42
PackageArchitecture: amd64
ProcCmdLine: root=UUID=439f2822-2bdb-4132-900b-bea7dcfc5d10 ro quiet splash ramdisk_size=4194304
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.42-server
Uname: Linux 2.6.28-11-server x86_64
UserGroups:

[Robstarusa (rob-naseca)]

I tried this several times but apport-collect keeps crashing...

Logging into Launchpad...
Downloading bug...
Bug title: Regression: Kernel Panic with bond0 & br0
Collecting apport information for source package linux-image-2.6.28-11-server...
Uploading additional information to Launchpad bug...
   short text data...
   attachment: BootDmesg.gz...
Traceback (most recent call last):
  File "/usr/bin/apport-collect", line 173, in <module>
    upload(report, bug)
  File "/usr/bin/apport-collect", line 97, in upload
    filename=part.get_filename(), is_patch=False)
  File "/usr/lib/python2.6/dist-packages/launchpadlib/resource.py", line 337, in __call__
    args[key] = simplejson.dumps(value, cls=DatetimeJSONEncoder)
  File "/var/lib/python-support/python2.6/simplejson/__init__.py", line 243, in dumps
    **kw).encode(obj)
  File "/var/lib/python-support/python2.6/simplejson/encoder.py", line 360, in encode
    return encode_basestring_ascii(o)
UnicodeDecodeError: 'utf8' codec can't decode byte 0x8b in position 1: unexpected code byte

[Robstarusa (rob-naseca)]

Schorschi:

Are you having the same bnx2 problems as me ?

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/366177

[Davíð Steinn Geirsson (david-dsg)]

Architecture: amd64
Dependencies:

DistroRelease: Ubuntu 9.04
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_AU.UTF-8
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Davíð Steinn Geirsson (david-dsg)]

I am seeing the same problem bridging the e1000e ethernet and IWL4965AGN wireless cards on my laptop. This forces me to use NetworkManager, a very suboptimal solution. For me this is an important issue. I am running jaunty, fully updated as of 12/may 2009.

[Jeremy Foshee (jeremyfoshee)]

Hi Robstarusa,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 366179

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]