Bug 207443

Summary:	Call Trace thrown on screen when network is restarted on bonding
Product:	Red Hat Enterprise Linux 5	Reporter:	Giribabu Bikki <giribabu_bikki>
Component:	kernel	Assignee:	Robert Hentosh <rhentosh>
Status:	CLOSED DUPLICATE	QA Contact:	Brian Brock <bbrock>
Severity:	low	Docs Contact:
Priority:	medium
Version:	5.0	CC:	jfeeney, linville, wwlinuxengineering
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-10-23 19:15:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	200812

Description Giribabu Bikki 2006-09-21 05:15:59 UTC

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


Additional info:

Comment 1 RHEL Program Management 2006-10-12 14:02:45 UTC

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.

Comment 3 jordan hargrave 2006-10-19 14:56:20 UTC

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.

Comment 4 John W. Linville 2006-10-23 19:15:13 UTC


*** This bug has been marked as a duplicate of 210577 ***