From: wurststulle <wurststulle@gmail.com>
To: linux-mips@linux-mips.org
Subject: Re: kexec on mips - anyone has it working?
Date: Mon, 23 Feb 2009 10:42:35 -0800 (PST) [thread overview]
Message-ID: <22167417.post@talk.nabble.com> (raw)
In-Reply-To: <m3d4d9o5z7.fsf@anduin.mandriva.com>
hi, thank you for the patch, but there is a mistake, that i can not fix:
+#ifdef CONFIG_CRASH_DUMP
+ if (crashk_res.start != crashk_res.end)
+ reserve_bootmem(crashk_res.start,
+ crashk_res.end - crashk_res.start + 1);
+#endif
the function reserve_bootmem need i think three arguments. while compiling
this error occurs:
arch/mips/kernel/setup.c: In function 'arch_mem_init':
arch/mips/kernel/setup.c:493: error: too few arguments to function
'reserve_bootmem'
make[6]: *** [arch/mips/kernel/setup.o] Error 1
thanks!
Arnaud Patard wrote:
>
> wurststulle <wurststulle@gmail.com> writes:
>
> Hi,
>
>> is there any solution for this, i have the same problem
>
> What's your exact problem ? It hangs right after saying 'Bye...' ?
> Some monthes ago, I played with the patch from M. Syrchin [ sorry, I don't
> remember if it was on linux-mips or on the kexec list ]. I've made on it
> a small modification (compare the machine_kexec_prepare function in my
> version [1] and the original function) and it was somewhat working on
> Qemu and on my box. It was not perfect but at least with a very minimal
> test system, it was working. Maybe you can try it and see if it works
> for you too. Depending on your platform, you may have to define machine
> specific hooks too.
>
> Regards,
> Arnaud
>
> [1] http://people.mandriva.com/~apatard/kexec_mips.patch
>
>
>
--
View this message in context: http://www.nabble.com/kexec-on-mips---anyone-has-it-working--tp17485898p22167417.html
Sent from the linux-mips main mailing list archive at Nabble.com.
next prev parent reply other threads:[~2009-02-23 18:42 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
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 [this message]
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=22167417.post@talk.nabble.com \
--to=wurststulle@gmail.com \
--cc=linux-mips@linux-mips.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