public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Lisa Mitchell <lisa.mitchell@hp.com>
To: Cliff Wickman <cpw@sgi.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"d.hatayama@jp.fujitsu.com" <d.hatayama@jp.fujitsu.com>,
	"kumagai-atsushi@mxc.nes.nec.co.jp"
	<kumagai-atsushi@mxc.nes.nec.co.jp>
Subject: Re: [PATCH v2] makedumpfile: request the kernel do page scans
Date: Wed, 16 Jan 2013 05:51:11 -0700	[thread overview]
Message-ID: <1358340671.13097.990.camel@lisamlinux.fc.hp.com> (raw)
In-Reply-To: <1358338529.13097.987.camel@lisamlinux.fc.hp.com>

On Wed, 2013-01-16 at 05:15 -0700, Lisa Mitchell wrote:

> Cliff I tried your patch above on makedumpfile v1.5.1 (built dynamically
> on the same DL980 I was running the test on), with all the RHEL 6
> versions of kernel patches you gave me from 1207 plus the kernel patch
> to kexec recommended for makedumpfile v1.5.1 built on top of a
> preliminary RHEL 6.4 kernel source (higher patch level of 2.6.32
> kernel), this time on a 1 TB Memory system (We have lost access to a 4
> TB Memory system for some time, now). On this same system, regular
> Makedumpfile v1.5.1 worked fine to produce a dump. But the Makedumpfile
> with the patches above could not even start the dump, and printed:
> 
> Saving vmcore-dmesg.txt
> Saved vmcore-dmesg.txt
> PL_REQUEST_MEMMAP returned -1
> Restarting system.
> 
> This happened with both a crashkernel size=200M that would have invoked
> cyclic buffer mode, and also with a larger one, 384M that should not
> have needed cyclic mode.  I had no cyclic buffer mode set or turned off
> in the makedumpfile command line, just recording memory usage with:
> 
> core_collector makedumpfile -c --message-level 31 -d 31
> debug_mem_level 2
> 
> 


I got a slightly different error message when I tried the test again on
the same system, setting crashkernel=512M, and adding --non-cyclic to
the makedumpfile command line.  It was:

Saving vmcore-dmesg.txt
Saved vmcore-dmesg.txt
Checking for memory holes          : [100 %]
 PL_REQUEST_MEMMAP returned -1
create_2nd_bitmap: Can't exclude unnecessary pages.



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

  reply	other threads:[~2013-01-16 16:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 16:20 [PATCH v2] makedumpfile: request the kernel do page scans Cliff Wickman
2013-01-16 12:15 ` Lisa Mitchell
2013-01-16 12:51   ` Lisa Mitchell [this message]
2013-01-16 17:50   ` Cliff Wickman
  -- strict thread matches above, loose matches on Subject: below --
2012-11-21 20:06 Cliff Wickman
2012-11-22  1:43 ` Hatayama, Daisuke
2012-11-22 14:07   ` HATAYAMA Daisuke
2013-01-07 13:39 ` Cliff Wickman
2013-01-09 15:09   ` HATAYAMA Daisuke
     [not found]     ` <20130111223034.GA2154@sgi.com>
2013-01-17  1:38       ` HATAYAMA Daisuke

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=1358340671.13097.990.camel@lisamlinux.fc.hp.com \
    --to=lisa.mitchell@hp.com \
    --cc=cpw@sgi.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=kexec@lists.infradead.org \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox