From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: Netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
corbet@lwn.net
Subject: Re: WARNING: at net/ipv4/tcp_input.c:2927 tcp_ack+0xd55/0x1991()
Date: Mon, 30 Mar 2009 18:40:36 +0200 [thread overview]
Message-ID: <20090330164035.GA2652@gentoox2.trippelsdorf.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0903301155150.30150@wrl-59.cs.helsinki.fi>
On Mon, Mar 30, 2009 at 07:01:22PM +0300, Ilpo Järvinen wrote:
> On Sat, 28 Mar 2009, Markus Trippelsdorf wrote:
>
> > On Sat, Mar 28, 2009 at 10:29:58AM +0200, Ilpo Järvinen wrote:
> > > On Sat, 28 Mar 2009, Markus Trippelsdorf wrote:
> > >
> > > > On Sat, Mar 28, 2009 at 01:05:09AM +0200, Ilpo Järvinen wrote:
> > > > > On Fri, 27 Mar 2009, Markus Trippelsdorf wrote:
> > > > >
> > > > > > I'm running the latest git kernel (2.6.29-03321-gbe0ea69) and I've got
> > > > > > this warning twice in the last few hours.:
>
> > > > > > The machine hangs afterwards.
> > > > >
> > > > > Is it really related to the warning for sure? I find it hard to
> > > > > believe...
> > > >
> > > > The machine is normally running stable for days. Switching back to 2.6.29
> > > > solves the problem...
> > >
> > > Sure, but does is hang right after printing that warning or much later on,
> > > e.g., one minute is already a very long time for the crash to be related
> > > to that warning... Even 5 seconds is a long time but I'd immediately say
> > > it's not related then :-).
> >
> > I really can't tell you. In both occurrences of the warning the machine
> > was already unusable when I noticed. I then rebooted and the last entry
> > in the logs was that warning.
>
> ...And, let me guess, you're in X and therefore unable to catch a final
> oops if any would be printed? It would be nice to get around that as well,
> either use serial/netconsole or hang in text mode while waiting for the
> crash (should be too hard if you are able to setup the workload first
> and then switch away from X and if reproducing takes about an hour)...
OK, I will try this later.
>
> Arguably the presence of that warning at both times is somewhat alarming.
Make that four times:
kernel # for i in log*; cat $i | grep "tcp_input";
Mar 27 19:57:40 [kernel] WARNING: at net/ipv4/tcp_input.c:2927 tcp_ack+0xd55/0x1991()
Mar 27 21:37:00 [kernel] WARNING: at net/ipv4/tcp_input.c:2927 tcp_ack+0xd55/0x1991()
Mar 28 18:41:03 [kernel] WARNING: at net/ipv4/tcp_input.c:2927 tcp_ack+0xd55/0x1994()
Mar 29 11:32:26 [kernel] WARNING: at net/ipv4/tcp_input.c:2927 tcp_ack+0xd5b/0x19a9()
The symptoms are always the same...
Another observation is that all four WARNINGs involve only one of my
two networks adapters, namely skge (build into my mobo). The other one
(r8169) never occurs in the call trace.
I will also try to reproduce the WARNING with Jon's patch applied.
--
Markus
next prev parent reply other threads:[~2009-03-30 16:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 21:12 Markus Trippelsdorf
2009-03-27 23:05 ` Ilpo Järvinen
2009-03-28 4:50 ` Markus Trippelsdorf
2009-03-28 8:29 ` Ilpo Järvinen
2009-03-28 9:55 ` Markus Trippelsdorf
2009-03-28 13:56 ` Jonathan Corbet
2009-03-30 8:51 ` Jarek Poplawski
2009-03-30 14:01 ` Jonathan Corbet
2009-03-30 16:40 ` Jarek Poplawski
2009-03-30 16:01 ` Ilpo Järvinen
2009-03-30 16:40 ` Markus Trippelsdorf [this message]
2009-03-30 18:52 ` Ilpo Järvinen
2009-03-31 7:10 ` Markus Trippelsdorf
2009-03-31 9:16 ` Ilpo Järvinen
2009-03-31 18:49 ` Markus Trippelsdorf
2009-03-31 19:12 ` Ilpo Järvinen
2009-04-01 7:00 ` Ilpo Järvinen
2009-04-01 11:09 ` Ilpo Järvinen
2009-04-01 11:35 ` Markus Trippelsdorf
2009-04-02 9:15 ` [PATCH 1/2] tcp: add helper for counter tweaking due mid-wq change Ilpo Järvinen
2009-04-02 9:18 ` [PATCH 2/2] tcp: miscounts due to tcp_fragment pcount reset Ilpo Järvinen
2009-04-02 23:32 ` David Miller
2009-04-02 23:32 ` [PATCH 1/2] tcp: add helper for counter tweaking due mid-wq change 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=20090330164035.GA2652@gentoox2.trippelsdorf.de \
--to=markus@trippelsdorf.de \
--cc=corbet@lwn.net \
--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
all inboxes | Powered by JetHome®