Red Hat Bugzilla – Bug 84845
eth10 not initialized on boot
Last modified: 2014-03-16 22:34:44 EDT
Description of problem:
At boot time, only eth0-9 are initialized. eth10 is available and exists,
but is not initialized. When run from the command line after system has
booted up, '/etc/init.d/network restart' finds all 11 interfaces. This
appears to be indepdendent of which card corresponds to which interface.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install > 10 network interfaces in a system. Verify that
'/etc/init.d/network start' will in fact start them all.
3. Watch startup messages; notice that only eth[0-9] are configured.
4. After boot, restart networking manually; watch eth10 be configured.
eth10 is not configured on boot, but is afterwards.
All interfaces are configured at boot time.
It's not easy being green.
It's been a couple of weeks-- has anyone taken a look at this bug yet?
Not yet, no.
ISSUE TRACKER 26386 opened as sev 1.
Note that this is at most a sev 2 as indicated in the Bugzilla.
Is this at all related to 98209 (I don't have such a machine immediately
Glen provided two tulip (quad-port 10/100 EN) cards for Bill Nottingham to test
with. Passing cards to Bill.
HP-IPF SAYS MUSTFIX BUG FOR UPDATE3. They have big hardware with more than 10
NICs and need this fixed. Suggest we add blocker bug 87937 but this was
clarified this week so need ruling from Chris/Tim to add blocker. HP provided
hardware to test which I passed to notting.
Works for me with initscripts-6.47.3-1.
I'm going to assume that this is related to bug 98209; it's the only
relevant change that could have caused this to start working.
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.