From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Stephen Hemminger" <shemminger@osdl.org>
Cc: "David Chinner" <dgc@sgi.com>,
chatz@melbourne.sgi.com, LKML <linux-kernel@vger.kernel.org>,
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
Date: Thu, 23 Nov 2006 11:27:26 +0100 [thread overview]
Message-ID: <9a8748490611230227x79247715h9e47a4e96bb7f915@mail.gmail.com> (raw)
In-Reply-To: <20061122120119.416901c7@freekitty>
On 22/11/06, Stephen Hemminger <shemminger@osdl.org> wrote:
> On Wed, 22 Nov 2006 13:58:11 +0100
> "Jesper Juhl" <jesper.juhl@gmail.com> wrote:
>
> > On 22/11/06, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> > > On 22/11/06, David Chinner <dgc@sgi.com> wrote:
> > > > On Tue, Nov 21, 2006 at 11:02:23PM +0100, Jesper Juhl wrote:
> > > > > On 21/11/06, David Chatterton <chatz@melbourne.sgi.com> 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:
>
Well, there's a very good explanation for that. The server has nothing
but XFS file systems (well, /boot is ext3, but that doesn't get used
for anything but the kernel image and System.map file).
>
> --- 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
>
Using 8K stacks works arround the problem, so for now the above patch
may well make sense. But, it would be better to get XFS fixed rather
than start adding dependencies for 4KSTACKS - it might be troublesome
getting rid of it again.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-11-23 10:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 9:27 Jesper Juhl
2006-11-21 21:53 ` David Chatterton
2006-11-21 22:02 ` Jesper Juhl
2006-11-21 23:31 ` David Chinner
2006-11-21 23:51 ` Jesper Juhl
2006-11-22 12:58 ` Jesper Juhl
2006-11-22 20:01 ` Stephen Hemminger
2006-11-23 10:27 ` Jesper Juhl [this message]
2006-11-23 1:18 ` David Chinner
2006-11-23 4:10 ` David Miller
2006-11-23 4:35 ` Al Viro
2006-11-23 6:47 ` Matthew Wilcox
2006-11-23 8:12 ` Arjan van de Ven
2006-11-23 22:08 ` [xfs-masters] " Nathan Scott
2006-11-26 14:31 ` Eric Sandeen
2006-11-23 7:08 ` David Chinner
2006-11-23 13:16 ` Ingo Oeser
2006-11-23 18:37 ` Arjan van de Ven
2006-11-23 19:54 ` David Miller
2006-11-24 0:55 ` David Chinner
2006-11-24 1:08 ` Jesper Juhl
2006-11-24 2:05 ` David Chinner
2006-11-24 7:52 ` Arjan van de Ven
2006-11-23 19:42 ` David Miller
2006-11-29 1:56 ` David Chinner
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=9a8748490611230227x79247715h9e47a4e96bb7f915@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=chatz@melbourne.sgi.com \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.com \
/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®