Red Hat Bugzilla – Bug 250003
DHCP client sometimes does not get an IP address with kernel-188.8.131.52-33.fc7
Last modified: 2007-11-30 17:12:11 EST
Description of problem:
Since updating to kernel-184.108.40.206-33.fc7 I'm having massive problems to get an
IP address via DHCP. During startup the boot process stays forever at "Getting
IP address for eth0". The kernel has not locked up as I still can use
CTRL-ATL-DEL to reboot. Also, everything is ok if I set the IP address manually
with ifconfig, only DHCP seems to fail. The network card is an Intel E1000.
There is nothing in the logs as syslog is started after network in rc5.d.
Version-Release number of selected component (if applicable):
Sometimes, when using DHCP
Steps to Reproduce:
Me, too, looks like 2.6.22 has a bug here. Perhaps related:
A lot of different machines does not get IP by DHCP client here with
kernel-220.127.116.11-33.fc7 because the client indefinitely waiting even receiving
DHCP reply (as seen by manual executing with debugging output enabled). Older
kernels based on 2.6.21 works ok. I don't have access to all FC7 kernel updates
to find which update breaked it up exactly (but I am able to try with some URL
to the archive).
There is no difference between old and new motherboards (from 800MHz to
completly new systems from different manufacturers) or different Ethernet cards
(onboard or in the slot) except some modern mobos only waits for ~10 or so
minutes and then continuing and works ok.
Is there any reason why such a buggy (see also
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249857) kernel would be not
replaced by a working one (e.g. roll-back using EPOCH)? Many non-experienced F7
users are now sitting in front of a no longer proper working desktop (no net, no
proper time on desktop and in syslog), probably having no idea, what's happen
after the latest applied kernel updates.
BTW: FC6 users have no such problems (at the moment)
Older kernel works OK and user is able to make a choice at startup. Also fixed
IP is OK.
The kernel-18.104.22.168-41.fc7 (released today) seems to solve the problem.
The bug could be closed and reopened if problem persit somewhere.
*** Bug 250034 has been marked as a duplicate of this bug. ***
*** Bug 249999 has been marked as a duplicate of this bug. ***
*** Bug 249950 has been marked as a duplicate of this bug. ***
*** Bug 249931 has been marked as a duplicate of this bug. ***
*** Bug 249886 has been marked as a duplicate of this bug. ***
*** Bug 249698 has been marked as a duplicate of this bug. ***
*** Bug 250032 has been marked as a duplicate of this bug. ***