From: Will Schmidt <will_schmidt@vnet.ibm.com>
To: Mel Gorman <mel@skynet.ie>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Memory Management List <linux-mm@kvack.org>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: pseries (power3) boot hang (pageblock_nr_pages==0)
Date: Wed, 21 Nov 2007 15:55:11 -0600 [thread overview]
Message-ID: <1195682111.4421.23.camel@farscape.rchland.ibm.com> (raw)
Hi Folks,
I've been seeing a boot hang/crash on power3 systems for a few weeks.
(hangs on a 270, drops to SP on a p610). This afternoon I got around
to tracking it down to the changes in
commit d9c2340052278d8eb2ffb16b0484f8f794def4de
Do not depend on MAX_ORDER when grouping pages by mobility
cpu 0x0: Vector: 100 (System Reset) at [c00000006e803ae0]
pc: c00000000009bf50: .setup_per_zone_pages_min+0x298/0x34c
lr: c00000000009be38: .setup_per_zone_pages_min+0x180/0x34c
[c00000006e803e20] c0000000005e3898 .init_per_zone_pages_min+0x80/0xa0
[c00000006e803ea0] c0000000005c9c04 .kernel_init+0x214/0x3d8
[c00000006e803f90] c000000000026cac .kernel_thread+0x4c/0x68
I narrowed it down to the for loop within setup_zone_migrate_reserve(),
called by setup_per_zone_pages_min(). The loop spins forever due to
pageblock_nr_pages being 0.
I imagine this would be properly fixed with something similar to the
change for iSeries. Depending on how obvious, quick and easy it is for
the experts to come up with a proper fix, I'll be able to do additional
debug and hacking after turkey-day. :-)
For the moment, I've hacked it with the following patch. (tested on
both the 270 and the p610):
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -2454,6 +2454,9 @@ static void setup_zone_migrate_reserve(struct zone
*zone)
reserve = roundup(zone->pages_min, pageblock_nr_pages) >>
pageblock_order;
+/* this is a cheap and dirty bailout, probally not a proper fix. */
+ if (pageblock_nr_pages==0) return;
+
for (pfn = start_pfn; pfn < end_pfn; pfn += pageblock_nr_pages)
{
if (!pfn_valid(pfn))
continue;
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2007-11-21 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 21:55 Will Schmidt [this message]
2007-11-21 22:03 ` Mel Gorman
2007-11-26 19:35 ` Will Schmidt
2007-11-28 10:52 ` Mel Gorman
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=1195682111.4421.23.camel@farscape.rchland.ibm.com \
--to=will_schmidt@vnet.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mel@skynet.ie \
--cc=sfr@canb.auug.org.au \
/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