From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: lists@corewars.org
Cc: Andrea Arcangeli <andrea@suse.de>,
riel@conectiva.com.br, Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.19 OOPS [Repost]
Date: 11 Sep 2002 18:48:16 +0100 [thread overview]
Message-ID: <1031766496.5832.5.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020911191614.A2078@corewars.org>
On Wed, 2002-09-11 at 18:16, lists@corewars.org wrote:
> Just in case this might shed some more light on the problem...
> I recompiled the kernel with frame pointers about a week ago, and I
> didn't face a single oops till today morning, when I recompiled the
> kernel without frame-pointers and I've been getting the same
> oopses all day.
>
Are you using gcc 3.0.x or an early gcc 3.1.x. There are bugs in those
where they write below the stack pointer which means an IRQ will corrupt
stuff. Turning on frame pointers might well hide this
next prev parent reply other threads:[~2002-09-11 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 17:07 lists
2002-09-04 18:11 ` lists
2002-09-04 18:22 ` Andrea Arcangeli
2002-09-05 20:32 ` lists
2002-09-11 17:16 ` lists
2002-09-11 17:48 ` Alan Cox [this message]
2002-09-12 11:48 ` lists
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=1031766496.5832.5.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@corewars.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
/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®