All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Paul Larson <plars@austin.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: [OOPS] 2.5.27 - __free_pages_ok()
Date: Mon, 22 Jul 2002 13:19:37 -0700	[thread overview]
Message-ID: <3D3C68D9.1020608@us.ibm.com> (raw)
In-Reply-To: 1027366468.5170.26.camel@plars.austin.ibm.com

Paul Larson wrote:
> Encountered this first with Linux-2.5.25+rmap and it looks like the
> problem also slipped into 2.5.27.  The same machine boots fine with a
> vanilla 2.5.25 or 2.5.26, but gets this on boot with rmap.  The machine
> is an 8-way PIII-700.

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.

-- 
Dave Hansen
haveblue@us.ibm.com


WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Paul Larson <plars@austin.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: [OOPS] 2.5.27 - __free_pages_ok()
Date: Mon, 22 Jul 2002 13:19:37 -0700	[thread overview]
Message-ID: <3D3C68D9.1020608@us.ibm.com> (raw)
In-Reply-To: 1027366468.5170.26.camel@plars.austin.ibm.com

Paul Larson wrote:
> Encountered this first with Linux-2.5.25+rmap and it looks like the
> problem also slipped into 2.5.27.  The same machine boots fine with a
> vanilla 2.5.25 or 2.5.26, but gets this on boot with rmap.  The machine
> is an 8-way PIII-700.

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.

-- 
Dave Hansen
haveblue@us.ibm.com

--
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/

  parent reply	other threads:[~2002-07-22 20:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-22 19:34 [OOPS] 2.5.27 - __free_pages_ok() Paul Larson
2002-07-22 20:03 ` Rik van Riel
2002-07-22 20:03   ` Rik van Riel
2002-07-22 20:05   ` Rik van Riel
2002-07-22 20:05     ` Rik van Riel
2002-07-22 22:34     ` Paul Larson
2002-07-22 22:34       ` Paul Larson
2002-07-22 22:52       ` William Lee Irwin III
2002-07-22 22:52         ` William Lee Irwin III
2002-07-23 17:40         ` Paul Larson
2002-07-23 17:40           ` Paul Larson
2002-07-23 17:48           ` Dave Hansen
2002-07-23 17:48             ` Dave Hansen
2002-07-23 17:49           ` William Lee Irwin III
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 19:57                 ` Paul Larson
2002-07-23 20:01                 ` Rik van Riel
2002-07-23 20:01                   ` Rik van Riel
2002-07-23  0:18       ` Alan Cox
2002-07-23  0:18         ` Alan Cox
2002-07-22 23:37         ` Thunder from the hill
2002-07-22 23:37           ` Thunder from the hill
2002-07-23 11:34         ` Paul Larson
2002-07-23 11:34           ` Paul Larson
2002-07-22 22:37     ` Paul Larson
2002-07-22 20:19 ` Dave Hansen [this message]
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=3D3C68D9.1020608@us.ibm.com \
    --to=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=plars@austin.ibm.com \
    /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.