Bug 436957

Summary: network does not start automatic at startup in kernel 2.6.24.3-12.f8
Product: [Fedora] Fedora Reporter: J.Jansen <joukj>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 8   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-03-12 19:53:09 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:

Description J.Jansen 2008-03-11 11:58:56 UTC 
Description of problem:
after upgrading to kernel 2.6.24.3-12 network does not start at boot. Manula
start is still possible (Looks like a variation on bug #436583, but not exactly
the same). Restarting in a 2.6.23 kernel still works as expected.

Version-Release number of selected component (if applicable):
2.6.24.3-12.f8

How reproducible:
Only on 2 (hard-ware identical machines)

Steps to Reproduce:
1.upgrade the kernel
2.reboot
3.
  
Actual results:
network is disabled on the machine and has to be started manually

Expected results:
automatic network start at boot

Additional info:
The machines have both 2 ethernet cards of which only one is connected:
  -3COM 3c905C (connected)
   -intel 82054EM (not connected to the internet)
When I boot in 2.6.24 the enabling of the eth-device is skipped (so no error
message) I have enable eth0 manually, which is as the system tells me the
non-connected intel card. This looks weird to me.
Comment 1 Chuck Ebbert 2008-03-12 19:53:09 UTC 

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