LKML Archive on
help / color / mirror / Atom feed
From: Mel Gorman <>
To: Gerhard Pircher <>
Subject: Re: Commit for mm/page_alloc.c breaks boot process on my machine
Date: Fri, 1 Feb 2008 19:11:19 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On (01/02/08 19:42), Gerhard Pircher didst pronounce:
> I'm trying to get the 2.6.24 Linux kernel booting on my AmigaOne machine
> (it's a desktop PowerPC G4 machine with 1.5GB RAM). I have written the
> device tree and platform setup files for arch/powerpc, which seem to be
> working so far.
> Kernel version 2.6.24-rc2 was booting fine with my patches until the
> kernel executes the INIT command. But kernel release v2.6.24 dies early
> during the boot process (even before the radeonfb driver initializes and
> outputs kernel messages). Bisecting revealed that this commit causes my
> machine to fail booting:
> (Revert "Bias the placement of kernel pages at lower PFNs")
> The machine boots fine, if I revert the patch. But I wonder what side
> effects this patch may have? Can somebody shed some light on this?

With this patch, early boot would use pages from lower PFNs. Without the
patch, it would use memory from higher PFNs. That is the only real

1. Is there any chance that all of your memory is not being properly
2. Any chance of seeing a dmesg log?
3. If you boot with the patch reverted and then do something to consume
all memory like build loads of kernel trees simultaneously, do you see
any problems?

Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

  reply	other threads:[~2008-02-01 19:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01 18:42 Commit for mm/page_alloc.c breaks boot process on my machine Gerhard Pircher
2008-02-01 19:11 ` Mel Gorman [this message]
2008-02-01 20:05   ` Gerhard Pircher
2008-02-01 20:25     ` Mel Gorman
2008-02-01 21:06       ` Gerhard Pircher
2008-02-04 10:42         ` Mel Gorman
2008-02-04 22:20           ` Gerhard Pircher
2008-02-04 23:30             ` Michael Ellerman
2008-02-05  0:01           ` Benjamin Herrenschmidt
2008-02-05 10:23             ` Mel Gorman
2008-02-05 20:50               ` Benjamin Herrenschmidt
2008-02-05  0:07         ` Benjamin Herrenschmidt
2008-02-05  0:06     ` Benjamin Herrenschmidt
2008-02-05 23:17       ` Gerhard Pircher

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).