Description of problem: Incoming network packets are not accepted when booting into kernel 2.6.16-1.2069_FC4. There is no reaction to the packets and the system acts broken. Mouse movement in gnome desktop was also very jerky, but everything else seems to work. Version-Release number of selected component (if applicable): 2.6.16-1.2069_FC4 How reproducible: Every time Steps to Reproduce: 1. Boot into kernel 2.6.16-1.2069_FC4 2. ping machine 3. no response 4. ping from machine 5. machine sends arp requests (at least sometimes) but fails to respond. Actual results: During boot I ping the machine continually; it never responds. When I boot with kernel 2.6.15-1.1833_FC4 it responds immediately eth0 is reported as coming up. When I have the machine up and ping from it, I can see arp requests on the connected network. The machine ignores repeated responses on the other side. When I switch back to kernel 1.1833_FC4 everything works correctly. Expected results: The machine should respond to pings. Additional info: I have two network cards eth0 8139too and eth1 3c59x I did a number of tests to determine this. Plugging in out / bringing up and down interfaces / testing both of my ethernet cards / connecting three hosts to the same network and verifying that the other two were working. It is possible that there were processes run from init continuously restarting due to the lack of network. The mouse movement problems may be unrelated to the real problem.
Created attachment 127202 [details] collection of system / rpm information
Created attachment 127203 [details] log of system booting with kernel 2.6.16-1.2069_FC4 During this log I booted the system and pinged it continuously from another machine over a cross cable. No response was ever seen even though the same setup worked immediately with the older kernel. The machine has a static IP address configured on eth0.
Created attachment 127204 [details] this file contains two (txt) logs from tcpdump Here are two logs from tcpdump. The problem host is 192.168.0.2. The default router on that host is 192.168.0.1; at the start no such host is present on the network. The host 192.168.0.249 is where the tcpdump is running and is pinging the host 192.168.0.2. For the second log I added the default router IP address to the test host part way through (ip addr add 192.168.0.1 dev eth0). From this point on it responds to arp requests from the problem host, but the problem host doesn't seem to see the response and keeps making requests. Even though I tried pinging 192.168.0.249 directly, I have never seen a related arp request.
Created attachment 127498 [details] kernel config file from failing 2.6.16 kernel This bug is seems to be the same on a standard 2.6.16 kernel (based on the package installed in the kernel src.rpm). I guess then that it's not related to Fedora specific issues. I'm going to try to test it on the a recent kernel and then try to report it upstream.
I have reproduced this in 2.6.16.2 also. I've now put it into bugzilla.kernel.org (see external bug reference).