LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: Giangiacomo Mariotti <giangiacomo_mariotti@yahoo.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Netdev <netdev@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: WARNING: at net/ipv4/tcp_input.c:2054 tcp_mark_head_lost()
Date: Wed, 27 Feb 2008 11:29:51 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0802271108290.13029@kivilampi-30.cs.helsinki.fi> (raw)
In-Reply-To: <20080223000310.4630daa8.akpm@linux-foundation.org>

On Sat, 23 Feb 2008, Andrew Morton wrote:

> 
> (cc netdev)
> 
> On Wed, 20 Feb 2008 20:04:39 -0800 (PST) Giangiacomo Mariotti <giangiacomo_mariotti@yahoo.com> wrote:
> 
> > This is what I got with dmesg :
> > 
> > [  266.978695] WARNING: at net/ipv4/tcp_input.c:2054 tcp_mark_head_lost()
> > [  266.978701] Pid: 0, comm: swapper Not tainted 2.6.24.2-my001 #1
> > [  266.978703] 
> > [  266.978704] Call Trace:
> > [  266.978706]  <IRQ>  [<ffffffff80426981>] tcp_ack+0x16d8/0x197f
> > [  266.978721]  [<ffffffff8022e72f>] __wake_up+0x38/0x4e
> > [  266.978727]  [<ffffffff804295ef>] tcp_rcv_established+0xe2/0x8cb
> > [  266.978732]  [<ffffffff8042f56f>] tcp_v4_do_rcv+0x30/0x39c
> > [  266.978738]  [<ffffffff80431d29>] tcp_v4_rcv+0x99b/0xa06
> > [  266.978743]  [<ffffffff803f2c95>] __netdev_alloc_skb+0x29/0x43
> > [  266.978749]  [<ffffffff80416d21>] ip_local_deliver_finish+0x152/0x212
> > [  266.978753]  [<ffffffff80416bac>] ip_rcv_finish+0x2f8/0x31b
> > [  266.978758]  [<ffffffff803f6c42>] netif_receive_skb+0x3ae/0x3d1
> > [  266.978763]  [<ffffffff8037398f>] rtl8169_rx_interrupt+0x45f/0x53e
> > [  266.978768]  [<ffffffff8037405b>] rtl8169_poll+0x36/0x16a
> > [  266.978773]  [<ffffffff803f8ca7>] net_rx_action+0xb7/0x1f3
> > [  266.978778]  [<ffffffff8023a3a5>] __do_softirq+0x65/0xce
> > [  266.978782]  [<ffffffff8020b0d2>] default_idle+0x0/0x3d
> > [  266.978786]  [<ffffffff8020d09c>] call_softirq+0x1c/0x28
> > [  266.978789]  [<ffffffff8020e4f0>] do_softirq+0x2c/0x7d
> > [  266.978792]  [<ffffffff8023a2fb>] irq_exit+0x3f/0x84
> > [  266.978794]  [<ffffffff8020e729>] do_IRQ+0xb6/0xd5
> > [  266.978797]  [<ffffffff8020b0d2>] default_idle+0x0/0x3d
> > [  266.978800]  [<ffffffff8020c421>] ret_from_intr+0x0/0xa
> > [  266.978801]  <EOI>  [<ffffffff8020b0fb>] default_idle+0x29/0x3d
> > [  266.978809]  [<ffffffff8020b1a2>] cpu_idle+0x93/0xbb
> > [  266.978813]  [<ffffffff805cfa4b>] start_kernel+0x2bb/0x2c7
> > [  266.978818]  [<ffffffff805cf123>] _sinittext+0x123/0x12a
> > [  266.978821] 
> > 

Are you able to reproduce this in any way? I did in the past a debug patch 
that verifies TCP's write queue state by the hard way, ie., by bruteforce 
walking often enough to catch inconsistencies early enough to find out 
the root cause. I'll try to find that for you after I first go through 
the 2.6.24.2's code once again (but I'm pretty busy at this moment, so 
it might take a small while)...

> > This though didn't cause any user-visible problem.

Usually it's very insignificant to see them, unless you have them in very 
large quantities (it usually triggers for the same occurance in a number 
of places where that very same thing is being checked, thus having many 
of them in a row once is not what I mean here).

Were there Leak printouts as well a bit after that? If not, this is 
triggered with either non-SACK TCP or it is a genuine S+L bits bug.

-- 
 i.

  reply	other threads:[~2008-02-27  9:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  4:04 Giangiacomo Mariotti
2008-02-23  8:03 ` Andrew Morton
2008-02-27  9:29   ` Ilpo Järvinen [this message]
2008-02-27 18:56     ` Guillaume Chazarain
2008-02-27 19:29       ` Ilpo Järvinen
2008-02-28  8:22         ` Ilpo Järvinen
2008-02-29  1:10           ` Andrew Morton
2008-02-29  4:35             ` Bill Fink
2008-02-29 12:24               ` Ilpo Järvinen
2008-03-02 12:20           ` Guillaume Chazarain
2008-03-02 12:38             ` Ilpo Järvinen
2008-03-02 13:15               ` Guillaume Chazarain
2008-03-02 19:51                 ` Ilpo Järvinen
2008-03-03  8:32                   ` Ilpo Järvinen
2008-03-03 13:40                     ` Ilpo Järvinen
2008-03-03 13:53                       ` [PATCH net-2.6] [TCP]: Must count fack_count also when skipping Ilpo Järvinen
2008-03-03 20:11                         ` David Miller
2008-03-24 20:36                         ` Frederik Himpe
2008-03-24 21:41                           ` David Miller
2008-03-25 21:24                             ` Ilpo Järvinen
2008-03-26  3:05                               ` David Miller

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.0802271108290.13029@kivilampi-30.cs.helsinki.fi \
    --to=ilpo.jarvinen@helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=giangiacomo_mariotti@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --subject='Re: WARNING: at net/ipv4/tcp_input.c:2054 tcp_mark_head_lost()' \
    /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

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).