From: William Lee Irwin III <wli@holomorphy.com>
To: Paul Larson <plars@austin.ibm.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, haveblue@us.ibm.com
Subject: Re: [OOPS] 2.5.27 - __free_pages_ok()
Date: Mon, 22 Jul 2002 15:52:51 -0700 [thread overview]
Message-ID: <20020722225251.GG919@holomorphy.com> (raw)
In-Reply-To: <1027377273.5170.37.camel@plars.austin.ibm.com>
On Mon, 2002-07-22 at 15:19, Dave Hansen wrote:
>> I was hitting the same thing on a Netfinity 8500R/x370. The problem
>> was an old compiler (egcs 2.91-something). It was triggered by a few
>> different things, including kernprof and dcache_rcu.
On Mon, Jul 22, 2002 at 05:34:32PM -0500, Paul Larson wrote:
> Well, it was a redhat box. Just to be certain, I made sure to use kgcc
> and it still hung on boot, but kgcc is egcs-2.91.66 19990314/Linux
> (egcs-1.1.2 release). If it would be helpful, I'll try compiling my
> kernel on a debian box tomorrow and booting with that.
ISTR this compiler having code generation problems. I think trying to
reproduce this with a working i386 compiler is in order, e.g. debian's
2.95.4 or some similarly stable version.
Cheers,
Bill
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-07-22 22:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 19:34 Paul Larson
2002-07-22 20:03 ` Rik van Riel
2002-07-22 20:05 ` Rik van Riel
2002-07-22 22:34 ` Paul Larson
2002-07-22 22:52 ` William Lee Irwin III [this message]
2002-07-23 17:40 ` Paul Larson
2002-07-23 17:48 ` Dave Hansen
2002-07-23 17:49 ` William Lee Irwin III
2002-07-23 19:02 ` Paul Larson
2002-07-23 19:57 ` Paul Larson
2002-07-23 20:01 ` Rik van Riel
2002-07-23 0:18 ` Alan Cox
2002-07-22 23:37 ` Thunder from the hill
2002-07-23 11:34 ` Paul Larson
2002-07-22 22:37 ` Paul Larson
2002-07-22 20:19 ` Dave Hansen
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=20020722225251.GG919@holomorphy.com \
--to=wli@holomorphy.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=plars@austin.ibm.com \
--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