[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0805291049420.19431@wrl-59.cs.helsinki.fi>
Date: Thu, 29 May 2008 11:10:39 +0300 (EEST)
From: "Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To: Andy Furniss <lists@...yfurniss.entadsl.com>
cc: Netdev <netdev@...r.kernel.org>
Subject: Re: WARNING: at net/ipv4/tcp_input.c
On Thu, 29 May 2008, Andy Furniss wrote:
> ? wrote:
> > On Sat, 3 May 2008, Andy Furniss wrote:
> >
> > > Ilpo J?rvinen wrote:
> > >
> > > > Since I've not yet found any other path that could lead to it except the
> > > > yesterday's false-positive, getting the write queue state more
> > > > accurately
> > > > captured by the debug patch on the very first occassion might help.
> > > > Here's
> > > > less spammy version of the debug patch (I added one printout as well to
> > > > get
> > > > more usefulness to transitional state reported).
> > > >
> > > OK, increased CONFIG_LOG_BUF_SHIFT from 14 to 18 and reversed old /
> > > applied
> > > new patch.
> >
> > Any luck so far?
> >
>
> Finally - looks like I got two together.
>
> It doesn't start with WARNING - but dmesg isn't full.
This looks ok trace this time :-), I changed the ordering of the lines so
that warning was supposed to appear only after the wq print. Now it's just
the hard par remaining, ie., I must figure out what was the state of TCP
before the event the event... :-).
If you still get additional events (you could if a particular torrent
peer is there having the same network behavior), please post them as well
if they reveal something that helps exclude cases (if I don't right away
get the idea :-)).
--
i.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists