From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: int 986 <int986@gmail.com>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: WARNING: at net/ipv4/tcp_input.c:2539 tcp_ack+0xd2b/0x191f()
Date: Tue, 20 May 2008 16:28:07 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0805191152390.16829@wrl-59.cs.helsinki.fi> (raw)
In-Reply-To: <651806990805190057u74f81630l9801b90c2613ed47@mail.gmail.com>
On Mon, 19 May 2008, int 986 wrote:
> thank you for detailed explanation. Debug patch is unlikely to test on our
> live servers, but i can stress test it on our test servers.
Thanks, please take the latest debug patch from here:
http://marc.info/?l=linux-netdev&m=120972551120080&w=2
Please make sure you have log enough buffer for kernel messages while
testing (CONFIG_LOG_BUF_SHIFT) so that the disaster of the last time
doesn't repeat... :-)
> We have farm with web servers for static content delivery and live
> streaming. Our servers are from the tiny one with two disks to large systems
> with 96 disks and external arrays. On every server we are using lighttpd
> 1.5svn and linux 2.6.25.3. This warning we are seeing on every server in our
> farm. I don't think that bug is connected to network setup may be is
> connected to lighttpd - because we are in six different co-locations and
> every co-location has your own network setup :)
Yeah, you may well be right, it could well be something else on the
end-to-end path which causes it to trigger. ...I was just trying to find
a common denominator as the other guy has a setup which is know to reorder
things.
--
i.
prev parent reply other threads:[~2008-05-20 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 15:19 WARNING: at net/ipv4/tcp_input.c:2539 tcp_ack+0xd2b/0x191f() int 986
2008-05-17 21:25 ` Ilpo Järvinen
[not found] ` <651806990805190057u74f81630l9801b90c2613ed47@mail.gmail.com>
2008-05-20 13:28 ` Ilpo Järvinen [this message]
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=Pine.LNX.4.64.0805191152390.16829@wrl-59.cs.helsinki.fi \
--to=ilpo.jarvinen@helsinki.fi \
--cc=int986@gmail.com \
--cc=netdev@vger.kernel.org \
/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).