All of lore.kernel.org
 help / color / mirror / Atom feed
From: wille <junk@willeweb.com>
To: kexec@lists.infradead.org
Subject: kexec: Overlapping memory segments error
Date: Thu, 20 Jan 2011 13:14:27 -0700	[thread overview]
Message-ID: <201101201314.27153.junk@willeweb.com> (raw)

I am running a minimal system with a stripped down x86 2.6.32 Linux kernel.  
From this environment I kexec to an Ubuntu Lucid i386 2.6.32 kernel.  This 
works fine on *most* hardware, but on some machines the kexec -l fails with 
overlapping memory segments.

First I used the kexec which comes with the Lucid i386 distro (kexec-tools 
2.0.1 released 13th August 2009).  Then I built kexec from the head of the 
git tree, which includes the patch "kexec: fix /sys/firmware/memmap memory 
range overlaps".  I was hopeful this patch would fix my problem, but it 
still fails with an "Overlapping memory segments" error.

As a specific example, on a Dell Latitude E6410 (which uses an Intel i7 
processor) the kexec -l fails with the following messages:

    setup_linux_vesafb: 640x480x16 @ e1000000 +12c000
    Overlapping memory segments at 0x7ffff000

One final clue: if I do the same kexec -l, but without the --initrd option I 
don't get the "Overlapping memory segments..." message, but of course 
without an initrd the system doesn't boot.

Any ideas?

-wille

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

             reply	other threads:[~2011-01-20 20:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 20:14 wille [this message]
2011-01-20 20:26 ` kexec: Overlapping memory segments error Cliff Wickman

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=201101201314.27153.junk@willeweb.com \
    --to=junk@willeweb.com \
    --cc=kexec@lists.infradead.org \
    /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.