netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Georgi Chorbadzhiyski <gf@unixsol.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Netdev <netdev@vger.kernel.org>
Subject: Re: Linux 2.6.25-rc6: WARNING: at net/ipv4/tcp_input.c:2510
Date: Fri, 04 Apr 2008 09:16:49 +0300	[thread overview]
Message-ID: <47F5C7D1.1080906@unixsol.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0804031315360.21524@wrl-59.cs.helsinki.fi>

Around 04/03/08 13:17, Ilpo Järvinen scribbled:
> On Thu, 27 Mar 2008, Georgi Chorbadzhiyski wrote:
> 
>> A week ago I updated one of my servers to 2.6.25-rc6 and today looking
>> through logs I've found these:
>>
>> [380219.823434] ------------[ cut here ]------------
>> [380219.823450] WARNING: at net/ipv4/tcp_input.c:2510 tcp_ack+0xc7e/0x177d()
> 
> Is this reproducable for you? If yes, is it possible for you to run 

Not in the moment.

I'm not getting such errors in the log since my last report. Today I'll update
to latest -git and will restart the server.

The machine that gave me this error is a http and ftp server handling not
very busy distro mirror (if this can give you any clues).

> processing expensive verification of TCP state (validates TCP write queue 
> invariants multiple times per ACK by scanning through the write queue) on 
> such machine?

How to run such a thing, can you give me some pointers?

-- 
Georgi Chorbadzhiyski
http://georgi.unixsol.org/

  reply	other threads:[~2008-04-04  6:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27 16:29 Linux 2.6.25-rc6: WARNING: at net/ipv4/tcp_input.c:2510 Georgi Chorbadzhiyski
2008-04-03 10:17 ` Ilpo Järvinen
2008-04-04  6:16   ` Georgi Chorbadzhiyski [this message]
2008-04-04 19:15     ` Ilpo Järvinen
2008-04-05 11:09       ` Georgi Chorbadzhiyski

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=47F5C7D1.1080906@unixsol.org \
    --to=gf@unixsol.org \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --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).