From: Vivek Goyal <vgoyal@redhat.com>
To: Soumendu Satapathy <soumendu.satapathy@reldata.com>
Cc: Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: FW: 2.6.18 Fedora core kernel gives: "Overlapping memory segments at" error
Date: Tue, 23 Feb 2010 16:50:32 -0500 [thread overview]
Message-ID: <20100223215032.GG11930@redhat.com> (raw)
In-Reply-To: <32AB6BC050DF9E4E91868C4C3B7B6ABBB56926@lion.reldatainc.local>
On Tue, Feb 23, 2010 at 04:32:59PM -0500, Soumendu Satapathy wrote:
> Hi Vivek,
>
>
>
> Is it a bug? Its works for 2.6.27 but fails for 2.6.18 kernel. However I
> use the vmlinuz image as a capture kernel in case of 2.6.27 as it does
> not complain of relocatable kernel with it.
>
>
>
> I am using a vmlinux kernel image to load as it complains vmlinuz image
> for not being relocatable in case of 2.6.18.
>
>
>
> I get the following error:-
>
>
>
> Overlapping memory segments at 0x27f7000
>
> "sort_segments failed"
>
Can you post the output of "readelf -l vmlinux" just curious if vmlinux
is reporting somehow overlappig memory segments. But you seem to be
suggesting that that same vmlinux works with older version of kexec-tools?
If yes, then it sounds like we introduced some bug in newer version of
kexec-tools.
What is your environemnt? I mean what is your production kernel. Are you
running 2.6.18 as production kernel and trying out loading 2.6.27 and
2.6.18 as capture kernel, or you have 2.6.27 as production kernel and
trying out 2.6.27 and 2.6.18 as capture kernel. Not that it matters much
at this point of time, just curious.
So I would begin with trying to load 2.6.18 vmlinux with older version
of kexec-tools.
Is this 2.6.18 vmlinux relocatable?
Thanks
Vivek
>
>
>
>
> Thanks
>
> Soumendu
>
>
>
> From: Soumendu Satapathy
> Sent: Tuesday, February 23, 2010 11:10 AM
> To: Kexec Mailing List
> Subject: 2.6.18 Fedora core kernel gives: "Overlapping memory segments
> at" error
>
>
>
> This is my .config for the capture kernel.
>
>
>
> CONFIG_KEXEC=y
>
> CONFIG_CRASH_DUMP=y
>
> CONFIG_PHYSICAL_START=0x2000000
>
>
>
> I use crashkernel=64M@32M.
>
>
>
> Thanks
>
> Soumendu
>
>
>
> From: Soumendu Satapathy
> Sent: Tuesday, February 23, 2010 11:07 AM
> To: Kexec Mailing List
> Subject: 2.6.18 Fedora core kernel gives: "Overlapping memory segments
> at" error
>
>
>
> Hi there,
>
>
>
> When I use a 2.6.27 Fedora core I am able to load a capture kernel
> properly and it boots when the first kernel crashes.
>
> I am using a x86_64 platform and 2.6.27 Fedora core.
>
>
>
> I use crashkernel=64M@32M.
>
>
>
> But when I use a 2.6.18 in the same environment and settings as above, I
> get the following error when I load a capture kernel:-
>
>
>
> "Overlapping memory segments at" error
>
> "Sort segments failed"
>
>
>
> I found that the kernel segments overlap when loading them in the 64M
> memory reserved for the capture kernel. My system memory is MemTotal:
> 8037944 kB
>
>
>
> I am using kexec-tools-2.0.1 and the "cat /proc/iomem" o/p is as
> follows.
>
>
>
> 00000000-0009b3ff : System RAM
>
> 0009b400-0009ffff : reserved
>
> 000e4000-000fffff : reserved
>
> 00100000-cff6ffff : System RAM
>
> 00200000-006f0747 : Kernel code
>
> 006f0748-009b9b3f : Kernel data
>
> 00be2000-01219ea7 : Kernel bss
>
> 02000000-05ffffff : Crash kernel
>
> cff70000-cff77fff : ACPI Tables
>
> cff78000-cff7ffff : ACPI Non-volatile Storage
>
> cff80000-cfffffff : reserved
>
> d1000000-d11fffff : PCI Bus 0000:01
>
> d1000000-d10fffff : PCI Bus 0000:02
>
> d1000000-d107ffff : 0000:02:03.0
>
> d1080000-d10fffff : 0000:02:03.1
>
> d1100000-d11fffff : PCI Bus 0000:03
>
> d1100000-d113ffff : 0000:03:02.0
>
> d1140000-d117ffff : 0000:03:02.1
>
> d1200000-d12fffff : PCI Bus 0000:04
>
> d1200000-d12fffff : PCI Bus 0000:05
>
> d1200000-d120ffff : 0000:05:04.0
>
> d1300000-d13fffff : PCI Bus 0000:06
>
> d1300000-d13fffff : PCI Bus 0000:07
>
> d1300000-d130ffff : 0000:07:04.0
>
> d1400000-d14fffff : PCI Bus 0000:09
>
> d1400000-d141ffff : 0000:09:01.0
>
> d1500000-d15003ff : 0000:00:1f.1
>
> dd000000-dd000fff : 0000:00:01.0
>
> dd001000-dd00100f : 0000:00:1d.4
>
> dd001400-dd0017ff : 0000:00:1d.7
>
> dd001400-dd0017ff : ehci_hcd
>
> dd100000-dd3fffff : PCI Bus 0000:01
>
> dd100000-dd100fff : 0000:01:00.1
>
> dd101000-dd101fff : 0000:01:00.3
>
> dd200000-dd2fffff : PCI Bus 0000:02
>
> dd200000-dd201fff : 0000:02:03.0
>
> dd202000-dd203fff : 0000:02:03.1
>
> dd300000-dd3fffff : PCI Bus 0000:03
>
> dd300000-dd300fff : 0000:03:02.0
>
> dd301000-dd301fff : 0000:03:02.1
>
> dd400000-dd4fffff : PCI Bus 0000:04
>
> dd400000-dd4fffff : PCI Bus 0000:05
>
> dd400000-dd40ffff : 0000:05:04.0
>
> dd400000-dd40ffff : tg3
>
> dd410000-dd41ffff : 0000:05:04.0
>
> dd410000-dd41ffff : tg3
>
> dd420000-dd42ffff : 0000:05:04.1
>
> dd420000-dd42ffff : tg3
>
> dd430000-dd43ffff : 0000:05:04.1
>
> dd430000-dd43ffff : tg3
>
> dd500000-dd5fffff : PCI Bus 0000:06
>
> dd500000-dd5fffff : PCI Bus 0000:07
>
> dd500000-dd50ffff : 0000:07:04.0
>
> dd500000-dd50ffff : tg3
>
> dd510000-dd51ffff : 0000:07:04.0
>
> dd510000-dd51ffff : tg3
>
> dd520000-dd52ffff : 0000:07:04.1
>
> dd520000-dd52ffff : tg3
>
> dd530000-dd53ffff : 0000:07:04.1
>
> dd530000-dd53ffff : tg3
>
> dd600000-dd6fffff : PCI Bus 0000:08
>
> dd600000-dd61ffff : 0000:08:01.0
>
> dd600000-dd61ffff : e1000
>
> dd620000-dd63ffff : 0000:08:02.0
>
> dd620000-dd63ffff : e1000
>
> dd700000-deffffff : PCI Bus 0000:09
>
> dd700000-dd700fff : 0000:09:01.0
>
> de000000-deffffff : 0000:09:01.0
>
> e0000000-efffffff : PCI MMCONFIG 0
>
> e0000000-efffffff : reserved
>
> fec00000-fec0ffff : reserved
>
> fec00000-fec00fff : IOAPIC 0
>
> fec10000-fec10fff : IOAPIC 1
>
> fec80000-fec80fff : IOAPIC 2
>
> fee00000-fee00fff : Local APIC
>
> fee00000-fee00fff : reserved
>
> ff800000-ffbfffff : reserved
>
> fffffc00-ffffffff : reserved
>
> 100000000-22fffffff : System RAM
>
>
>
> Could it be a bug in the Kexec?
>
>
>
> thanks
>
> Soumendu S Satapathy
>
> Senior Software Developer
>
> RELDATA Inc.
>
> 1719 Route 10, Suite 209
>
> Parsippany, NJ 07054
>
> (973) 644-2770 ext. 139 office
>
> 732-692-7230 mobile
>
> (973) 644-3385 fax
>
> soumendu.satapathy@reldata.com
>
> www.reldata.com <http://www.reldata.com/>
>
>
>
>
>
>
>
> Soumendu S Satapathy
>
> Senior Software Developer
>
> RELDATA Inc.
>
> 1719 Route 10, Suite 209
>
> Parsippany, NJ 07054
>
> (973) 644-2770 ext. 139 office
>
> 732-692-7230 mobile
>
> (973) 644-3385 fax
>
> soumendu.satapathy@reldata.com
>
> www.reldata.com <http://www.reldata.com/>
>
>
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-02-23 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 21:32 FW: 2.6.18 Fedora core kernel gives: "Overlapping memory segments at" error Soumendu Satapathy
2010-02-23 21:50 ` Vivek Goyal [this message]
2010-02-23 22:17 ` FW: 2.6.18 Fedora core kernel gives: "Overlapping memorysegments " Soumendu Satapathy
2010-02-23 22:36 ` Vivek Goyal
2010-02-23 22:31 ` Soumendu Satapathy
2010-02-23 22:37 ` Vivek Goyal
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=20100223215032.GG11930@redhat.com \
--to=vgoyal@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=soumendu.satapathy@reldata.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox