From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM lockup during Kexec operation
Date: Sat, 22 Apr 2017 00:24:16 +0100 [thread overview]
Message-ID: <20170421232416.GN17774@n2100.armlinux.org.uk> (raw)
In-Reply-To: <f094f2a481994c31bff01ef7579f1d3c@LPHQEX2013.litepoint.internal>
On Fri, Apr 21, 2017 at 11:04:19PM +0000, Rudici Cazeao wrote:
> The issue is localized to linux-3.0.51/arch\arm/mach-transcede/hotplug.c.
>
> cpu_enter_lowpower();
> platform_do_lowpower(cpu, &spurious);
> cpu_leave_lowpower(). / * bring this CPU back into the world of cache coherency, and then restore interrupts */
>
>
> static inline void platform_do_lowpower(unsigned int cpu, int *spurious) {
> for (;;) { / * there is no power-control hardware on this platform, so all we can do is put the core into WFI; this is safe as the calling code will have already disabled interrupts */
> wfe();
> if (pen_release == cpu) {
> break; / * OK, proper wakeup, we're done */
> }
>
> (*spurious)++; / * Getting here, means that we have come out of WFI without having been woken up - Just note it happening - when we're woken, we can report its occurrence.
> }
> }
Sorry, but with the above, the platform can't support suspend/resume or
kexec reliably. It needs a proper implementation - iow, one which
actually takes the CPU offline such that it resumes as it does the very
first time we boot.
This also doesn't seem to be mainline kernel related - and searching
google for "arm/mach-transcede" brings up no relevant results,
certainly not on the first page.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2017-04-21 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 23:04 ARM lockup during Kexec operation Rudici Cazeao
2017-04-21 23:24 ` Russell King - ARM Linux [this message]
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=20170421232416.GN17774@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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