From: Andi Kleen <ak@suse.de>
To: Crazy AMD K7 <snort2004@mail.ru>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: do_IRQ: stack overflow: 872..
Date: 18 Dec 2004 08:50:49 +0100 [thread overview]
Message-ID: <p73zn0ccaee.fsf@verdi.suse.de> (raw)
In-Reply-To: <1131604877.20041218092730@mail.ru.suse.lists.linux.kernel>
Crazy AMD K7 <snort2004@mail.ru> writes:
> Hi!
> I have found a few days ago strange messages in /var/log/messages
> More than 10 times there was do_IRQ: stack overflow: (nimber).... followed
> with code. If need I can send all this data. I have run
> ksymoops with only first 3 cases. Here is the first, the second and
> the third are in attachment.
> After that oopses my system continued to work.
It's not really an oops, just a warning that stack space got quiet tight.
The problem seems to be that the br netfilter code is nesting far too
deeply and recursing several times. Looks like a design bug to me,
it shouldn't do that.
> uname uname -a
> Linux linux 2.4.28 #2 ÷ÔÒ îÏÑ 30 15:43:35 MSK 2004 i686 unknown
> gcc -v
> Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
> gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113)
> I have applies ebtables_brnf patch (http://bridge.sf.net) and a
Don't do that then or contact the author to fix it. Unfortunately
the code is also in 2.6 mainline.
-Andi
next parent reply other threads:[~2004-12-18 7:51 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1131604877.20041218092730@mail.ru.suse.lists.linux.kernel>
2004-12-18 7:50 ` Andi Kleen [this message]
2004-12-18 11:12 ` do_IRQ: stack overflow: 872 Bart De Schuymer
2004-12-18 11:14 ` Andi Kleen
2004-12-18 11:51 ` Bart De Schuymer
2004-12-18 13:53 ` Andi Kleen
2004-12-18 16:07 ` Re[2]: " Crazy AMD K7
2004-12-18 16:46 ` Bart De Schuymer
2005-01-07 17:05 ` David Woodhouse
2005-01-07 18:00 ` [Bridge] " Stephen Hemminger
2005-01-07 18:00 ` Stephen Hemminger
2005-01-07 18:06 ` [Bridge] " David Woodhouse
2005-01-07 18:06 ` David Woodhouse
2005-01-07 21:27 ` [Bridge] " Bart De Schuymer
2005-01-07 21:27 ` Bart De Schuymer
2005-01-18 21:57 ` [Bridge] " David S. Miller
2005-01-18 21:57 ` David S. Miller
2005-01-22 22:30 ` [Bridge] [PATCH/RFC] Reduce call chain length in netfilter (was: Re: do_IRQ: stack overflow: 872..) Bart De Schuymer
2005-01-22 22:30 ` Bart De Schuymer
2005-01-22 23:22 ` [Bridge] " Martin Josefsson
2005-01-22 23:22 ` Martin Josefsson
2005-01-23 12:40 ` [Bridge] " Bart De Schuymer
2005-01-23 12:40 ` Bart De Schuymer
2005-01-23 16:08 ` [Bridge] " Martin Josefsson
2005-01-23 16:08 ` Martin Josefsson
2005-01-26 6:05 ` [Bridge] " David S. Miller
2005-01-26 6:05 ` David S. Miller
2005-01-26 9:08 ` [Bridge] " Bart De Schuymer
2005-01-26 9:08 ` Bart De Schuymer
2005-01-26 23:49 ` [Bridge] Re: [PATCH/RFC] Reduce call chain length in netfilter Patrick McHardy
2005-01-26 23:49 ` Patrick McHardy
2005-01-27 7:18 ` [Bridge] " David S. Miller
2005-01-27 7:18 ` David S. Miller
2005-01-27 17:50 ` [Bridge] " Patrick McHardy
2005-01-27 17:50 ` Patrick McHardy
2005-01-27 19:47 ` [Bridge] " David S. Miller
2005-01-27 19:47 ` David S. Miller
2005-01-27 21:16 ` [Bridge] " Bart De Schuymer
2005-01-27 21:16 ` Bart De Schuymer
2005-01-27 22:48 ` [Bridge] " Patrick McHardy
2005-01-27 22:48 ` Patrick McHardy
2005-01-27 23:24 ` [Bridge] " David S. Miller
2005-01-27 23:24 ` David S. Miller
2005-01-28 0:08 ` [Bridge] " Patrick McHardy
2005-01-28 0:08 ` Patrick McHardy
2005-01-28 0:29 ` [Bridge] " Rusty Russell
2005-01-28 0:29 ` Rusty Russell
2005-01-28 1:10 ` [Bridge] " David S. Miller
2005-01-28 1:10 ` David S. Miller
2005-01-28 1:32 ` [Bridge] " Rusty Russell
2005-01-28 1:32 ` Rusty Russell
2005-01-28 1:35 ` [Bridge] " Patrick McHardy
2005-01-28 1:35 ` Patrick McHardy
2004-12-18 6:27 do_IRQ: stack overflow: 872 Crazy AMD K7
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=p73zn0ccaee.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=snort2004@mail.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.