All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maksym Veremeyenko <verem@domain.hid>
To: Xenomai-help@domain.hid
Subject: [Xenomai-help] Strange deadlock.
Date: Fri, 09 Feb 2007 21:35:44 +0200	[thread overview]
Message-ID: <45CCCD10.9000008@domain.hid> (raw)

Hi!

I found dead lock in my program and looking for reason, but i found 
something strange. Is possible mutex state looks like:
[root@domain.hid /]# cat /proc/xenomai/registry/native/mutexes/coll_VDCP_1
=locked by bus_monitor_proc[0] depth=1
+vdcp[0030]m
+bus_monitor_proc[0]

seems bus_monitor_proc[0] locked mutex and want to lock again but its 
blocked.  (i still looking for stack corruption point, but no success.) 
It have the same behavior on two configuration 2.6.17.4 + 2.2.4 and 
2.6.19.2 + 2.3.0 + 1.7-01
i checked with GDB - two task are wating for mutex.
All task perform switching to secondary mode.


Also have a questions:

1. On program start after previous crash i unable to create named mutex, 
because it [-EEXIST], after bind it's unable to operate with it because 
it locked by task from early died program, i have to restart computer. 
Any suggestions?

2. Does exist API function to detect mutex owner?



-- 
________________________________________
Maksym Veremeyenko



             reply	other threads:[~2007-02-09 19:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 19:35 Maksym Veremeyenko [this message]
2007-02-09 20:54 ` [Xenomai-help] Strange deadlock Philippe Gerum
2007-02-09 21:39   ` Maksym Veremeyenko
2007-02-09 21:14 ` Dmitry Adamushko
2007-02-09 22:10   ` Maksym Veremeyenko
2007-02-09 23:53     ` Dmitry Adamushko
2007-02-10  4:07 ` Maksym Veremeyenko
2007-02-10 10:34   ` Jan Kiszka
2007-02-11 18:28     ` Maksym Veremeyenko
2007-02-11 19:05       ` Philippe Gerum

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=45CCCD10.9000008@domain.hid \
    --to=verem@domain.hid \
    --cc=Xenomai-help@domain.hid \
    /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.