> Things got stranger. The symptoms started to appear on other connections
> too (slashdot web for example). TCP bad packet count increased and no
> success was made. I did a reboot with the same kernel (2.4.19+bk of some
> state, 4. Aug probably) and it just started to work with the same kernel
> image.
>
I am seeing this exact same problem on 2.4.18+ipsec+grsecurity, though
mine is on an Intel NIC..
eth0: OEM i82557/i82558 10/100 Ethernet, 00:02:B3:1E:41:4D, IRQ 10.
eth0 Link encap:Ethernet HWaddr 00:02:B3:1E:41:4D
inet addr:10.30.3.2 Bcast:10.30.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:110268 errors:0 dropped:0 overruns:0 frame:0
TX packets:4613 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:26566206 (25.3 MiB) TX bytes:430171 (420.0 KiB)
Interrupt:10
This box was up for about 15 days without problems, and then started
exhibiting this behavior of not seeing SYNACK's. Though this was
happening to me on all attempts at making an outgoing TCP connection. My
tcpdump was nearly identical to your earlier post. I rebooted it, and it
has not had any problems with outgoing connections since(a whole 6
hours).
> Now I will test and see if the symptoms appear again after some days.
>
That is where I am at too. If worst comes to worst, I will break out the
memtest86 disk and see if it is in fact bad RAM causing this stuff.
btw... I am not subscribed to lkml, so please CC: me on any replies to
this. Thanks. :)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 15 2002 - 22:00:38 EST