Bug 491387 - PXE Kickstart using RHEL5 U2 x86_64 to Sun X4100 (NIC Intel e1000 driver) fails to acquire an IP via dhcp after loading the initrd
Summary: PXE Kickstart using RHEL5 U2 x86_64 to Sun X4100 (NIC Intel e1000 driver) fai...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda
Version: 5.2
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-20 18:05 UTC by Ahmed Taha
Modified: 2011-07-27 17:21 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-27 17:21:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Abnormal Exit error after static network config fails (55.57 KB, image/png)
2009-03-20 18:11 UTC, Ahmed Taha
no flags Details
Ctrl+Alt+F4 Log During eth0 failing to acquire an IP via dhcp (131.84 KB, image/png)
2009-03-20 18:17 UTC, Ahmed Taha
no flags Details
Ctrl+Alt+F3 During eth0 failing to acquire an IP via DHCP (136.12 KB, image/png)
2009-03-20 18:19 UTC, Ahmed Taha
no flags Details

Description Ahmed Taha 2009-03-20 18:05:50 UTC
Description of problem:

PXE Kickstart using RHEL5 U2 x86_64 to Sun X4100 (NIC Intel e1000 driver) fails to acquire an IP via dhcp after loading the initrd. 

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

RHEL5 U2 

How reproducible: Always


Steps to Reproduce:
1. PXE boot X4100 Sun Server from the vmlinuz and initrd.img of RHEL5 U2 x86_64. At the PXE boot menu select the distribution (RHEL5 U2) configured in /tftpboot/pxelinux.cfg/default file to kickstart the Sun Server. The anaconda network configuration dialogue will repeatedly prompt for IP info unable to acquire an IP via the dhcp broadcast from the kickstart server. 
  
Actual results:

Kickstarting a Sun X4100 x86_64 with RHEL5 U2 fails.


Expected results:

Kickstarting a Sun X4100 x86_64 with RHEL5 U2 should succeed.

Additional info:

Some of the work-around solutions that I have tried so far are the following:

1- Appending nicdelay=30 linksleep=10 to the initrd boot line

2- Using a custom initrd that does not have the e1000e module in it (only contains the e1000 module necessary for the Intel Card)

3- Static network configuration using a static IP .. which brings a different error message (uploaded image sigsegv.png) and exits abnormally.

Comment 1 Ahmed Taha 2009-03-20 18:11:21 UTC
Created attachment 336095 [details]
Abnormal Exit error after static network config fails

Comment 2 Ahmed Taha 2009-03-20 18:17:58 UTC
Created attachment 336096 [details]
Ctrl+Alt+F4 Log During eth0 failing to acquire an IP via dhcp

Comment 3 Ahmed Taha 2009-03-20 18:19:00 UTC
Created attachment 336098 [details]
Ctrl+Alt+F3 During eth0 failing to acquire an IP via DHCP

Comment 4 Ahmed Taha 2009-03-20 18:29:54 UTC
(In reply to comment #0)
> Description of problem:
> 
> PXE Kickstart using RHEL5 U2 x86_64 to Sun X4100 (NIC Intel e1000 driver) fails
> to acquire an IP via dhcp after loading the initrd. 
> 
> Version-Release number of selected component (if applicable):
> 
> RHEL5 U2 
> 
> How reproducible: Always
> 
> 
> Steps to Reproduce:
> 1. PXE boot X4100 Sun Server from the vmlinuz and initrd.img of RHEL5 U2
> x86_64. At the PXE boot menu select the distribution (RHEL5 U2) configured in
> /tftpboot/pxelinux.cfg/default file to kickstart the Sun Server. The anaconda
> network configuration dialogue will repeatedly prompt for IP info unable to
> acquire an IP via the dhcp broadcast from the kickstart server. 
> 
> Actual results:
> 
> Kickstarting a Sun X4100 x86_64 with RHEL5 U2 fails.
> 
> 
> Expected results:
> 
> Kickstarting a Sun X4100 x86_64 with RHEL5 U2 should succeed.
> 
> Additional info:
> 
> Some of the work-around solutions that I have tried so far are the following:
> 
> 1- Appending nicdelay=30 linksleep=10 to the initrd boot line
> 
> 2- Using a custom initrd that does not have the e1000e module in it (only
> contains the e1000 module necessary for the Intel Card)
> 
> 3- Static network configuration using a static IP .. which brings a different
> error message (uploaded image sigsegv.png) and exits abnormally.

Comment 5 Ahmed Taha 2009-03-20 18:30:56 UTC
The network card is Intel and the server hardware is Sun x4100. The network card, and hence, the kickstart process has no problems when using RHEL5 U1 (except for a spontaneous fluctuation of the NIC while it comes up with an IP).


When using RHEL5 U2 (and also if trying the new RHEL5  U3), the e1000 driver cannot report an UP link to eth0 (the kickstart device)

Comment 6 Chris Lumens 2010-10-13 21:21:34 UTC
Sorry for not seeing this bug report earlier.  Do you have multiple NICs in the computer, and anaconda is choosing the wrong one?  Also, U2 and U3 are both fairly old at this point.  Can you try with U5 or U6 (whatever's available to you) and see if the problem goes away?  Thanks.


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