| To: | Tomasz Chmielewski <mangoo@wpkg.org> |
|---|---|
| Subject: | Re: kexec on mips - anyone has it working? |
| From: | Nicolas Schichan <nschichan@freebox.fr> |
| Date: | Thu, 29 May 2008 13:47:04 +0200 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <483C4F73.4040909@wpkg.org> |
| Organization: | Freebox |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <483BCB75.4050901@wpkg.org> <200805271449.45124.nschichan@freebox.fr> <483C4F73.4040909@wpkg.org> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | KMail/1.9.6 (enterprise 0.20070907.709405) |
On Tuesday 27 May 2008 20:14:11 you wrote: > Aah, I see. > > Anyway, it doesn't work - with or without this slight change in > machine_kexec.c, with kexec compiled from the sources in the link you > gave or with kexec-tools-testing-20080324, it just doesn't work on > BCM43XX with OpenWRT patches. At least on Asus WL-500gP. I'm not familiar with broadcom CPU names, but isn't BCM43XX supposed to be a Wifi chipset ? :) However, could you kexec a kernel from a kernel that has CONFIG_MIPS_UNCACHED set (under "Kernel hacking", "run uncached")? this will slow down the kernel that does the kexec, but if this works, then it is most probably a cache problem. Could you also indicate the last lines of kernel messages just before the "Bye." ? Are you trying to kexec a big kernel image ? how much RAM do you have on the board ? are there some hardware that could have a hard time to be re-probed by the kexeced linux kernel ? Regards, -- Nicolas Schichan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Changing the treatment of the MIPS HI and LO registers, Maciej W. Rozycki |
|---|---|
| Next by Date: | Re: kexec on mips - anyone has it working?, Maciej W. Rozycki |
| Previous by Thread: | Re: kexec on mips - anyone has it working?, Simon Horman |
| Next by Thread: | Re: kexec on mips - anyone has it working?, Tomasz Chmielewski |
| Indexes: | [Date] [Thread] [Top] [All Lists] |