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 10:06:17 +0000 [thread overview]
Message-ID: <20101110100617.GA23244@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB030D4FAE5C@dbde02.ent.ti.com>
On Wed, Nov 10, 2010 at 11:25:21AM +0530, Shilimkar, Santosh wrote:
> > -----Original Message-----
> > From: Catalin Marinas [mailto:catalin.marinas at arm.com]
> > Sent: Tuesday, November 09, 2010 10:08 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
> >
> > On Tue, 2010-11-09 at 13:18 +0000, Russell King - ARM Linux wrote:
> > > On Tue, Nov 09, 2010 at 06:40:39PM +0530, Shilimkar, Santosh wrote:
> > > > With commit 3d3f78d752bf, reboot seems to broken on ARM
> > > > machines. CPU dies while doing flush_pmd_entry() as part of
> > > > setup_mm_for_reboot()
> >
> > What do you mean by 'dies'? Can you still connect with a debugger or it
> > got to some weird state?
> >
> It goes to some weird state. Basically the emulation connection dies,
> and debugger gets disconnected.
>
> > > > I know this is not the fix but intention is to report the
> > > > issue and also provide temporary fix till it get fixed correctly
> > >
> > > So you're now rebooting with the secondary CPUs still running. I guess
> > > that the secondary CPUs end up crashing and don't restart.
> > >
> > > I think more the question is why the CP15 cache clean/flush is hanging
> > > with the other CPUs taken down. All the other CPUs will be doing is
> > > sitting in a loop doing nothing.
> >
> > I can't think of anything. Did the other CPUs print 'stopping'?
> No it doesn't not print anything.
The processing of the IPI is asynchronous to the CPU which is rebooting
continuing - which means that if there is some kind of bus lockup, you
won't get anything from any of the CPUs.
You might be able to get something from the other CPUs by inserting a
mdelay(100) after the call to machine_shutdown(), to give the other CPUs
time to respond.
next prev parent reply other threads:[~2010-11-10 10:06 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 [this message]
2010-11-10 14:04 ` Catalin Marinas
2010-11-10 15:43 ` Shilimkar, Santosh
2010-11-10 15:46 ` Russell King - ARM Linux
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=20101110100617.GA23244@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).