All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Nicolas Schichan <nschichan@freebox.fr>
Cc: linux-mips@linux-mips.org, openwrt-devel@lists.openwrt.org,
	Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: kexec on mips - anyone has it working?
Date: Fri, 30 May 2008 13:39:16 +0200	[thread overview]
Message-ID: <483FE764.1090901@wpkg.org> (raw)
In-Reply-To: <200805301327.11925.nschichan@freebox.fr>

Nicolas Schichan schrieb:
> On Thursday 29 May 2008 22:15:47 Tomasz Chmielewski wrote:
>> # kexec -e
>> b44: eth0: powering down PHY
>> Starting new kernel
>> Will call new kernel at 00305000
> 
> The calling address of the kernel looks quite wrong, it should clearly
> be inside the KSEG0 zone. could  you please indicate the output of the
> command "mips-linux-readelf -l vmlinux" ?

# uname -m
mips
# readelf -l vmlinux

Elf file type is EXEC (Executable file)
Entry point 0x80251b50
There are 2 program headers, starting at offset 52

Program Headers:
   Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
   LOAD           0x001000 0x80001000 0x80001000 0x2dd07a 0x303250 RWE 
0x2000
   NOTE           0x000000 0x00000000 0x00000000 0x00000 0x00000 R   0x4

  Section to Segment mapping:
   Segment Sections...
    00     .text __ex_table __dbe_table .rodata .pci_fixup __ksymtab 
__ksymtab_gpl __ksymtab_strings __param .data .data.cacheline_aligned 
.init.text .init.data .init.setup .initcall.init .con_initcall.init 
.exit.text .init.ramfs .bss
    01

-- 
Tomasz Chmielewski
http://wpkg.org

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

WARNING: multiple messages have this Message-ID (diff)
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Nicolas Schichan <nschichan@freebox.fr>
Cc: linux-mips@linux-mips.org,
	Kexec Mailing List <kexec@lists.infradead.org>,
	openwrt-devel@lists.openwrt.org
Subject: Re: kexec on mips - anyone has it working?
Date: Fri, 30 May 2008 13:39:16 +0200	[thread overview]
Message-ID: <483FE764.1090901@wpkg.org> (raw)
In-Reply-To: <200805301327.11925.nschichan@freebox.fr>

Nicolas Schichan schrieb:
> On Thursday 29 May 2008 22:15:47 Tomasz Chmielewski wrote:
>> # kexec -e
>> b44: eth0: powering down PHY
>> Starting new kernel
>> Will call new kernel at 00305000
> 
> The calling address of the kernel looks quite wrong, it should clearly
> be inside the KSEG0 zone. could  you please indicate the output of the
> command "mips-linux-readelf -l vmlinux" ?

# uname -m
mips
# readelf -l vmlinux

Elf file type is EXEC (Executable file)
Entry point 0x80251b50
There are 2 program headers, starting at offset 52

Program Headers:
   Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
   LOAD           0x001000 0x80001000 0x80001000 0x2dd07a 0x303250 RWE 
0x2000
   NOTE           0x000000 0x00000000 0x00000000 0x00000 0x00000 R   0x4

  Section to Segment mapping:
   Segment Sections...
    00     .text __ex_table __dbe_table .rodata .pci_fixup __ksymtab 
__ksymtab_gpl __ksymtab_strings __param .data .data.cacheline_aligned 
.init.text .init.data .init.setup .initcall.init .con_initcall.init 
.exit.text .init.ramfs .bss
    01

-- 
Tomasz Chmielewski
http://wpkg.org

  reply	other threads:[~2008-05-30 11:39 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27  8:51 kexec on mips - anyone has it working? Tomasz Chmielewski
2008-05-27  8:51 ` Tomasz Chmielewski
2008-05-27 12:05 ` Nicolas Schichan
2008-05-27 12:40   ` Tomasz Chmielewski
2008-05-27 12:40     ` Tomasz Chmielewski
2008-05-27 12:49     ` Nicolas Schichan
2008-05-27 18:14       ` Tomasz Chmielewski
2008-05-27 18:14         ` Tomasz Chmielewski
2008-05-27 23:31         ` Simon Horman
2008-05-27 23:31           ` Simon Horman
2008-05-29 11:47         ` Nicolas Schichan
2008-05-29 12:16           ` Tomasz Chmielewski
2008-05-29 12:16             ` Tomasz Chmielewski
2008-05-29 20:15           ` Tomasz Chmielewski
2008-05-29 20:15             ` Tomasz Chmielewski
2008-05-30  1:40             ` Maciej W. Rozycki
2008-05-30  1:40               ` Maciej W. Rozycki
2008-05-30 11:27             ` Nicolas Schichan
2008-05-30 11:27               ` Nicolas Schichan
2008-05-30 11:39               ` Tomasz Chmielewski [this message]
2008-05-30 11:39                 ` Tomasz Chmielewski
2008-07-01 13:42                 ` Nicolas Schichan
2008-07-01 13:42                   ` Nicolas Schichan
2008-07-01 17:53                   ` Tomasz Chmielewski
2008-07-01 17:53                     ` Tomasz Chmielewski
2008-07-01 18:00                     ` Nicolas Schichan
2008-07-01 18:00                       ` Nicolas Schichan
2008-07-01 18:21                       ` Tomasz Chmielewski
2008-07-01 18:21                         ` Tomasz Chmielewski
2009-02-22 16:50                         ` wurststulle
2009-02-23  9:30                           ` Arnaud Patard
2009-02-23 18:42                             ` wurststulle
2009-02-23 21:29                               ` Arnaud Patard
2008-07-01 18:25                       ` Tomasz Chmielewski
2008-07-01 18:25                         ` Tomasz Chmielewski
2008-05-27 12:40   ` Nicolas Schichan

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=483FE764.1090901@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-mips@linux-mips.org \
    --cc=nschichan@freebox.fr \
    --cc=openwrt-devel@lists.openwrt.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.