From: Mikulas Patocka <mpatocka@redhat.com>
To: torvalds@linux-foundation.org, Peter Zijlstra <peterz@infradead.org>
Cc: Stepan Moskovchenko <stepanm@codeaurora.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Signed-off-by:;
Subject: [PATCH] 5fbd036b552f633abb394a319f7c62a5c86a9cd7 breaks PA-RISC boot
Date: Tue, 8 May 2012 23:30:05 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1205082323020.21169@file.rdu.redhat.com> (raw)
In-Reply-To: <1336250006.2463.139.camel@laptop>
On Sat, 5 May 2012, Peter Zijlstra wrote:
> On Fri, 2012-05-04 at 23:26 -0400, Mikulas Patocka wrote:
> > Your patch 5fbd036b552f633abb394a319f7c62a5c86a9cd7 breaks PA-RISC boot. I
> > have a dual-core PA-8800. With the patch applied, the kernel crashes with
> > these messages. The timer structures are apparently corrupted, as the
> > timer sees a negative amount of delayed cycles:
>
> You'll find:
>
> http://marc.info/?l=linux-parisc&m=133241790810604&w=2
>
> will probably fix the issue.
I confirm that the patch fixes the problem.
So let's send it to Linus so that 3.4 will boot on PA-RISC.
Mikulas
---
The scheduler depends on receiving the CPU_STARTING notification, without
which we end up into a lot of trouble. So add the missing call to
notify_cpu_starting() in the bringup code.
Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
Acked-by: Mikulas Patocka <mpatocka@redhat.com>
---
arch/parisc/kernel/smp.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
Index: linux-3.4-rc6-fast/arch/parisc/kernel/smp.c
===================================================================
--- linux-3.4-rc6-fast.orig/arch/parisc/kernel/smp.c 2012-05-09 04:54:35.000000000 +0200
+++ linux-3.4-rc6-fast/arch/parisc/kernel/smp.c 2012-05-09 04:55:24.000000000 +0200
@@ -295,8 +295,13 @@ smp_cpu_init(int cpunum)
printk(KERN_CRIT "CPU#%d already initialized!\n", cpunum);
machine_halt();
- }
+ }
+
+ notify_cpu_starting(cpunum);
+
+ ipi_call_lock();
set_cpu_online(cpunum, true);
+ ipi_call_unlock();
/* Initialise the idle task for this CPU */
atomic_inc(&init_mm.mm_count);
prev parent reply other threads:[~2012-05-09 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 3:26 Mikulas Patocka
2012-05-05 20:33 ` Peter Zijlstra
2012-05-09 3:30 ` Mikulas Patocka [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=Pine.LNX.4.64.1205082323020.21169@file.rdu.redhat.com \
--to=mpatocka@redhat.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=stepanm@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®