Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756789AbWKVUBa (ORCPT ); Wed, 22 Nov 2006 15:01:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752916AbWKVUBa (ORCPT ); Wed, 22 Nov 2006 15:01:30 -0500 Received: from smtp.osdl.org ([65.172.181.25]:7849 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1756777AbWKVUB2 (ORCPT ); Wed, 22 Nov 2006 15:01:28 -0500 Date: Wed, 22 Nov 2006 12:01:19 -0800 From: Stephen Hemminger To: "Jesper Juhl" Cc: "David Chinner" , chatz@melbourne.sgi.com, LKML , xfs@oss.sgi.com, xfs-masters@oss.sgi.com, netdev@vger.kernel.org, linux-scsi@vger.kernel.org Subject: Re: 2.6.19-rc6 : Spontaneous reboots, stack overflows - seems to implicate xfs, scsi, networking, SMP Message-ID: <20061122120119.416901c7@freekitty> In-Reply-To: <9a8748490611220458w4d94d953v21f7a29a9f1bdb72@mail.gmail.com> References: <200611211027.41971.jesper.juhl@gmail.com> <45637566.5020802@melbourne.sgi.com> <9a8748490611211402xdc2822fqbc95a77fe54d49b1@mail.gmail.com> <20061121233141.GP37654165@melbourne.sgi.com> <9a8748490611211551v2ebe88fel2bcf25af004c338a@mail.gmail.com> <9a8748490611220458w4d94d953v21f7a29a9f1bdb72@mail.gmail.com> Organization: OSDL X-Mailer: Sylpheed-Claws 2.5.0-rc3 (GTK+ 2.10.6; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2128 Lines: 54 On Wed, 22 Nov 2006 13:58:11 +0100 "Jesper Juhl" wrote: > On 22/11/06, Jesper Juhl wrote: > > On 22/11/06, David Chinner wrote: > > > On Tue, Nov 21, 2006 at 11:02:23PM +0100, Jesper Juhl wrote: > > > > On 21/11/06, David Chatterton wrote: > ... > > > > >Thanks for traces, I've captured this information. > > > > > > > > > You are welcome. If you want/need more traces then I've got ~2.1G > > > > worth of traces that you can have :) > > > > > > Well, we don't need that many, but it would be nice to have a > > > set of unique traces that lead to overflows - could you process > > > them in some way just to extract just the unique XFS traces that > > > occur? > > > > > I'll try to extract a copy of each unique trace that involves xfs, > > sometime tomorrow or the day after, and then send you the result. > > > > Attached are two files. The one named stack_overflows.txt.gz contains > one instance of each unique stack overflow + trace that I've got. The > other file named kernel_BUG.txt.gz contains a few BUG() messages that > were also in the logs. > You have a kind of worst case scenario there: XFS + Block layer TCP receive/transmit VLAN It is hard to know who to blame, there is no information about stack level at each call. Since it doesn't show up for filesystems other than XFS, I would pick on that. Perhaps the following: --- 2.6.19-rc6.orig/arch/i386/Kconfig.debug 2006-11-22 11:59:32.000000000 -0800 +++ 2.6.19-rc6/arch/i386/Kconfig.debug 2006-11-22 12:00:28.000000000 -0800 @@ -58,7 +58,7 @@ config 4KSTACKS bool "Use 4Kb for kernel stacks instead of 8Kb" - depends on DEBUG_KERNEL + depends on DEBUG_KERNEL && !XFS_FS help If you say Y here the kernel will use a 4Kb stacksize for the kernel stack attached to each process/thread. This facilitates - 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/