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>
Subject: Re: kexec on mips - anyone has it working?
Date: Thu, 29 May 2008 14:16:23 +0200 [thread overview]
Message-ID: <483E9E97.6050207@wpkg.org> (raw)
In-Reply-To: <200805291347.05196.nschichan@freebox.fr>
Nicolas Schichan schrieb:
> 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 ? :)
Well, yeah, indeed the device is sold as a wireless router. But it can
perfectly run Debian, so it should run kexec as well, shouldn't it? ;)
> 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." ?
I'll try that later today and will post the results.
> Are you trying to kexec a big kernel image ?
Hmm, is it big? It's the same kernel I booted:
# ls -l vmlinux
-rwxr-xr-x 1 root root 3868065 May 26 23:30 vmlinux
> how much RAM do you have
> on the board ?
It has 32 MB RAM; some ~11 MB is used before I load another kernel.
> are there some hardware that could have a hard time to
> be re-probed by the kexeced linux kernel ?
The kexeced kernel is the same one I booted, so no.
--
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>
Subject: Re: kexec on mips - anyone has it working?
Date: Thu, 29 May 2008 14:16:23 +0200 [thread overview]
Message-ID: <483E9E97.6050207@wpkg.org> (raw)
In-Reply-To: <200805291347.05196.nschichan@freebox.fr>
Nicolas Schichan schrieb:
> 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 ? :)
Well, yeah, indeed the device is sold as a wireless router. But it can
perfectly run Debian, so it should run kexec as well, shouldn't it? ;)
> 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." ?
I'll try that later today and will post the results.
> Are you trying to kexec a big kernel image ?
Hmm, is it big? It's the same kernel I booted:
# ls -l vmlinux
-rwxr-xr-x 1 root root 3868065 May 26 23:30 vmlinux
> how much RAM do you have
> on the board ?
It has 32 MB RAM; some ~11 MB is used before I load another kernel.
> are there some hardware that could have a hard time to
> be re-probed by the kexeced linux kernel ?
The kexeced kernel is the same one I booted, so no.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2008-05-29 12:16 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 [this message]
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
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=483E9E97.6050207@wpkg.org \
--to=mangoo@wpkg.org \
--cc=kexec@lists.infradead.org \
--cc=linux-mips@linux-mips.org \
--cc=nschichan@freebox.fr \
/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.