Red Hat Bugzilla – Bug 190586
internet down after kernel upgrade to 2107*
Last modified: 2015-01-04 17:26:51 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
3.not able to ping internet ip address , ip address locally assigned, after
kernel upgrade from kernel-2.6.16-1.2096_FC5 to kernel-2.6.16-1.2107_FC5
everything works fine with the old kernel.
I'm seeing the same thing:
NIC appears to be up, but can't ping it's local IP, can't ping 127.0.0.1, and
can't ping anything else on the network. I've double-checked to make sure
iptables is off, etc. but it's still the same. Rebooting into a previous kernel
works just fine.
*** Bug 190606 has been marked as a duplicate of this bug. ***
does booting with pci=nomsi make this go away?
Actually, that option is also broken in this kernel (sigh).
2108, available from http://people.redhat.com/davej/kernels/Fedora/FC5/
has this disabled by default. Give that a try ?
With me 2107 I did not notice any other problems that when loading web pages
from other client the pages showed up ok when they contained only text. If
they contained any images the pages did not load. (The browser just stalled
and showed nothing). Bigger files/tranmissions -> problem?
Apache log showed no problems. The requests of the unshown images was logged.
I was not able to test more. ssh connection worked btw. Rebooting to old
kernel cured the problem.
With the exception of comment #7, which appears to be a different problem, I'm
seeing this, too ... but only on machines using the tg3 driver. What driver are
the rest of you using for your network cards? For my tg3-using machines, the
symptom is that the DHCP step appears to fail. However, when I look at the
lease file, I see that my machine actually did successfully talk to the DHCP
server and got a lease. Right after the DHCP step, I see the message "no IPv6
routers present", which is silly since these machines are all configured to use
IPv4. Somehow the machine becomes convinced that DHCP failed, even though it
succeeded, and it reverts to 127.0.0.1 as its primary address. Following
bootup, I then get the symptoms the other reporters indicated, but it's due to
the machine thinking the network setup process failed.
I also see quite a few "could not allocate memory" messages in my log from
various kernel subsystems. If kernel memory allocation is broken, that could
explain the widely varying bug reports for this kernel.
I saw it on machines with e1000.
Dave, i'm sure You're a lot smarter than i am, so i'm sure You've noticed that
all of the problems with 2107 that sound like this one have to do with
networking. I just upgraded myself and discovered that all connections from a
host to itself (whether 127.0.0.1 or a non-loopback address) get "stuck".
Looking at them with netstat -an reveals that there are a lot of bytes in the
Send-Q on the server side of the connection.
For the record, this has happened to me with Thunderbird/Dovecot on the same
machine and Firefox/Squid on the same machine. Other machines connecting to my
Dovecot & Squid server with Thunderbird and Firefox have no problems.
Perhaps You've already figured this out, and i just didn't see it in all the bug
reports. If so, forgive the noise.
I'm also seeing similar behavior (except comment #7) with the e1000 driver, 2107
i686 SMP kernel; the interface comes up (static IP), can ping other hosts, but
can't make any kind of TCP connection. Downgrading to 2096 makes the problem go