From: Peter Zijlstra <peterz@infradead.org>
To: m.luescher@vtxmail.ch
Cc: ghaskins@novell.com,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Carsten.Emde@osadl.org, rostedt@goodmis.org
Subject: Re: Re: Re: Hard lockup with 2.6.24.7-rt26 on x86 - cause found
Date: Fri, 06 Feb 2009 12:28:24 +0100 [thread overview]
Message-ID: <1233919704.10894.5.camel@laptop> (raw)
In-Reply-To: <49725.1233916457@vtxmail.ch>
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
Should read:
#define CPUPRI_NR_PRI_WORDS BITS_TO_LONG(CPUPRI_NR_PRIORITIES)
Can't remember much about that other patch, although I was involved back
then.
Does -tip work OK? Most of that cpupri stuff went upstream iirc.
next prev parent reply other threads:[~2009-02-06 11:29 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 [this message]
2009-02-06 12:39 ` Gregory Haskins
2009-02-06 14:16 ` Re: " 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=1233919704.10894.5.camel@laptop \
--to=peterz@infradead.org \
--cc=Carsten.Emde@osadl.org \
--cc=ghaskins@novell.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=m.luescher@vtxmail.ch \
--cc=rostedt@goodmis.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 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.