Bug 176334

Summary:	Network startup failure under 1776 and 1777 kernels
Product:	[Fedora] Fedora	Reporter:	Benjmain Youngdahl <angben>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DUPLICATE	QA Contact:	Brock Organ <borgan>
Severity:	high	Docs Contact:
Priority:	medium
Version:	5	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-12-21 15:49:19 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:	177685
Bug Blocks:

Description Benjmain Youngdahl 2005-12-21 15:38:29 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8) Gecko/20051216 Fedora/1.5-3 Firefox/1.5

Description of problem:
Unable to boot with certain kernels.

Version-Release number of selected component (if applicable):
8.19-1

How reproducible:
Always

Steps to Reproduce:
1.  Boot system with 1776 or 1777 kernel


Actual Results:  System hangs with error message when starting eth0.

(I will attach exact error message to this bug as soon I reboot again and copy it down; can't find it in logs.)

Expected Results:  System should succeed at starting up eth0 and continue boot process.


Additional info:

Because it happens as the "network" service starts up, I've assigned this to "initscripts".  I believe this is related to the kernel version as well, as kernel 1773 does not perturb this situation, but 1776 and 1777 do.

I've tried in both permissive and enforcing selinux mode; no difference noted.

Comment 1 Benjmain Youngdahl 2005-12-21 15:47:07 UTC

Determining IP information for eth0... SIOCSIFFLAGS Device or resource busy
SIOCSIFFLAGS Device or resource busy

That's the exact error message.

(It prints the busy message twice, and I realize the first part there is the
standard output, just putting it there for context.)

Comment 2 Benjmain Youngdahl 2005-12-21 15:49:19 UTC


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