From: Philippe Gerum <rpm@xenomai.org>
To: Daniel Schnell <daniel.schnell@domain.hid>
Cc: xenomai@xenomai.org
Subject: RE: [Xenomai-help] Kernel-OOps
Date: Tue, 27 Feb 2007 15:38:14 +0100 [thread overview]
Message-ID: <1172587094.27967.10.camel@domain.hid> (raw)
In-Reply-To: <DD39B5C3F4963040ADC9768BE7E430CB01B536B3@domain.hid>
On Tue, 2007-02-27 at 13:53 +0000, Daniel Schnell wrote:
> Daniel Schnell wrote:
> > Hi,
> >
> > I have a bad Kernel-Ooops on my MPC5200B based PPC target.
> > Unfortunately not reproducable with a small application again.
> > I used a 2.4.25 based Denx Kernel (latest and greatest version) and
> > Xenomai - trunk with revision 2256.
> >
>
>
> If I increase MAX_DELAYED_MM in linux/kernel/sched.c from 32 to 64 the
> OOPS disappears ....
>
Which is normal, since this is the BUG_ON() statement in sched.c:558
that triggers.
> As we have quite a number of concurrent threads running (>50) could
> MAX_DELAYED_MM be depending on the number of threads in the system ?
Some usage patterns involving permanent mode switches inside a large set
of real-time threads that only rarely relinquish the CPU to other
regular Linux tasks may cause this. This is specific to 2.4 kernels. I
will raise this value in the next patch update. Thanks,
--
Philippe.
next prev parent reply other threads:[~2007-02-27 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 13:25 [Xenomai-help] Kernel-OOps Daniel Schnell
2007-02-27 13:53 ` Daniel Schnell
2007-02-27 14:38 ` Philippe Gerum [this message]
2007-02-27 14:51 ` Daniel Schnell
2007-02-27 19:03 ` Philippe Gerum
2007-02-28 8:59 ` Daniel Schnell
2007-02-28 10:35 ` Philippe Gerum
2007-02-28 14:25 ` Daniel Schnell
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=1172587094.27967.10.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=daniel.schnell@domain.hid \
--cc=xenomai@xenomai.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.