All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sachin P. Sant" <sachinp@in.ibm.com>
To: Vivek Goyal <vgoyal@redhat.com>, bwalle@suse.de
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [mm] Crashkernel memory reservation fails with 2.6.24-rc8-mm1
Date: Tue, 05 Feb 2008 12:09:30 +0530	[thread overview]
Message-ID: <47A804A2.5020208@in.ibm.com> (raw)
In-Reply-To: <47A7F53C.8090606@in.ibm.com>

Sachin P. Sant wrote:
> Bernhard Walle wrote:
>> * Vivek Goyal <vgoyal@redhat.com> [2008-02-04 19:38]:  
>>> Bernahard, any idea who is the competitor here?     
>> Hm ..., can you boot the kernel without crashkernel= and provide the
>> /proc/iomem?   
> Attached is the /proc/iomem output with and without crashkernel
> parameter.
>
> Adding debug gives this extra information.
>
> hm, page 02a9d000 reserved twice.
> crashkernel reservation failed - memory is in use
>
> Will try to add more debug statements.
Hm . no problem with 2.6.24-mm1.

early res: 4 [9dc00-a0bff] EBDA
early res: 5 [8000-11fff] PGTABLE
Reserving 128MB of memory at 32MB for crashkernel (System RAM: 9088MB)
 [ffffe20000000000-ffffe200001fffff] PMD ->ffff810001200000 on node 0

# cat /proc/iomem
......
 008b8000-0099dc8b : Kernel bss
  02000000-09ffffff : Crash kernel
c7fcae00-c7fcf7ff : ACPI Tables
.....

Thanks
-Sachin


  reply	other threads:[~2008-02-05  6:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 16:11 [mm] Crashkernel memory reservation fails with 2.6.24-rc8-mm1 Sachin P. Sant
2008-02-04 16:11 ` Sachin P. Sant
2008-02-04 18:38 ` Vivek Goyal
2008-02-04 18:38   ` Vivek Goyal
2008-02-04 19:35   ` Bernhard Walle
2008-02-04 19:35     ` Bernhard Walle
2008-02-05  5:33     ` Sachin P. Sant
2008-02-05  5:33       ` Sachin P. Sant
2008-02-05  6:39       ` Sachin P. Sant [this message]
2008-02-05  8:09       ` Bernhard Walle
2008-02-05  8:09         ` Bernhard Walle

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=47A804A2.5020208@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=bwalle@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.