From: Eric Sandeen <sandeen@sandeen.net>
To: Orion Poplawski <orion@cora.nwra.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: do_IRQ stack overflow on 32-bit CentOS 4
Date: Tue, 30 Jun 2009 12:52:44 -0500 [thread overview]
Message-ID: <4A4A50EC.4090201@sandeen.net> (raw)
In-Reply-To: <loom.20090630T165732-116@post.gmane.org>
Orion Poplawski wrote:
> Just hit a:
>
> do_IRQ: stack overflow: 452
>
> on 32-bit CentOS 4 machine with xfs-kmod-0.4-2.el4. Is there anything that can
> be done to minimize this risk? Running xfs over md raid5 array, exporting via
> nfs. More kernel dump messages are posted at:
>
> http://bugs.centos.org/view.php?id=3136
get an x86_64 machine ;)
The stack overflow message is misleading; it means you have 452 -left-
unfortunately on some kernels, simply printing that message actually
consumes what's left, and more. See http://lkml.org/lkml/2007/8/29/245
This was fixed in 2.6.18-108.el5 and beyond.
Upstream has some xfs stack size fixes; this may eventually make it to a
centos near you.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-30 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 17:00 do_IRQ stack overflow on 32-bit CentOS 4 Orion Poplawski
2009-06-30 17:52 ` Eric Sandeen [this message]
2009-06-30 18:10 ` Eric Sandeen
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=4A4A50EC.4090201@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@oss.sgi.com \
--cc=orion@cora.nwra.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