From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Temporary fix for broken arch reboot
Date: Wed, 10 Nov 2010 15:46:04 +0000 [thread overview]
Message-ID: <20101110154604.GA27571@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB030D58A400@dbde02.ent.ti.com>
On Wed, Nov 10, 2010 at 09:13:21PM +0530, Shilimkar, Santosh wrote:
>
>
> > -----Original Message-----
> > From: Catalin Marinas [mailto:catalin.marinas at arm.com]
> > Sent: Wednesday, November 10, 2010 7:35 PM
> > To: Russell King - ARM Linux
> > Cc: Shilimkar, Santosh; linux-arm-kernel at lists.infradead.org; Gadiyar,
> > Anand
> > Subject: Re: [PATCH] ARM: Temporary fix for broken arch reboot
> >
> > The printing only happens for SYSTEM_BOOTING or SYSTEM_RUNNING. I
> > suspect in this case we have SYSTEM_RESTARTING and the condition in
> > ipi_cpu_stop() is false, therefore no printing. It may be worth putting
> > some printks outside the 'if' to see whether the secondary CPUs get
> > there.
> >
> While doing some experiments on this issue, one interesting
> observation I made. Looks like there is race between two
> Cores which makes system behave badly in reboot path.
>
> Just adding a delay in the ipi_cpu_stop() makes the reboot work
> as well
That could just be that it's taking longer than 500us for the reboot CPU
to get through setup_mm_for_reboot().
next prev parent reply other threads:[~2010-11-10 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 13:10 [PATCH] ARM: Temporary fix for broken arch reboot Shilimkar, Santosh
2010-11-09 13:18 ` Russell King - ARM Linux
2010-11-09 13:25 ` Shilimkar, Santosh
2010-11-09 16:38 ` Catalin Marinas
2010-11-09 17:05 ` Anand Gadiyar
2010-11-10 5:55 ` Shilimkar, Santosh
2010-11-10 10:06 ` Russell King - ARM Linux
2010-11-10 14:04 ` Catalin Marinas
2010-11-10 15:43 ` Shilimkar, Santosh
2010-11-10 15:46 ` Russell King - ARM Linux [this message]
2010-11-12 10:31 ` Shilimkar, Santosh
2010-11-15 15:25 ` Russell King - ARM Linux
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=20101110154604.GA27571@n2100.arm.linux.org.uk \
--to=linux@arm.linux.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;
as well as URLs for NNTP newsgroup(s).