From: "David S. Miller" <davem@davemloft.net>
To: Andrew Morton <akpm@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: tcp heisenbug
Date: Fri, 8 Oct 2004 12:25:48 -0700 [thread overview]
Message-ID: <20041008122548.544a3329.davem@davemloft.net> (raw)
In-Reply-To: <20041008014151.26e17547.akpm@osdl.org>
On Fri, 8 Oct 2004 01:41:51 -0700
Andrew Morton <akpm@osdl.org> wrote:
> fetchmail broke. It's fetching mail from localhost (ssh port-forwarded to
> remote servers) and then for some reason it wants to open an SMTP
> connection to localhost. It was failing, some error message about that
> SMTP connection.
>
> While I was poking at it, it started to work. `uptime' said 6 minutes. So
> I'd be suspecting that there's a jiffy wrap bug in TCP-to-localhost
> introduced since 2.6.9-rc3.
That's possible.
It could also be something that only happens the first time you try
to talk to a remote system.
You're using e1000 on x86 right? Maybe force TSO off via ethtool
right after the interface is brought up and see if that makes it
go away?
next prev parent reply other threads:[~2004-10-08 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 8:41 tcp heisenbug Andrew Morton
2004-10-08 19:25 ` David S. Miller [this message]
2004-10-08 19:33 ` Andrew Morton
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=20041008122548.544a3329.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).