Red Hat Bugzilla – Bug 235332
xen kernel reports "BUG" when enslaving NICs to bond
Last modified: 2008-02-07 23:26:23 EST
Description of problem:
Hi, all fc6 kernels (now kernel-xen-2.6.20-1.2933.fc6) report BUG and produce
stack trace when bonding interface is started (resp. interface is enslaved in bond)
Version-Release number of selected component (if applicable):
FC6 lates updates
Steps to Reproduce:
1.create bond configuration (I use ALB but this has no effect) for NICs which
are not "renamed" during xend startup
2. boot xen kernel or execute "ifup bond0"
3. The "BUG" and call trace messages will appear in /var/log/messages
4. the system continues to work without problem
BUG" and call trace messages will appear in /var/log/messages
No problem reported
The problem appears during manipulation of enslaved devices, eg. adding or
removing, not by loading the bonding module
Created attachment 151739 [details]
/var/log/messages from system boot
This is an upstream bonding issue (MAC changes must be moved to process context)
which is not specific to Xen.
Well, the error does not appear if non-xen kernel is booted. Also the ALB mode
of bonding should not move/change mac addresses, right?
If you boot the xen kernel, then the xen userspace detects this and does
different things with bridging setup. So booting xen could easily be tickling
an existing core bug; that doesn't mean that the bug itself is in xen.
The upstream bonding maintainer has recognised this problem and is working on a fix:
(This is a mass-update to all current FC6 kernel bugs in NEW state)
I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug, however this version of Fedora is no longer
Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.
Thanks for using Fedora!
Per the previous comment in this bug, I am closing it as INSUFFICIENT_DATA,
since no information has been lodged for over 30 days.
Please re-open this bug or file a new one if you can provide the requested data,
and thanks for filing the original report!