mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "David Chinner" <dgc@sgi.com>
Cc: "Arjan van de Ven" <arjan@infradead.org>,
	"Ingo Oeser" <netdev@axxeo.de>,
	"David Miller" <davem@davemloft.net>,
	chatz@melbourne.sgi.com, 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: Fri, 24 Nov 2006 02:08:53 +0100	[thread overview]
Message-ID: <9a8748490611231708w3abf295bw3c007acf5cdcf336@mail.gmail.com> (raw)
In-Reply-To: <20061124005528.GF11034@melbourne.sgi.com>

On 24/11/06, David Chinner <dgc@sgi.com> wrote:
> On Thu, Nov 23, 2006 at 07:37:00PM +0100, Arjan van de Ven wrote:
> > On Thu, 2006-11-23 at 14:16 +0100, Ingo Oeser wrote:
> > > Hi there,
> > >
> > > David Chinner schrieb:
> > > > If the softirqs were run on a different stack, then a lot of these
> >
> > softirqs DO run on their own stack!
>
> So they run on a separate stack for 4k stacks on x86?
>

Yes, with 4K stacks there's sepperate IRQ stack.

>From the help text for CONFIG_4KSTACKS :

"If you say Y here the kernel will use a 4Kb stacksize for the
 kernel stack attached to each process/thread. This facilitates
 running more threads on a system and also reduces the pressure
 on the VM subsystem for higher order allocations. This option
 will also use IRQ stacks to compensate for the reduced stackspace."


> They don't run on a separate stack for 8k stacks on x86 -
> Jesper's traces show that - so this may indicate an issue
> with the methodology used to generate the stack overflow
> traces inteh first place. i.e. if 4k stacks use a separate
> stack, then most of the reported overflows are spurious
> and would not normally occur on 4k stack systems..
>

Well, some of the traces show that we were down to ~3K stack free with
8K stacks, so ~5K used. Even with 4K stacks and sepperate stack for
IRQs we will still be uncomfortably close to the edge in those cases.
Also, I did manage to capture a single line via netconsole while
running with 4K stacks :
    do_IRQ: stack overflow: 492
Unfortunately that was the only line that made it to the remote log
server, so I don't have the actual trace for that one. But it does
show that there really is an issue when running with 4K stacks, IRQ
stacks or no.


-- 
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

  reply	other threads:[~2006-11-24  1:08 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
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 [this message]
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=9a8748490611231708w3abf295bw3c007acf5cdcf336@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=arjan@infradead.org \
    --cc=chatz@melbourne.sgi.com \
    --cc=davem@davemloft.net \
    --cc=dgc@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=netdev@axxeo.de \
    --cc=netdev@vger.kernel.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®