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: Tue, 01 Jul 2008 19:53:17 +0200 [thread overview]
Message-ID: <486A6F0D.4070802@wpkg.org> (raw)
In-Reply-To: <200807011542.29274.nschichan@freebox.fr>
Nicolas Schichan schrieb:
> On Friday 30 May 2008 13:39:16 Tomasz Chmielewski wrote:
>
> Hello,
>
>> Nicolas Schichan schrieb:
>>> On Thursday 29 May 2008 22:15:47 Tomasz Chmielewski wrote:
>>>> 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
>
> This is quite surprising. The jump address that kexec will use is
> cleary not what I expected. I would have expected it to be the Entry
> point address given by readelf.
>
> could you try the following patch to make sure that the kimage*
> structure is not corrupted by the code in machine_kexec() ?
>
> Index: linux/arch/mips/kernel/machine_kexec.c
> ===================================================================
> --- linux/arch/mips/kernel/machine_kexec.c (revision 8056)
> +++ linux/arch/mips/kernel/machine_kexec.c (working copy)
> @@ -49,6 +49,8 @@
> unsigned long entry;
> unsigned long *ptr;
>
> + printk("image->start = %p", image->start);
> +
> reboot_code_buffer =
> (unsigned long)page_address(image->control_code_page);
Umm?
CC arch/mips/kernel/machine_kexec.o
cc1: warnings being treated as errors
arch/mips/kernel/machine_kexec.c: In function 'machine_kexec':
arch/mips/kernel/machine_kexec.c:52: warning: format '%p' expects type
'void *', but argument 2 has type 'long unsigned int'
make[6]: *** [arch/mips/kernel/machine_kexec.o] Error 1
make[5]: *** [arch/mips/kernel] Error 2
make[5]: Leaving directory
`/home/tch-data/openwrt/11612/build_dir/linux-brcm47xx/linux-2.6.25.9'
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2008-07-01 17:53 UTC|newest]
Thread overview: 22+ 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 12:05 ` Nicolas Schichan
2008-05-27 12:40 ` Tomasz Chmielewski
2008-05-27 12:49 ` Nicolas Schichan
2008-05-27 18:14 ` Tomasz Chmielewski
2008-05-27 23:31 ` Simon Horman
2008-05-29 11:47 ` Nicolas Schichan
2008-05-29 12:16 ` Tomasz Chmielewski
2008-05-29 20:15 ` Tomasz Chmielewski
2008-05-30 1:40 ` Maciej W. Rozycki
2008-05-30 11:27 ` Nicolas Schichan
2008-05-30 11:39 ` Tomasz Chmielewski
2008-07-01 13:42 ` Nicolas Schichan
2008-07-01 17:53 ` Tomasz Chmielewski [this message]
2008-07-01 18:00 ` Nicolas Schichan
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-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=486A6F0D.4070802@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox