From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Frank Rowand <frank.rowand@am.sony.com>,
"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
"Rowand, Frank" <Frank_Rowand@sonyusa.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Mike Galbraith <efault@gmx.de>, Ingo Molnar <mingo@tglx.de>,
Venkatesh Pallipadi <venki@google.com>
Subject: Re: [ANNOUNCE] 3.0.1-rt11
Date: Wed, 7 Sep 2011 11:46:33 +0100 [thread overview]
Message-ID: <20110907104633.GR6619@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.02.1109071115410.2723@ionos>
On Wed, Sep 07, 2011 at 11:25:29AM +0200, Thomas Gleixner wrote:
> This smells badly like the problem we've seen on x86 before. And
> looking at the arm SMP boot code:
>
> asmlinkage void __cpuinit secondary_start_kernel(void)
> {
> .....
>
> /*
> * Give the platform a chance to do its own initialisation.
> */
> platform_secondary_init(cpu);
>
> /*
> * Enable local interrupts.
> */
> notify_cpu_starting(cpu);
> local_irq_enable();
>
> Here we enable interrupts, but the CPU is neither online nor active.
>
> local_fiq_enable();
That's intentional. Some of the code below needs IRQs enabled.
I think we had this reported before and I got to the bottom of it - the
platform was doing something it shouldn't. I don't remember the details,
maybe when all the emails come through I can see the original bug report
I'll remember.
next prev parent reply other threads:[~2011-09-07 12:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 10:53 [ANNOUNCE] 3.0.1-rt11 Peter Zijlstra
2011-08-13 11:48 ` Mike Galbraith
2011-08-13 11:58 ` Peter Zijlstra
2011-08-13 13:59 ` Mike Galbraith
2011-08-13 14:23 ` Peter Zijlstra
2011-08-13 16:27 ` Paul E. McKenney
2011-08-14 4:23 ` Mike Galbraith
2011-08-16 14:17 ` Nivedita Singhvi
2011-08-16 15:10 ` Mike Galbraith
2011-08-16 15:18 ` Nivedita Singhvi
2011-08-16 19:31 ` Paul E. McKenney
2011-08-17 4:28 ` Mike Galbraith
2011-08-17 5:03 ` Nivedita Singhvi
2011-08-15 10:09 ` Mike Galbraith
2011-08-14 21:19 ` Clark Williams
2011-08-23 14:12 ` [patch] sched, rt: fix migrate_enable() thinko Mike Galbraith
2011-09-08 2:11 ` Frank Rowand
2011-09-08 4:58 ` Mike Galbraith
2011-08-24 23:58 ` [ANNOUNCE] 3.0.1-rt11 Frank Rowand
2011-08-26 23:55 ` Paul E. McKenney
2011-08-29 19:57 ` Frank Rowand
2011-08-30 3:17 ` Paul E. McKenney
2011-09-07 2:53 ` Frank Rowand
2011-09-07 3:00 ` Frank Rowand
2011-09-07 6:42 ` Paul E. McKenney
2011-09-07 9:25 ` Thomas Gleixner
2011-09-07 10:46 ` Russell King - ARM Linux [this message]
2011-09-07 10:47 ` Russell King - ARM Linux
2011-09-07 10:57 ` Thomas Gleixner
2011-09-07 14:01 ` Russell King - ARM Linux
2011-09-07 16:32 ` Thomas Gleixner
2011-09-07 16:33 ` Frank Rowand
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=20110907104633.GR6619@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Frank_Rowand@sonyusa.com \
--cc=efault@gmx.de \
--cc=frank.rowand@am.sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@tglx.de \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=venki@google.com \
/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).