Bug 116711 - kernel not completing interface initialization when network script finished
Summary: kernel not completing interface initialization when network script finished
Keywords:
Status: CLOSED DUPLICATE of bug 97610
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: initscripts
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-24 16:20 UTC by Joshua Jensen
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:01:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
lspci -v output from the problematic machine (5.26 KB, text/plain)
2004-02-24 16:21 UTC, Joshua Jensen
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.