All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Haskins <ghaskins@novell.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: m.luescher@vtxmail.ch,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Carsten.Emde@osadl.org, rostedt@goodmis.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Hard lockup with 2.6.24.7-rt26 on x86 - cause found
Date: Fri, 06 Feb 2009 07:39:47 -0500	[thread overview]
Message-ID: <498C2F93.9090405@novell.com> (raw)
In-Reply-To: <1233919704.10894.5.camel@laptop>

[-- Attachment #1: Type: text/plain, Size: 2061 bytes --]

Peter Zijlstra wrote:
> On Fri, 2009-02-06 at 11:34 +0100, Matthias Luescher wrote:
>   
>> Hi
>>
>> I finally found out which patch does not work well with my configuration:
>>
>> 2.6.24.7-rt12 seems to be ok, with 2.6.24.7-rt13 the command cyclictest -p99 -t10 -n -i250 crashes the kernel.
>>
>> 2.6.24.7-rt13 has the follwing new patches:
>> ftrace-hotplug-fix.patch
>> ftrace-wakeup-rawspinlock.patch
>> radix-tree-lockdep-plus1.patch
>> sched-cpupri-hotplug-support.patch
>> sched-cpupri-priocount.patch
>>
>> No I went again to 2.6.24.7-rt26 but removed some patches:
>> 2.6.24.7-rt26 with all patches -> CRASH
>> 2.6.24.7-rt26 without sched-cpupri-hotplug-support.patch and without sched-cpupri-priocount.patch ->OK
>> 2.6.24.7-rt26 without sched-cpupri-hotplug-support.patch ->CRASH
>>     
>
> sched-cpupri-priocount.patch is buggy
>
> +#define CPUPRI_NR_PRI_WORDS (CPUPRI_NR_PRIORITIES + BITS_PER_LONG/2)/BITS_PER_LONG
>   

Thomas fixed this somewhere along the way with the inlined patch. 
Steven, this should be pulled into all actively maintained -rt branches
that do not already have it.

commit e539d8fcd11af811db70707d47ea436d5621d0da
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Thu Jun 5 10:28:00 2008 +0200

    sched: fix the cpuprio count really
   
    Peter pointed out that the last version of the "fix" was still one off
    under certain circumstances. Use BITS_TO_LONG instead to get an
    accurate result.
   
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

diff --git a/kernel/sched_cpupri.h b/kernel/sched_cpupri.h
index 6b38355..f25811b 100644
--- a/kernel/sched_cpupri.h
+++ b/kernel/sched_cpupri.h
@@ -3,8 +3,8 @@
 
 #include <linux/sched.h>
 
-#define CPUPRI_NR_PRIORITIES 2+MAX_RT_PRIO
-#define CPUPRI_NR_PRI_WORDS (CPUPRI_NR_PRIORITIES +
BITS_PER_LONG/2)/BITS_PER_LONG
+#define CPUPRI_NR_PRIORITIES   (MAX_RT_PRIO + 2)
+#define CPUPRI_NR_PRI_WORDS    BITS_TO_LONGS(CPUPRI_NR_PRIORITIES)
 
 #define CPUPRI_INVALID -1
 #define CPUPRI_IDLE     0



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2009-02-06 12:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 10:34 Re: Re: Hard lockup with 2.6.24.7-rt26 on x86 - cause found Matthias Luescher
2009-02-06 11:28 ` Peter Zijlstra
2009-02-06 12:39   ` Gregory Haskins [this message]
2009-02-06 14:16   ` Steven Rostedt

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=498C2F93.9090405@novell.com \
    --to=ghaskins@novell.com \
    --cc=Carsten.Emde@osadl.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=m.luescher@vtxmail.ch \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.