public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: lists@corewars.org
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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: Thu, 12 Sep 2002 13:48:00 +0200	[thread overview]
Message-ID: <20020912134800.A1068@corewars.org> (raw)
In-Reply-To: <1031766496.5832.5.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Wed, Sep 11, 2002 at 06:48:16PM +0100

Hm, actually I am.

And from the oops traces, the offending intruction always seems to be a
pop.

I'll upgrade and try again.

Thanks,
Sapan

On Wed, Sep 11, 2002 at 06:48:16PM +0100, Alan Cox wrote:
> 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
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

      reply	other threads:[~2002-09-12 11:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-03 17:07 2.4.19 OOPS [Repost] 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
2002-09-12 11:48           ` lists [this message]

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=20020912134800.A1068@corewars.org \
    --to=lists@corewars.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.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