From: Chandru <chandru@in.ibm.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>,
Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.28-rc9 panics with crashkernel=256M while booting
Date: Mon, 19 Jan 2009 13:41:58 +0530 [thread overview]
Message-ID: <200901191341.58437.chandru@in.ibm.com> (raw)
In-Reply-To: <1232128377.27278.69.camel@nimitz>
On Friday 16 January 2009 23:22:57 Dave Hansen wrote:
> Just looking at it, that calculation is OK. But, there was one in your
> dmesg that looked a page too long, like page 0x1001 instead of 0x1000.
> I'd find out how that happened.
That is a result of PFN_UP() in reserve_bootmem_node() for which we hit the
BUG_ON() eventually. Prior to calling reserve_bootmem_node() we have...
node_ar.end_pfn = node->node_end_pfn = PFN_DOWN(physbase+reserve_size).
Hence a PFN_UP() will raise the value of 'end'. The kernel has
CONFIG_PPC_64K_PAGES enabled in the config.
Chandru
next prev parent reply other threads:[~2009-01-19 8:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200812241325.49404.chandru@in.ibm.com>
2008-12-25 7:35 ` 2.6.28-rc9 panics with crashkernel=256M while booting Andrew Morton
2008-12-25 8:07 ` Andrew Morton
2008-12-26 0:59 ` Paul Mackerras
2008-12-29 21:36 ` Dave Hansen
2009-01-05 13:49 ` Chandru
2009-01-05 16:30 ` Dave Hansen
2009-01-07 12:58 ` Chandru
2009-01-07 17:25 ` Dave Hansen
2009-01-08 10:29 ` Chandru
2009-01-08 20:03 ` Dave Hansen
2009-01-09 11:07 ` Chandru
2009-01-15 8:05 ` Chandru
2009-01-16 12:16 ` Chandru
2009-01-16 17:52 ` Dave Hansen
2009-01-19 8:11 ` Chandru [this message]
2009-01-19 11:30 ` Chandru
2009-01-20 8:13 ` Chandru
2009-01-22 0:29 ` Dave Hansen
2009-01-22 8:20 ` Chandru
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=200901191341.58437.chandru@in.ibm.com \
--to=chandru@in.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).