Red Hat Bugzilla – Bug 207443
Call Trace thrown on screen when network is restarted on bonding
Last modified: 2007-11-30 17:07:34 EST
Description of problem:When bonding is started on RHEL5 Beta1, Call traces are
thrown on the screen. But the bond works fine. The failover also happens
successfully. This is seen on mode=1 and mode=6.
Version-Release number of selected component (if applicable):RHEL5-b1
How reproducible:evrytime network restart with bonding
Steps to Reproduce:
1.Install RHEL5 B1
2.Create the Bond with mode=6
3.Restart the network services.
4.Call trace are thrown on the screen.
Actual results:call traces are thrown on the screen
Expected results:no call traces are expected on the console
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux release. Product Management has requested further review
of this request by Red Hat Engineering. This request is not yet committed for
inclusion in release.
The bonding drivers will need to run their monitoring threads to run in
sleepable context. The way to do this is by using workqueues. However, all
spinlocks/read/write locks that may be called by the monitoring threads must
be changed to use the _bh forms.
*** This bug has been marked as a duplicate of 210577 ***