From: Lars Segerlund <lars.segerlund@gmail.com>
To: linux-rt-users@vger.kernel.org
Subject: some rt-preempt help if possible.
Date: Thu, 26 Apr 2012 22:27:30 +0200 [thread overview]
Message-ID: <CAF-VNap+wE=dPy-J7BcZhS7K9AZRBW61TC0-7gAVuoqUzu-e_g@mail.gmail.com> (raw)
Hi Everyone,
The linux cnc is trying to port their software to rt preempt, however
there is a patched version for emc 2.4 that works ok, and when these
patches are brought to emc 2.5 it hangs on startup.
Aparently it's a mutex that hangs.
Now any help or pointers would be appreciated, particulary on how to
debug a mutex hang ....
Roughly the same code runs ok in the old version, and most people on
the linuxcnc list are only familiar with RTLinux and RTAI. Any help
appreciated, since the code is still 'wet', so this is a small call
for help is someone feels like it.
If it's of topic, or not interesting please ignore.
http://news.gmane.org/gmane.linux.distributions.emc.devel
/ regards, Lars Segerlund
reply other threads:[~2012-04-26 20:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAF-VNap+wE=dPy-J7BcZhS7K9AZRBW61TC0-7gAVuoqUzu-e_g@mail.gmail.com' \
--to=lars.segerlund@gmail.com \
--cc=linux-rt-users@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).