From: Tomas Kalibera <kalibera@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Kernel crash with Xenomai (caused by fork?)
Date: Wed, 02 Apr 2008 19:46:27 -0400 [thread overview]
Message-ID: <47F41AD3.2020809@domain.hid> (raw)
In-Reply-To: <18420.2520.32895.319766@domain.hid>
Gilles Chanteperdrix wrote:
> Of course, we are looking for all bugs. But please tell me: do you get
> the lock-up even before fork is called ? If not, could you verify that
> at least some Xenomai programs run correctly, for instance latency ?
>
The lock up with patch 5 happens before fork is called, but after a
real-time task is started by the program. I don't know better now - I'd
have to add more logging. If I run in strace, the lock-up does not happen.
Thinking about that, it can be a bug in my program. If I understand the
concept of Xenomai correctly, I can just write a real-time task that
would starve the Linux kernel indefinitely, correct ? My program
definitely does have bugs. So I'll do more debugging.
The lock-up does NOT happen with latency. But, the bug in the kernel
without patch 5 (the one that lead to a stack trac, after call to fork),
did not appear in latency, either.
> Looking at the code, I think I found a bug, but I doubt it could cause a
> lockup. The definition of VM_PINNED in include/linux/mm.h collides with
> another bit used by Linux, so this defintion should be changed from:
> #define VM_PINNED 0x08000000
> to:
> #define VM_PINNED 0x10000000
>
> I will now try, if possible, to reproduce the bug on a x86 box of mine
> and will keep you informed.
>
Thanks ! I'll indeed build kernel with patch 6, test again, and test my
application.
Tomas
next prev parent reply other threads:[~2008-04-02 23:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 21:06 [Xenomai-core] Kernel crash with Xenomai (caused by fork?) Tomas Kalibera
2008-03-28 23:25 ` Gilles Chanteperdrix
2008-03-29 0:08 ` Gilles Chanteperdrix
2008-03-29 1:36 ` Tomas Kalibera
2008-03-29 20:17 ` Gilles Chanteperdrix
2008-03-30 20:27 ` Gilles Chanteperdrix
2008-03-31 4:04 ` Tomas Kalibera
2008-03-31 20:21 ` Gilles Chanteperdrix
2008-03-31 20:30 ` Gilles Chanteperdrix
2008-04-01 0:00 ` Tomas Kalibera
2008-04-01 5:52 ` Gilles Chanteperdrix
2008-04-01 7:59 ` Gilles Chanteperdrix
2008-04-01 13:54 ` Tomas Kalibera
2008-04-01 14:03 ` Gilles Chanteperdrix
2008-04-01 15:45 ` Tomas Kalibera
2008-04-01 15:58 ` Gilles Chanteperdrix
2008-04-01 21:23 ` Tomas Kalibera
2008-04-02 8:42 ` Gilles Chanteperdrix
2008-04-02 15:02 ` Tomas Kalibera
2008-04-02 15:07 ` Gilles Chanteperdrix
2008-04-02 18:14 ` Tomas Kalibera
2008-04-02 19:38 ` Tomas Kalibera
2008-04-02 19:42 ` Bill Gatliff
2008-04-02 19:44 ` Gilles Chanteperdrix
2008-04-02 21:45 ` Tomas Kalibera
2008-04-02 22:34 ` Gilles Chanteperdrix
2008-04-02 22:53 ` Gilles Chanteperdrix
2008-04-03 17:31 ` Tomas Kalibera
2008-04-05 4:32 ` Tomas Kalibera
2008-04-05 9:10 ` Jan Kiszka
2008-04-02 23:46 ` Tomas Kalibera [this message]
2008-04-03 9:04 ` Gilles Chanteperdrix
2008-04-02 19:52 ` Gilles Chanteperdrix
2008-04-02 21:37 ` Tomas Kalibera
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=47F41AD3.2020809@domain.hid \
--to=kalibera@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--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.