From: Manfred Gruber <m.gruber@tirol.com>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, Jan Altenberg <jan.altenberg@linutronix.de>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: preempt_rt bug or warn on arm v4t
Date: Wed, 25 Apr 2007 17:02:09 +0200 [thread overview]
Message-ID: <200704251702.09125.m.gruber@tirol.com> (raw)
In-Reply-To: <200704201526.40785.m.gruber@tirol.com>
Hi !
Gerrit Binnenmars pointed out that others have the same problem:
http://linux.omap.com/pipermail/linux-omap-open-source/2007-April/009535.html:
http://article.gmane.org/gmane.linux.distributions.gumstix.general/21376/match=gumstix+realtime+bug+sched+c
Jan Altenberg showed me that in include/asm-arm/system.h I should comment out
this line:
#define __ARCH_WANT_INTERRUPTS_ON_CTXSW
Without this line, irqs are disabled on context switches. But this is only a
change that the WARN dose not more occure. Is this now a hack or the
sollution? Hopfully some RT hacker can look deeper, and find what is wrong.
thanks
regards manfred
Am Freitag, 20. April 2007 15:26 schrieben Sie:
> hi jan !
>
> Am Freitag, 20. April 2007 15:01 schrieben Sie:
> > > I am using 2.6.21-rc7 with Preempt_rt Patch 2.6.20-rc6-rt0 on ep93xx.
> >
> > Do you mean 2.6.21-rc6-rt0?
>
> sorry yes 2.6.21-rc6-rt0.
>
> > > This oops does not trigger in preempt_rt patch is applied.
> >
> > It does only appear, when the preempt_rt patch is applied. Did I get you
> > right?
>
> correct
>
> regards manfred
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2007-04-25 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 11:06 Manfred Gruber
2007-04-20 13:01 ` Jan Altenberg
2007-04-20 13:26 ` Manfred Gruber
2007-04-25 15:02 ` Manfred Gruber [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=200704251702.09125.m.gruber@tirol.com \
--to=m.gruber@tirol.com \
--cc=jan.altenberg@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome