From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, y-goto@jp.fujitsu.com
Subject: Re: sparc64 bootup regression...
Date: Wed, 30 Apr 2008 09:30:52 +0200 [thread overview]
Message-ID: <20080430073052.GA11015@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20080430161540.bfff2c45.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, Apr 30, 2008 at 04:15:40PM +0900, KAMEZAWA Hiroyuki wrote:
> On Tue, 29 Apr 2008 23:38:32 -0700
> Andrew Morton <akpm@linux-foundation.org> wrote:
> > On Tue, 29 Apr 2008 23:12:41 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
> > > This commit causes bootup failures on sparc64:
> > >
> > > commit 86f6dae1377523689bd8468fed2f2dd180fc0560
> > > Author: Yasunori Goto <y-goto@jp.fujitsu.com>
> > > Date: Mon Apr 28 02:13:33 2008 -0700
> > >
> > > memory hotplug: allocate usemap on the section with pgdat
> > Thanks. Does a straightforward revert fix it? If so, we could do that while heads
> > are being scratched.
That patch broke the s390 port to SPARSEMEM (not upstream yet) as well.
Reverting it does help.
However increasing SECTION_SIZE_BITS to 25 (was: 20) does help too.
But that doesn't seem to help on sparc64 where it is already 30, strange.
> How about this ? If this is messy (or doesn't work), Goto-san will rework
> his own patch by himself. (this patch is against -mm but I think no HUNK to
> git tree)
>
> ==
> This kind of page allocation, which specifies the address range,
> can fail easily.
>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiruyo@jp.fujitsu.com>
>
> Index: mm-2.6.25-mm1/mm/sparse.c
> ===================================================================
> --- mm-2.6.25-mm1.orig/mm/sparse.c
> +++ mm-2.6.25-mm1/mm/sparse.c
> @@ -264,10 +264,16 @@ static unsigned long *__init sparse_earl
> * To solve above issue, this collects all usemap on the same section
> * which has pgdat.
> */
> +#ifdef CONFIG_NUMA /* contig_page_data for !NUMA case is not good to do this */
> section_nr = pfn_to_section_nr(__pa(pgdat) >> PAGE_SHIFT);
> usemap = alloc_bootmem_section(usemap_size(), section_nr);
> if (usemap)
> return usemap;
> +#endif
> + /* above allocation can fail. */
> + usemap = alloc_bootmem_node(NODE_DATA(nid), usemap_size());
> + if (usemap)
> + return usemap;
>
> /* Stupid: suppress gcc warning for SPARSEMEM && !NUMA */
> nid = 0;
Fixes it on s390 at least.
next prev parent reply other threads:[~2008-04-30 7:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 6:12 David Miller
2008-04-30 6:38 ` Andrew Morton
2008-04-30 6:46 ` KAMEZAWA Hiroyuki
2008-04-30 7:15 ` KAMEZAWA Hiroyuki
2008-04-30 7:25 ` David Miller
2008-04-30 7:33 ` KAMEZAWA Hiroyuki
2008-04-30 12:53 ` Yasunori Goto
2008-06-03 22:14 ` David Miller
2008-06-04 5:05 ` Yasunori Goto
2008-04-30 7:30 ` Heiko Carstens [this message]
2008-04-30 7:44 ` KAMEZAWA Hiroyuki
2008-04-30 7:45 ` Heiko Carstens
2008-04-30 7:19 ` David Miller
2008-05-07 22:09 ` Rafael J. Wysocki
2008-05-07 22:25 ` Andrew Morton
2008-05-07 22:32 ` Rafael J. Wysocki
2008-05-07 22:46 ` David Miller
2008-05-01 5:13 ` powerpc boot regression Tony Breeds
2008-05-01 14:51 ` Badari Pulavarty
2008-05-01 19:01 ` Geoff Levand
2008-05-01 23:07 ` Tony Breeds
2008-05-03 12:05 ` Yasunori Goto
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=20080430073052.GA11015@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=y-goto@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome