From: Andrea Arcangeli <andrea@suse.de>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Jan Hubicka <jh@suse.cz>, Keith Owens <kaos@ocs.com.au>
Subject: Re: Panic from 2.4.19-pre9-aa2
Date: Fri, 7 Jun 2002 01:53:12 +0200 [thread overview]
Message-ID: <20020606235312.GF1004@dualathlon.random> (raw)
In-Reply-To: <80230000.1023396285@flay> <20020606212028.GA1004@dualathlon.random> <83910000.1023400420@flay> <20020606231521.GB1004@dualathlon.random> <103110000.1023407113@flay>
On Thu, Jun 06, 2002 at 04:45:13PM -0700, Martin J. Bligh wrote:
> > At first glance this seems a miscompilation, a compiler bug, not bug in
> > 2.4.19pre9aa2 (this clearly explains why you're the only one reproducing
> > this weird oops). it even sounds like ksymoops is buggy, ksymoops had to
> > say c0147dad (+7d), not c0147dac and +7c (maybe you compiled ksymoops
> > with the same compiler of the kernel? If not Keith should have a look
> > here).
> >
> > What compiler are you using? Maybe 2.96?
>
> Errm .... Redhat 6.2 default ... egcs-2.91.66 .... time to upgrade ?? ;-) ;-)
hmm, that's a bad news, that's egcs 1.1.2, strange, it was supposed to
be safe oh well, but OTOH I'm not too surprised nobody noticed because I
doubt many people compiles with 2.4 with egcs still.
> Pah ... reinstalling these machines is a pain in the ass .... ;-)
Could you try compiling in another machine with a gcc 2.95 and see if
you can still reproduce it? If it's a race condition and a real kernel
bug it should be easily reproducible no matter the compiler.
Andrea
next prev parent reply other threads:[~2002-06-06 23:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 20:44 Panic from 2.4.19-pre9-aa2 Martin J. Bligh
2002-06-06 21:20 ` Andrea Arcangeli
2002-06-06 21:53 ` Martin J. Bligh
2002-06-06 23:15 ` Andrea Arcangeli
2002-06-06 23:45 ` Martin J. Bligh
2002-06-06 23:53 ` Andrea Arcangeli [this message]
2002-06-06 23:31 ` Hugh Dickins
2002-06-07 1:33 ` Keith Owens
2002-06-06 23:18 ` Martin J. Bligh
2002-06-06 23:36 ` Andrea Arcangeli
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=20020606235312.GF1004@dualathlon.random \
--to=andrea@suse.de \
--cc=Martin.Bligh@us.ibm.com \
--cc=jh@suse.cz \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
/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.