From: Denys Vlasenko <vda.linux@googlemail.com>
To: "Malte Schröder" <maltesch@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange network related data corruption
Date: Tue, 9 Oct 2007 12:57:20 +0100 [thread overview]
Message-ID: <200710091257.20874.vda.linux@googlemail.com> (raw)
In-Reply-To: <20071009132553.439f7d8b@cp771133>
On Tuesday 09 October 2007 12:25, Malte Schröder wrote:
> > Does it happen over loopback?
>
> I just tried a few times and yes, it also happens on loopback, but
> much less frequently. Now I am really confused ...
Actually, that eliminates a lot of cases.
Run memtest86 overnight ("bad hardware" theory),
try older kernel versions ("kernel bug" theory).
--
vda
next prev parent reply other threads:[~2007-10-09 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 16:47 Strange network related data corruption Malte Schröder
2007-10-08 13:01 ` Denys Vlasenko
2007-10-09 11:25 ` Malte Schröder
2007-10-09 11:57 ` Denys Vlasenko [this message]
2007-10-13 7:55 ` Malte Schröder
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=200710091257.20874.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maltesch@gmx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox