Bug 5131
| Summary: | Computer hangs when default-gw becomes unreachable | ||
|---|---|---|---|
| Product: | Networking | Reporter: | Sebastian Hyrwall (zibbe) |
| Component: | Other | Assignee: | S.Mohideen (moin) |
| Status: | REJECTED INSUFFICIENT_DATA | ||
| Severity: | high | CC: | protasnb |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.13-rc3-mm1 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
|
Description
Sebastian Hyrwall
2005-08-26 02:21:29 UTC
bugme-daemon@kernel-bugs.osdl.org 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? bugme-daemon@kernel-bugs.osdl.org wrote: >http://bugzilla.kernel.org/show_bug.cgi?id=5131 > > > > > >------- Additional Comments From akpm@osdl.org 2005-08-26 04:44 ------- >bugme-daemon@kernel-bugs.osdl.org 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? > > > >------- You are receiving this mail because: ------- >You reported the bug, or are watching the reporter. > > > > I may be able to test 2.6.13-rc6-mm2 in a while. Unfortunetly this system is in production so I can not just take it down. But If the problem happens again I will change to 2.6.13-rc6-mm2. No nothing interesting at all in the kernel logs. I can however add that a friend with similar specs and same kernel version had a similar problem except that the computer didn't crash right away. After the problem happened he could login as root on the console and everything seemed to be working except that the e1000-card could not communicate with the gateway. The gateway did answer the arp-requests from the e1000-card but it didn't respond to icmp or route any traffic. However he could communicate with all other computers in the same subnet and those computers could also communicate with the gateway properly. He also tried changing mac-address on the card and IP-address. After that the gateway would answer to a few icmp-packets and then dying like before. He also tried unloading and loading the e1000-module without success. A few minutes later the computer hanged like mine does. After a power-reset everything worked fine again. Andrew Morton wrote: >bugme-daemon@kernel-bugs.osdl.org 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 Any update on this problem please. Thanks. Closing the bug since no recent activity. Please reopen if confirmed with newest kernel. |