All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cbf123@mail.usask.ca>
To: Vivek Goyal <vgoyal@redhat.com>, Haren Myneni <hbabu@us.ibm.com>,
	kexec@lists.infradead.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: visible memory seems wrong in kexec crash dump kernel
Date: Thu, 11 Jul 2013 14:55:23 -0600	[thread overview]
Message-ID: <51DF1BBB.5060904@mail.usask.ca> (raw)

Hi,

I'm running 2.6.34 with kexec 2.0.1 on a Freescale p5020-based system with 8GB of memory.  (It's an embedded system and I can't do much about the fact that it's using older software.)

I booted the original kernel with "crashkernel=224M@32M" in the boot args.  I then loaded the crash kernel with:

./kexec -p vmlinux.kontron.strip --append="root=/dev/mtdblock0 rw rootfstype=jffs2 panic=5 1 maxcpus=1 noirqdistrib reset_devices"

Then I triggered a crash:

echo 1 > /proc/sys/kernel/sysrq
echo c > /proc/sysrq-trigger


When the crash kernel came up, it had "elfcorehdr=48392K savemaxmem=8192M" in the kernel boot args, and "free" showed the system as having 7908652 KB of total memory instead of the expected 224MB.

Do I need to manually specify some options to kexec in order to preserve the memory of the original system?  I seem to recall that kexec did this automatically on x86 systems.

Thanks,
Chris


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

WARNING: multiple messages have this Message-ID (diff)
From: Chris Friesen <cbf123@mail.usask.ca>
To: Vivek Goyal <vgoyal@redhat.com>, Haren Myneni <hbabu@us.ibm.com>,
	<kexec@lists.infradead.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	<linuxppc-dev@lists.ozlabs.org>
Subject: visible memory seems wrong in kexec crash dump kernel
Date: Thu, 11 Jul 2013 14:55:23 -0600	[thread overview]
Message-ID: <51DF1BBB.5060904@mail.usask.ca> (raw)

Hi,

I'm running 2.6.34 with kexec 2.0.1 on a Freescale p5020-based system with 8GB of memory.  (It's an embedded system and I can't do much about the fact that it's using older software.)

I booted the original kernel with "crashkernel=224M@32M" in the boot args.  I then loaded the crash kernel with:

./kexec -p vmlinux.kontron.strip --append="root=/dev/mtdblock0 rw rootfstype=jffs2 panic=5 1 maxcpus=1 noirqdistrib reset_devices"

Then I triggered a crash:

echo 1 > /proc/sys/kernel/sysrq
echo c > /proc/sysrq-trigger


When the crash kernel came up, it had "elfcorehdr=48392K savemaxmem=8192M" in the kernel boot args, and "free" showed the system as having 7908652 KB of total memory instead of the expected 224MB.

Do I need to manually specify some options to kexec in order to preserve the memory of the original system?  I seem to recall that kexec did this automatically on x86 systems.

Thanks,
Chris

             reply	other threads:[~2013-07-11 20:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 20:55 Chris Friesen [this message]
2013-07-11 20:55 ` visible memory seems wrong in kexec crash dump kernel Chris Friesen
2013-07-11 21:22 ` Chris Friesen
2013-07-11 21:22   ` Chris Friesen
2013-07-11 22:46   ` Chris Friesen
2013-07-11 22:46     ` Chris Friesen
2013-07-12  1:21   ` Michael Ellerman
2013-07-12  1:21     ` Michael Ellerman
2013-07-12 21:08     ` Chris Friesen
2013-07-12 21:08       ` Chris Friesen
2013-07-12 22:59       ` Chris Friesen
2013-07-12 22:59         ` Chris Friesen
2013-07-13  6:30         ` Chris Friesen
2013-07-13  6:30           ` Chris Friesen
2013-07-14  4:36           ` Michael Ellerman
2013-07-14  4:36             ` Michael Ellerman
2013-07-14  5:26             ` Benjamin Herrenschmidt
2013-07-14  5:26               ` Benjamin Herrenschmidt
2013-07-14 23:08               ` Chris Friesen
2013-07-14 23:08                 ` Chris Friesen
2013-07-14 23:11                 ` Benjamin Herrenschmidt
2013-07-14 23:11                   ` Benjamin Herrenschmidt
2013-07-29 23:10           ` Scott Wood
2013-07-29 23:10             ` Scott Wood
2013-07-31 16:40             ` Friesen, Christopher
2013-07-31 16:40               ` Friesen, Christopher
2013-07-31 16:50               ` Scott Wood
2013-07-31 16:50                 ` Scott Wood

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=51DF1BBB.5060904@mail.usask.ca \
    --to=cbf123@mail.usask.ca \
    --cc=benh@kernel.crashing.org \
    --cc=hbabu@us.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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.