All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] ipipe: fix domain migration helper
Date: Wed, 16 Jan 2013 16:25:11 +0100	[thread overview]
Message-ID: <50F6C657.2060503@xenomai.org> (raw)
In-Reply-To: <50F6C3EE.1020508@siemens.com>

On 01/16/2013 04:14 PM, Jan Kiszka wrote:
> Hi Philippe,
>
> a first heads-up, maybe you have an idea before I start debugging: That
> patch causes troubles when our application shuts down. The main thread
> hangs like this, unkillable:
>

It looks like the LO_WAKEUP_REQ virtual interrupt does not reach the 
handler.

> # cat /proc/xenomai/sched
> CPU  PID    CLASS  PRI      TIMEOUT   TIMEBASE   STAT       NAME
>    0  0      idle    -1      -         master     R          ROOT/0
>    1  0      idle    -1      -         master     R          ROOT/1
>    2  0      idle    -1      -         master     R          ROOT/2
>    3  0      idle    -1      -         master     R          ROOT/3
>    4  0      idle    -1      -         master     R          ROOT/4
>    5  0      idle    -1      -         master     R          ROOT/5
>    6  0      idle    -1      -         master     R          ROOT/6
>    7  0      idle    -1      -         master     R          ROOT/7
>    8  0      idle    -1      -         master     R          ROOT/8
>    9  0      idle    -1      -         master     R          ROOT/9
>   10  0      idle    -1      -         master     R          ROOT/10
>   11  0      idle    -1      -         master     R          ROOT/11
>    0  2435   rt       0      -         master     X          ShadowTask_2435
> # cat /proc/2435/stack
> [<ffffffff810b5b94>] xnpod_suspend_thread+0x434/0x570
> [<ffffffff810beb30>] xnshadow_relax+0xe0/0x240
> [<ffffffff810c08e3>] losyscall_event+0x1c3/0x280
> [<ffffffff8109e73a>] ipipe_syscall_hook+0x5a/0x90
> [<ffffffff8109c311>] __ipipe_notify_syscall+0x131/0x2e0
> [<ffffffff8101e841>] __ipipe_syscall_root+0x41/0x160
> [<ffffffff8126a41a>] __ipipe_syscall_root_thunk+0x35/0x67
> [<ffffffffffffffff>] 0xffffffffffffffff
>
> This was with your current core-3.5 branch.
>
> I'm currently updating my virtual debug environment. The issue may also
> be reproducible with standard Xenomai tests.
>
> Jan
>


-- 
Philippe.


  reply	other threads:[~2013-01-16 15:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 15:14 [Xenomai] ipipe: fix domain migration helper Jan Kiszka
2013-01-16 15:25 ` Philippe Gerum [this message]
2013-01-16 15:30   ` Jan Kiszka
2013-01-16 15:52     ` Jan Kiszka
2013-01-16 19:07       ` Jan Kiszka

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=50F6C657.2060503@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@siemens.com \
    --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.