Andrew Morton wrote:
[EMAIL PROTECTED] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=5131
Summary: Computer hangs when default-gw becomes unreachable
Kernel Version: 2.6.13-rc3-mm1
...
Right now I'm going to try 2.6.13-rc7 to see if the problem occurs there too.
Thanks. It would be useful if you could also test 2.6.13-rc6-mm2.
I assume there was nothing interesting in the kernel logs?
I don't know if this is any help but I was able to reproduce the problem
in another way.
I also have a second e1000-nic in the box. A 64-bit one sitting in a
pci-slot. The problem occurs every time if I do something like this:
Both nic's are connected to the same switch and is not separated by
vlans or anything like that.
The first nic (eth0) has address 192.168.0.2, the second nic (eth1) has
192.168.0.2.
Then what I did was that I applied a staticroute to a second box so that
it would use the eth1-nic:
ip route add 192.168.0.3 dev eth1
Then the second box connected to 192.168.0.2 (eth0) via ftp and
downloads a file which is then sourced with the 192.168.0.2 ip but
transferred
via eth1.
192.168.0.2(eth0) --> eth1 -> 192.168.0.3
Packets are returned coming in on eth0.
192.168.0.3 -> 192.168.0.2(eth0)
Immedietly when i transferred the file the nic's stopped transferring
data and I was back at the problem my friend had.
The box could for some reason not communicate with the gateway
(192.168.0.1) but it could with any other box in the subnet.
Why this problem occured now when the gateway had nothing to do with any
of the test I have no idea.
I solved the problem by unloading the e1000-module and loading it again.
And this now happened in 2.6.13-rc7
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
