From: Roger Gammans <roger@computer-surgery.co.uk>
To: Meelis Roos <mroos@cs.ut.ee>
Cc: kuznet@ms2.inr.ac.ru, "David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux TCP problem while talking to hostme.bkbits.net ?
Date: Tue, 13 Aug 2002 13:31:59 +0100 [thread overview]
Message-ID: <20020813133159.A21210@computer-surgery.co.uk> (raw)
In-Reply-To: <Pine.GSO.4.43.0208131137110.14316-100000@romulus.cs.ut.ee>; from mroos@cs.ut.ee on Tue, Aug 13, 2002 at 11:40:08AM +0300
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
On Tue, Aug 13, 2002 at 11:40:08AM +0300, Meelis Roos wrote:
> > The problem is that checksum in tcpdump is OK.
> > This smells really bad.
> >
> > I feel you have to hunt where exactly the segment is dropped
> > and TCPInErrs is incremented.
>
> Things got stranger. The symptoms started to appear on other connections
> [....]
> 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've seen these sort of symptoms before and it turned out
to be faulty memory.
Back in 2.2 I had a box which picked the behavior up if
you did a ifconfig down/ifconfig up after it had been running
for some time.
tcpdump on the localbox it that case showed Ok (outgoing) packets, but
another box on the same network segment showed the same packets as
corrupted.
Changing the RAM cured it completely.
TTFN
--
Roger.
Master of Peng Shui. (Ancient oriental art of Penguin Arranging)
GPG Key FPR: CFF1 F383 F854 4E6A 918D 5CFF A90D E73B 88DE 0B3E
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-08-13 12:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
[not found] <1029389331.20774.17.camel@lancelot>
2002-08-15 5:35 ` Clint Byrum
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=20020813133159.A21210@computer-surgery.co.uk \
--to=roger@computer-surgery.co.uk \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--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.