public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: show_mem panic
Date: Wed, 10 Mar 2004 18:45:43 +0000	[thread overview]
Message-ID: <20040310184543.GA9355@sgi.com> (raw)
In-Reply-To: <20040310180923.GA9032@sgi.com>

On Wed, Mar 10, 2004 at 10:09:23AM -0800, Jesse Barnes wrote:
> It's in the inner loop looking at the pages in the first node's
> node_mem_map.  I'm almost positive that this code worked in the past,
> Andreas, when you reproduced this on a tiger machine was it with
> CONFIG_VIRTUAL_MEM_MAP enabled?

Bjorn just informed me that John Marvin was taking a look at this.  It
looks like we need to make sure the page we're about to look at is
valid for the virtual mem map case.  And btw, it looks like the contig
version of show_mem should be fixed: total shouldn't include
non-existant pages (if we add pfn_valid checks to both the discontig and
contig versions that should be an easy fix).

Jesse

  reply	other threads:[~2004-03-10 18:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10 18:09 show_mem panic Jesse Barnes
2004-03-10 18:45 ` Jesse Barnes [this message]
2004-03-10 22:54 ` Andreas Schwab

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=20040310184543.GA9355@sgi.com \
    --to=jbarnes@sgi.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox