From: Clint Byrum <cbyrum@spamaps.org>
To: Meelis Roos <mroos@cs.ut.ee>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux TCP problem while talking to hostme.bkbits.net ?
Date: 14 Aug 2002 22:35:04 -0700 [thread overview]
Message-ID: <1029389705.21173.31.camel@lancelot> (raw)
In-Reply-To: <1029389331.20774.17.camel@lancelot>
> 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. :)
next parent reply other threads:[~2002-08-15 5:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1029389331.20774.17.camel@lancelot>
2002-08-15 5:35 ` Clint Byrum [this message]
2002-08-11 12:19 Linux TCP problem while talking to hostme.bkbits.net ? Meelis Roos
2002-08-11 21:25 ` kuznet
2002-08-12 7:28 ` Meelis Roos
2002-08-12 9:54 ` David S. Miller
2002-08-12 10:14 ` Meelis Roos
2002-08-12 17:32 ` kuznet
2002-08-13 8:40 ` Meelis Roos
2002-08-13 12:31 ` Roger Gammans
2002-09-19 13:15 ` Meelis Roos
2002-09-19 19:21 ` David S. Miller
2002-08-13 13:40 ` kuznet
2002-08-13 13:48 ` Larry McVoy
2002-08-13 13:57 ` Meelis Roos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1029389705.21173.31.camel@lancelot \
--to=cbyrum@spamaps.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@cs.ut.ee \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.