mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Magnus Damm" <magnus.damm@gmail.com>
To: vgoyal@in.ibm.com
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	fastboot@lists.osdl.org,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Horms <horms@verge.net.au>, "Magnus Damm" <magnus@valinux.co.jp>
Subject: Re: 2.6.19-rc1: kexec broken on x86_64
Date: Thu, 5 Oct 2006 22:56:51 +0900	[thread overview]
Message-ID: <aec7e5c30610050656u6d287752pc9d1bcbb807442d3@mail.gmail.com> (raw)
In-Reply-To: <20061005134522.GB20551@in.ibm.com>

Hi Vivek,

On 10/5/06, Vivek Goyal <vgoyal@in.ibm.com> wrote:
> On Thu, Oct 05, 2006 at 07:28:35PM +0900, Magnus Damm wrote:
> > Kexec is broken on x86_64 under 2.6.19-rc1.
> >
> > Or rather - kexec works ok under 2.6.19-rc1, but something related to
> > the vmlinux format has probably changed and kexec-tools fails to load
> > a vmlinux from 2.6.19-rc1.
> >
> > Loading bzImage works as usual, but vmlinux does not load properly.
> >
> > The kexec binary fails with the following message:
> >
> > Overlapping memory segments at 0x351000
> > sort_segments failed
> > / #
> >
>
> Hi Magnus,
>
> Can you please post the readelf -l output of the vmlinux you are trying
> to load. That's will give some indication if the segments are really
> overlapping in vmlinux or is it some processing bug at kexec-tools part.

Elf file type is EXEC (Executable file)
Entry point 0x100100
There are 4 program headers, starting at offset 64

Program Headers:
  Type           Offset             VirtAddr           PhysAddr
                 FileSiz            MemSiz              Flags  Align
  LOAD           0x0000000000100000 0xffffffff80100000 0x0000000000100000
                 0x00000000001a4888 0x00000000001a4888  R E    100000
  LOAD           0x00000000002a5000 0xffffffff802a5000 0x00000000002a5000
                 0x000000000008e086 0x00000000000c1504  RWE    100000
  LOAD           0x0000000000400000 0xffffffffff600000 0x00000000002fd000
                 0x0000000000000c08 0x0000000000000c08  RWE    100000
  NOTE           0x0000000000000000 0x0000000000000000 0x0000000000000000
                 0x0000000000000000 0x0000000000000000  R      8

 Section to Segment mapping:
  Segment Sections...
   00     .text __ex_table .rodata .pci_fixup __ksymtab __ksymtab_gpl
__ksymtab_unused __ksymtab_strings __param
   01     .data .data.cacheline_aligned .data.read_mostly
.data.init_task .data.page_aligned .init.text .init.data .init.setup
.initcall.init .con_initcall.init .altinstructions
.altinstr_replacement .exit.text .init.ramfs .bss
   02     .vsyscall_0 .xtime_lock .vxtime .vgetcpu_mode .sys_tz
.sysctl_vsyscall .xtime .jiffies .vsyscall_1 .vsyscall_2 .vsyscall_3
   03

Thanks,

/ magnus

  reply	other threads:[~2006-10-05 13:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 10:28 Magnus Damm
2006-10-05 13:45 ` Vivek Goyal
2006-10-05 13:56   ` Magnus Damm [this message]
2006-10-05 14:24     ` Vivek Goyal
2006-10-05 15:17       ` Eric W. Biederman
2006-10-05 14:33     ` Eric W. Biederman
2006-10-05 16:33     ` Vivek Goyal
2006-10-06  2:28       ` Magnus Damm

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=aec7e5c30610050656u6d287752pc9d1bcbb807442d3@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=horms@verge.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus@valinux.co.jp \
    --cc=vgoyal@in.ibm.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

Powered by JetHome