All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bob Picco" <bob.picco@hp.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: john stultz <johnstul@us.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Sripathi Kodi <sripathik@in.ibm.com>,
	Bernhard Walle <bwalle@suse.de>,
	"Eric W. Biederman"@redhat.com, acme@redhat.com,
	apw@shadowen.org
Subject: Re: [BUG] sysrq-m oops
Date: Thu, 7 Jun 2007 14:21:22 -0400	[thread overview]
Message-ID: <20070607182122.GE11999@localhost> (raw)
In-Reply-To: <4668276E.4030504@redhat.com>

Chuck Ebbert wrote:	[Thu Jun 07 2007, 11:42:38AM EDT]
> On 06/06/2007 08:27 PM, john stultz wrote:
> > Hey All,
> > 	With 2.6.21 and the current -git, we're seeing the following oops when
> > we try sysrq-m:
> > 
> 
> It's here in arch/x86_64/mm/init.c::show_mem():
> 
>         for_each_online_pgdat(pgdat) {
>                for (i = 0; i < pgdat->node_spanned_pages; ++i) {
This is probably with sparsemem? I'm working with acme@redhat.com to
test a patch. Basically you need to validate the pfn because it
could be in a hole. Most arches which support sparsemem perform this
check.

			if (!pfn_valid(pgdat->node_start_pfn + i))
				continue;
bob
>                         page = pfn_to_page(pgdat->node_start_pfn + i);
>                         total++;
>  ======>                if (PageReserved(page))
>                                 reserved++;
>                         else if (PageSwapCache(page))
>                                 cached++;
>                         else if (page_count(page))
>                                 shared += page_count(page) - 1;
>                }
>         }
> 
> page is completely bogus (it's 0x0000000003480000)
> -
> 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:[~2007-06-07 18:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07  0:27 [BUG] sysrq-m oops john stultz
2007-06-07 15:42 ` Chuck Ebbert
2007-06-07 18:21   ` Bob Picco [this message]
2007-06-07 19:54     ` john stultz
2007-06-08  1:00       ` Bob Picco
2007-06-08 16:07         ` Andy Whitcroft
2007-06-07 20:39     ` Andy Whitcroft

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=20070607182122.GE11999@localhost \
    --to=bob.picco@hp.com \
    --cc="Eric W. Biederman"@redhat.com \
    --cc=acme@redhat.com \
    --cc=apw@shadowen.org \
    --cc=bwalle@suse.de \
    --cc=cebbert@redhat.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sripathik@in.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.