Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755975AbZC3QBj (ORCPT ); Mon, 30 Mar 2009 12:01:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753870AbZC3QB1 (ORCPT ); Mon, 30 Mar 2009 12:01:27 -0400 Received: from courier.cs.helsinki.fi ([128.214.9.1]:34198 "EHLO mail.cs.helsinki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753810AbZC3QB0 (ORCPT ); Mon, 30 Mar 2009 12:01:26 -0400 Date: Mon, 30 Mar 2009 19:01:22 +0300 (EEST) From: "=?ISO-8859-1?Q?Ilpo_J=E4rvinen?=" X-X-Sender: ijjarvin@wrl-59.cs.helsinki.fi To: Markus Trippelsdorf cc: Netdev , LKML , corbet@lwn.net Subject: Re: WARNING: at net/ipv4/tcp_input.c:2927 tcp_ack+0xd55/0x1991() In-Reply-To: <20090328095514.GA2599@gentoox2.trippelsdorf.de> Message-ID: References: <20090327211202.GA10014@gentoox2.trippelsdorf.de> <20090328045056.GA2394@gentoox2.trippelsdorf.de> <20090328095514.GA2599@gentoox2.trippelsdorf.de> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; boundary="-696208474-395882101-1238403878=:30150" Content-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2572 Lines: 63 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---696208474-395882101-1238403878=:30150 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Content-ID: 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)... Arguably the presence of that warning at both times is somewhat alarming. > > So you never saw this warning before within 2.6.29 or 2.6.28-26 timeframe? > > Thats right. And you were looking for them too at that time? If you still have old logs available you can verify that easily... if they're compressed you'll need something like this: for i in ; do gunzip -c -d $i | grep "tcp_input"; done) -- i. ---696208474-395882101-1238403878=:30150-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/