From: lsorense@domain.hid (Lennart Sorensen)
To: xenomai@xenomai.org
Subject: [Xenomai-core] CONFIG_XENO_HW_UNLOCKED_SWITCH=y causes random process corruption in xenomai 2.6.0 on powerpc.
Date: Fri, 23 Dec 2011 12:33:09 -0500 [thread overview]
Message-ID: <20111223173309.GM27742@domain.hid> (raw)
After spending quite a while trying to explain how things like /bin/echo
could possibly segfault, I finally discovered that the new feature in
xenomai 2.6.0 (new when moving from 2.4.10 that is) of having preemptible
context switches is what is corrupting the state of random linux processes
once in a while.
After turning the option off, I haven't seen a single crash just like 2.4.10.
So something subtle is wrong with this option.
It appears to be most likely to occour (possibly only likely) when
xenomai is handling interrupts.
It seems that getting an interrupt in the middle of a context switch at
the wrong time corrupts the process that is being switched to or from
(no idea which it is).
Unless someone can think of a way to track down and fix this I would
certainly suggest making the option off by default instead of on.
With CONFIG_XENO_HW_UNLOCKED_SWITCH=n I don't have any problems anymore.
--
Len Sorensen
next reply other threads:[~2011-12-23 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 17:33 Lennart Sorensen [this message]
2011-12-23 18:17 ` [Xenomai-core] CONFIG_XENO_HW_UNLOCKED_SWITCH=y causes random process corruption in xenomai 2.6.0 on powerpc Philippe Gerum
2011-12-23 18:32 ` Lennart Sorensen
2011-12-23 20:08 ` Philippe Gerum
2011-12-23 20:25 ` Lennart Sorensen
2011-12-23 21:48 ` Philippe Gerum
2011-12-23 21:55 ` Lennart Sorensen
2011-12-23 21:58 ` Philippe Gerum
2012-01-04 13:34 ` Philippe Gerum
2018-03-21 15:40 ` [Xenomai] " Frank Benkert
2018-03-21 16:40 ` Philippe Gerum
2018-03-22 7:22 ` Frank Benkert
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=20111223173309.GM27742@domain.hid \
--to=lsorense@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.