From: Thomas Gleixner <tglx@linutronix.de>
To: "N, Mugunthan V" <mugunthanvnm@ti.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: RE: [ANNOUNCE] 3.0-rt3
Date: Wed, 27 Jul 2011 20:32:40 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1107272029430.2660@ionos> (raw)
In-Reply-To: <45EE9921DD12714AB1D7B7B9D2FE208B0230256D48BF@dbde03.ent.ti.com>
On Wed, 27 Jul 2011, N, Mugunthan V wrote:
Please do not top post.
> I am testing 3.0-rt3 on AM3517 - Arm Cortex A8. As the kernel from the
> mainline is not booting I am using a patch to boot AM3517 kernel on top of
> the mainline kernel. Its crashing when I start hackbench and cyclictest.
>
> There were two warnings while starting the test and then the kernel crashes.
> Attaching the patch and the rt-config file.
>
> [ 266.001220] BUG: sleeping function called from invalid context at
> kernel/rtmutex.c:645
That should be fixed by the patch below.
> [ 267.494995] ------------[ cut here ]------------
> [ 267.495086] WARNING: at kernel/lockdep.c:939 __bfs+0x1f8/0x254()
Could you please disable CONFIG_RCU_BOOST ?
Thanks,
tglx
Index: linux-2.6/arch/arm/include/asm/mmu.h
===================================================================
--- linux-2.6.orig/arch/arm/include/asm/mmu.h
+++ linux-2.6/arch/arm/include/asm/mmu.h
@@ -6,7 +6,7 @@
typedef struct {
#ifdef CONFIG_CPU_HAS_ASID
unsigned int id;
- spinlock_t id_lock;
+ raw_spinlock_t id_lock;
#endif
unsigned int kvm_seq;
} mm_context_t;
Index: linux-2.6/arch/arm/mm/context.c
===================================================================
--- linux-2.6.orig/arch/arm/mm/context.c
+++ linux-2.6/arch/arm/mm/context.c
@@ -31,7 +31,7 @@ DEFINE_PER_CPU(struct mm_struct *, curre
void __init_new_context(struct task_struct *tsk, struct mm_struct *mm)
{
mm->context.id = 0;
- spin_lock_init(&mm->context.id_lock);
+ raw_spin_lock_init(&mm->context.id_lock);
}
static void flush_context(void)
@@ -58,7 +58,7 @@ static void set_mm_context(struct mm_str
* the broadcast. This function is also called via IPI so the
* mm->context.id_lock has to be IRQ-safe.
*/
- spin_lock_irqsave(&mm->context.id_lock, flags);
+ raw_spin_lock_irqsave(&mm->context.id_lock, flags);
if (likely((mm->context.id ^ cpu_last_asid) >> ASID_BITS)) {
/*
* Old version of ASID found. Set the new one and
@@ -67,7 +67,7 @@ static void set_mm_context(struct mm_str
mm->context.id = asid;
cpumask_clear(mm_cpumask(mm));
}
- spin_unlock_irqrestore(&mm->context.id_lock, flags);
+ raw_spin_unlock_irqrestore(&mm->context.id_lock, flags);
/*
* Set the mm_cpumask(mm) bit for the current CPU.
prev parent reply other threads:[~2011-07-27 18:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 10:33 [ANNOUNCE] 3.0-rt3 Thomas Gleixner
2011-07-24 14:40 ` Maarten Lankhorst
2011-07-24 16:12 ` Thomas Gleixner
2011-07-24 16:42 ` hermann
2011-07-24 16:44 ` Thomas Gleixner
2011-07-24 16:53 ` hermann
2011-07-24 17:23 ` Georgiewskiy Yuriy
2011-07-25 22:20 ` Darren Hart
2011-07-26 6:00 ` Darren Hart
2011-07-26 11:44 ` Maarten Lankhorst
2011-07-26 17:01 ` Darren Hart
2011-07-26 17:11 ` Maarten Lankhorst
2011-07-27 1:57 ` [ANNOUNCE] 3.0-rt3 (futex_requeue bad spinlock magic) Darren Hart
2011-07-27 8:25 ` Darren Hart
2011-07-26 9:01 ` [ANNOUNCE] 3.0-rt3 Thomas Gleixner
2011-07-25 22:55 ` Fernando Lopez-Lezcano
2011-07-26 9:13 ` Uwe Kleine-König
2011-07-26 23:52 ` Fernando Lopez-Lezcano
2011-07-26 23:57 ` Fernando Lopez-Lezcano
2011-07-26 3:11 ` Frank Rowand
2011-07-26 9:30 ` Uwe Kleine-König
2011-07-26 3:12 ` Frank Rowand
2011-07-26 9:19 ` Uwe Kleine-König
2011-07-26 9:25 ` Thomas Gleixner
2011-07-26 3:14 ` Frank Rowand
2011-07-26 3:49 ` Darren Hart
2011-07-26 6:20 ` Yong Zhang
2011-07-27 18:05 ` N, Mugunthan V
2011-07-27 18:32 ` Thomas Gleixner [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=alpine.LFD.2.02.1107272029430.2660@ionos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mugunthanvnm@ti.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