From: Kai Moritz <kai.m.moritz@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-help] Problems with mutex
Date: Wed, 30 Nov 2005 13:21:18 +0100 [thread overview]
Message-ID: <438D993E.7010904@domain.hid> (raw)
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
Hello folks,
I'm using Xenomai 2.0.1 with Linux 2.6.14 and ipipe. I've a strange
problem using mutex-locks. Repeted calls to rt_mutex_lock with
TM_NONBLOCK on the same mutex return always 0, which means lock
successfully aquired, if I understand the API-documentation right.
I've attached a small programm to test that behavior and the
log-messages it produces on my machine. Perhaps anyone has a hint, what
I'm doing wrong...
Greetings Kai Moritz
[-- Attachment #2: mutex.tgz --]
[-- Type: application/x-gtar, Size: 1759 bytes --]
[-- Attachment #3: messages --]
[-- Type: text/plain, Size: 2250 bytes --]
Nov 29 19:35:47 localhost kernel: mutex: module initialization... mutex: creating mutex... done!
Nov 29 19:35:47 localhost kernel: mutex: initializing test thread... done.
Nov 29 19:35:47 localhost kernel: mutex: starting rt timer (one shot mode)... done.
Nov 29 19:35:47 localhost kernel: mutex: starting test thread...
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 0th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 1th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 2th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 3th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 4th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 5th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 6th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 7th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 8th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 9th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 10th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 11th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 12th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 13th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 14th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 15th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 16th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 17th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 18th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: locking mutex the 19th time...done: 0!
Nov 29 19:35:47 localhost kernel: mutex: all tests done!
Nov 29 19:35:47 localhost kernel: mutex: test thread successfully started.
Nov 29 19:35:47 localhost kernel: mutex: module initialization done.
Nov 29 19:35:47 localhost kernel: mutex: deleting mutex... done!
Nov 29 19:35:47 localhost kernel: mutex: module cleanup done.
next reply other threads:[~2005-11-30 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 12:21 Kai Moritz [this message]
2005-11-30 12:29 ` [Xenomai-help] Problems with mutex Jan Kiszka
2005-11-30 12:53 ` Kai Moritz
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=438D993E.7010904@domain.hid \
--to=kai.m.moritz@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.