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

-------- Original-Nachricht --------
> Datum: Fri, 1 Feb 2008 19:11:19 +0000
> Von: Mel Gorman <>
> An: Gerhard Pircher <>
> CC:
> Betreff: Re: Commit for mm/page_alloc.c breaks boot process on my machine

> 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
> difference.
> 1. Is there any chance that all of your memory is not being properly
>    initialised?
Do you mean uninitialized hardware? That shouldn't be a problem, since
older kernels (e.g. 2.6.19 with platform patches for arch/ppc) are running

> 2. Any chance of seeing a dmesg log?
That's a little bit of a problem. The kernel log in memory doesn't show
any kernel oops, but is also fragmented (small fragments seem to have been
overwritten with 0x0). I could extract it by using the U-boot firmware,
but that takes some time, as the serial console is not yet working.
I tried to boot the kernel with 512MB and 1.5GB RAM. The amount of memory
doesn't have any effect and the amount of memory is reported correctly
in the kernel 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?
Well, I can't answer this question. The kernel currently locks up when
loading the INIT program. But that is another problem (I still have to
bisect it) and doesn't seem to be related to this problem.

Thanks for your help!

GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung:

  reply	other threads:[~2008-02-01 20:05 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
2008-02-01 20:05   ` Gerhard Pircher [this message]
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).