Description of problem: I upgraded from RH9 to the new 2.6-test kernel under http://people.redhat.com/arjanv/2.5 using yum. Everything installed fine with no errors. However upon reboot, retrieving an IP address using DHCP fails. Reboot again under the RH9 kernel (2.4.20-18.9) and DHCP works fine. My ethernet card is a RealTek 8139. Version-Release number of selected component (if applicable): How reproducible: Very reproducible Steps to Reproduce: 1. /sbin/ifup eth0 2. 3. Actual results: Times out Expected results: the ip address is received from the DHCP server Additional info:
I tried to debug this by booting into the 2.6 kernel and activating the network connection by hand using 'ifup eth0' and the gui interface. The output of 'dmesg' shows the driver loading properly (lsmod confirms this too). The content of /var/log/messages shows two DHCPREQUEST then about 6 DHCPDISCOVERs with the latter timing out. I also downloaded the latest dhclient for RH9 but that had no affect.
Does it start working again if you boot with acpi=off ? or noapic ? or a combination of both ?
acpi=off --> works pci=noacpi --> works acpi=off pci=noacpi --> works However, I noticed when using pci=noacpi, my boot time is about 20 seconds slower. Is that normal? Thanks for the tip! Now what does this mean? Is it a software problem or is the cheap hardware I bought last month flaky? :)
just means that there are still bugs in ACPI. *complete lack of surprise*. These are also tracked upstream. See http://bugzilla.kernel.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&component=ACPI&long_desc_type=allwordssubstr&long_desc=&kernel_version_type=allwordssubstr&kernel_version=&bug_status=NEW&bug_status=ASSIGNED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= for an insight .. This bug in particular has been around for quite a while, so bugging the ACPI folks to get it fixed would be a good thing.
Thanks! Yeah, I will go bug them, I have some free time.
Is this a dup of 101217?
I believe this bug has been fixed a while ago (months maybe). You can close this issue for now. If I still have problems I will re-open a new issue. Thanks.