Bug 116711

Summary: kernel not completing interface initialization when network script finished
Product: Red Hat Enterprise Linux 3 Reporter: Joshua Jensen <joshua>
Component: initscriptsAssignee: Arjan van de Ven <arjanv>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: riel
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-02-21 19:01:37 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:
Attachments:
Description Flags
lspci -v output from the problematic machine none

Description Joshua Jensen 2004-02-24 16:20:29 UTC 
Description of problem:

The problem is that when the network script initializes the cards, the
actual initialization of the cards isn't yet finished by the time the
netfs script runs.  A bad work-around is to rig the random script
(which runs after the network but before the netfs script) to simply
sleep for 10 seconds.  This works well, isn't pretty.  Shouldn't the
kernel initialize the driver and card immediately?


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

RHEL3 AS with all updates


How reproducible:

tg3 driver being used for two NICs


Additional info:

lspci -v output attached
Comment 1 Joshua Jensen 2004-02-24 16:21:12 UTC 
Created attachment 97996 [details]
lspci -v output from the problematic machine

lspci -v output from the problematic machine
Comment 2 Joshua Jensen 2004-02-26 17:33:28 UTC 
This is causing BIG problems on Oracle servers.... nfs mounts don't
mount when the machine is rebooted.  Please address!
Comment 3 Bill Nottingham 2004-02-26 21:00:11 UTC 

*** This bug has been marked as a duplicate of 97610 ***
Comment 4 Red Hat Bugzilla 2006-02-21 19:01:37 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.