From: "Dmitry Adamushko" <dmitry.adamushko@domain.hid>
To: Maksym Veremeyenko <verem@domain.hid>
Cc: Xenomai help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Strange deadlock.
Date: Sat, 10 Feb 2007 00:53:31 +0100 [thread overview]
Message-ID: <b647ffbd0702091553w41f4ec9cne58a59206a58121d@domain.hid> (raw)
In-Reply-To: <45CCF15F.806@domain.hid>
> i try to move lock/unlock to macros and add some history logging.
>
> Is possible next scenario:
> 1. task A lock mutex M
> 2. task A going to secondary mode
> 3. task A performing "long" io wait operation and some flags modified.
> ...
What do you mean by "some flags modified" ?
Anyway, the "scenario" you have described is just not how it all works.
> BTW
> at some moment i got a kernel oops, not very informative but...
> ...
> Feb 9 23:26:02 dev-3 kernel: CPU: 0
> Feb 9 23:26:02 dev-3 kernel: EIP: 0060:[<c01b53b2>] Not tainted VLI
> Feb 9 23:26:02 dev-3 kernel: EFLAGS: 00210246 (2.6.17.14-xenomai #1)
> Feb 9 23:26:02 dev-3 kernel: EIP is at remove_proc_entry+0x22/0x1b0
> ...
> <c014476e> registry_proc_callback+0x17e/0x370
Does it happen at the time your application deletes some objects (e.g.
mutexes) ?
If it's not possible to get a simpler code fragment out of your
application to illustrate this problem, then maybe you could describe
some logic behind your application..
(how often each task acquires a lock / how long does it hold it and
what kind of actions does it do at this time, etc.)...
TIA,
--
Best regards,
Dmitry Adamushko
next prev parent reply other threads:[~2007-02-09 23:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 19:35 [Xenomai-help] Strange deadlock Maksym Veremeyenko
2007-02-09 20:54 ` 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 [this message]
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=b647ffbd0702091553w41f4ec9cne58a59206a58121d@domain.hid \
--to=dmitry.adamushko@domain.hid \
--cc=verem@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.