All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Montgomery <bob.montgomery@hp.com>
To: Chandru <chandru@in.ibm.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: kdump: quad core Opteron
Date: Mon, 08 Dec 2008 16:35:16 -0700	[thread overview]
Message-ID: <1228779316.3428.367.camel@amd.troyhebe> (raw)
In-Reply-To: <200812082126.16680.chandru@in.ibm.com>

On Mon, 2008-12-08 at 15:56 +0000, Chandru wrote:

> Hi Bob,
> 
> This problem was recently reported on a LS42 blade and the patch given by you
> also resolved the issue here too.  However I made couple of changes to
> kexec-tools to ignore GART memory region and not have elf headers created to
> it.  This patch also seemed to work on a LS21.
> 
> Thanks,
> Chandru

Hi Chandru,

I tried your patch on kexec-tools, and I'm seeing a zero-length section
in /proc/vmcore (using readelf -e /proc/vmcore) right after the GART
hole:

/proc/iomem in the main kernel shows:
  01000000-08ffffff : Crash kernel 
  20000000-23ffffff : GART
cfe4e000-cfe55fff : ACPI Tables

And readelf -e /proc/vmcore in the kdump kernel shows:

Program Headers:
  Type           Offset             VirtAddr           PhysAddr
                 FileSiz            MemSiz              Flags  Align
...
  LOAD           0x000000000144d99c 0xffff810009000000 0x0000000009000000
                 0x0000000017000000 0x0000000017000000  RWE    0
  LOAD           0x000000001844d99c 0xffff810024000000 0x0000000024000000
                 0x00000000abe4e000 0x00000000abe4e000  RWE    0
  LOAD           0x00000000c429b99c 0xffff810024000000 0x0000000024000000
                 0x0000000000000000 0x0000000000000000  RWE    0
...

The first LOAD shown covers 09000000-20000000, the System RAM between
the Crash kernel and the GART.  
The next LOAD covers 24000000-cfe4e000, which is the System RAM between
the GART and the ACPI Tables.  So that all looks good.

Then the next LOAD is also at 24000000 with a 0 in the size fields.
I haven't had a chance to check the code yet.

Bob Montgomery



_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  parent reply	other threads:[~2008-12-08 23:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 12:51 kdump: quad core Opteron Chandru
2008-10-07 13:06 ` Bernhard Walle
2008-10-07 13:24 ` Vivek Goyal
2008-10-07 15:59   ` Bob Montgomery
2008-10-08 13:51     ` Chandru
2008-12-08 15:56     ` Chandru
2008-12-08 21:54       ` Vivek Goyal
2008-12-09 12:12         ` Chandru
2008-12-09 18:55           ` Bob Montgomery
2008-12-08 23:35       ` Bob Montgomery [this message]
2008-12-09  1:32         ` Neil Horman
2008-12-09 11:59         ` Chandru
2008-10-08 13:40   ` Chandru

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=1228779316.3428.367.camel@amd.troyhebe \
    --to=bob.montgomery@hp.com \
    --cc=chandru@in.ibm.com \
    --cc=kexec@lists.infradead.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.