kexec+kdump + vmcoreinfo patch

Neil Horman nhorman at redhat.com
Mon Aug 27 13:54:23 EDT 2007


On Mon, Aug 27, 2007 at 01:02:53PM -0400, Don Zickus wrote:
> On Mon, Aug 27, 2007 at 12:55:38PM -0400, Neil Horman wrote:
> > > crashkernel=64M at 16M
> > > 
> > Hmm, well that should be enough.  looking at your log, it appears as though you
> > have a 512k chunk allocatable, which should seem sufficient to go on a little
> > longer.  The fact that your not seems to indicate that you are allocating a
> > suspiciously large single chunk of ram.  I'd configure your initramfs to drop to
> > a shell prompt before it sets up lp0.  Then you can step through the actions of
> > the init script and monitor the contents of /proc/slabinfo to get an idea of
> > whats eating up all your lowmem prior to the oom kill.
> > 
> > Neil
> > 
> 
> <snipped from Randy's output>
> 
> Out of memory: kill process 680 (boot) score 309 or a child
> Killed process 701 (S01boot.udev)
> 
> Heh, it's udev again.  What a surprise! </sarcasm>
> 
> Neil, didn't we solve this with an init 1 or something (ignoring the whole
> busybox thing).
> 
I don't recall, but that could well have been prior to my involvement in the
project.  I can tell you that I don't run udevd in my initramfs for kdump, and
I've never seen this particular oom-kill before, so there certainly seems to be
some level of correlation there.

Regards
Neil

> Cheers,
> Don
> 

-- 
/***************************************************
 *Neil Horman
 *Software Engineer
 *Red Hat, Inc.
 *nhorman at redhat.com
 *gpg keyid: 1024D / 0x92A74FA1
 *http://pgp.mit.edu
 ***************************************************/



More information about the kexec mailing list