From: Philippe Gerum <rpm@xenomai.org>
To: Mark Saiia <mark.saiia@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] ipipe error
Date: Thu, 05 Mar 2009 10:55:35 +0100 [thread overview]
Message-ID: <49AFA197.9090704@domain.hid> (raw)
In-Reply-To: <67b6b3430903041631p107682bdyf5d5fb9c0e70d86d@domain.hid>
Mark Saiia wrote:
> When running 2.6.27.19 w/ Xenomai 2.4.7 on a geode board, I get the
> following in the log. I haven't done any debugging yet, but wanted to
> see if anyone else has this issue. It results in some of the
> application threads not being responsive, while others are still
> running.
>
Is CONFIG_FRAME_POINTER enabled for your kernel, i.e. can we trust the backtrace
below?
Additionally, what happens if you stop asking rt_task_set_mode() to clear
primary mode via toggling the T_PRIMARY flag? (which you should very likely NOT
do, btw. Forcing the current mode is counter-productive most of the time; this
is an internal feature for very, very specific needs of some Xenomai library code).
> ar 5 15:08:22 (none) user.err kernel: I-pipe: Detected illicit call
> from domain 'Xenomai'
> Mar 5 15:08:22 (none) user.err kernel: into a service
> reserved for domain 'Linux' and below.
> Mar 5 15:08:22 (none) user.warn kernel: Pid: 990, comm: main thread
> Not tainted 2.6.27.19-standard-xenomai #1
> Mar 5 15:08:22 (none) user.warn kernel: [<c0146d3d>]
> ipipe_check_context+0x8d/0xb0
> Mar 5 15:08:22 (none) user.warn kernel: [<c0115535>]
> sub_preempt_count+0x15/0x80
> Mar 5 15:08:22 (none) user.warn kernel: [<c0115e1e>]
> finish_task_switch+0x2e/0x80
> Mar 5 15:08:22 (none) user.warn kernel: [<c01172ba>]
> ipipe_reenter_root+0x1a/0x60
> Mar 5 15:08:22 (none) user.warn kernel: [<c0155a2d>] xnshadow_relax+0x9d/0x100
> Mar 5 15:08:22 (none) user.warn kernel: [<c015e9b7>]
> __rt_task_set_mode+0x67/0x90
> Mar 5 15:08:22 (none) user.warn kernel: [<c0155dd7>]
> losyscall_event+0xb7/0x170
> Mar 5 15:08:22 (none) user.warn kernel: [<c0155d20>] ?
> losyscall_event+0x0/0x170
> Mar 5 15:08:22 (none) user.warn kernel: [<c0148150>]
> __ipipe_dispatch_event+0xd0/0x220
> Mar 5 15:08:22 (none) user.warn kernel: [<c010d54a>]
> __ipipe_syscall_root+0x3a/0xe0
> Mar 5 15:08:22 (none) user.warn kernel: [<c010320b>] system_call+0x2b/0x4c
> Mar 5 15:08:22 (none) user.warn kernel: =======================
> Mar 5 15:08:22 (none) user.warn kernel: ------------[ cut here ]------------
> Mar 5 15:08:22 (none) user.warn kernel: WARNING: at
> kernel/sched.c:4322 sub_preempt_count+0x7d/0x80()
> Mar 5 15:08:22 (none) user.warn kernel: Modules linked in: ipv6
> eepro100 mii genrtc usb_storage nls_iso8859_1 nls_cp437
> Mar 5 15:08:22 (none) user.warn kernel: Pid: 990, comm: main thread
> Not tainted 2.6.27.19-standard-xenomai #1
> Mar 5 15:08:22 (none) user.warn kernel: [<c011b746>]
> warn_on_slowpath+0x46/0x60
> Mar 5 15:08:22 (none) user.warn kernel: [<c010320b>] ? system_call+0x2b/0x4c
> Mar 5 15:08:22 (none) user.warn kernel: [<c011cc71>] ? printk+0x41/0x180
> Mar 5 15:08:22 (none) user.warn kernel: [<c0103c85>] ?
> show_trace_log_lvl+0x25/0x30
> Mar 5 15:08:22 (none) user.warn kernel: [<c0101e5a>] ? __switch_to+0xa/0x150
> Mar 5 15:08:22 (none) user.warn kernel: [<c0146d42>] ?
> ipipe_check_context+0x92/0xb0
> Mar 5 15:08:22 (none) user.warn kernel: [<c0115535>] ?
> sub_preempt_count+0x15/0x80
> Mar 5 15:08:22 (none) user.warn kernel: [<c011559d>]
> sub_preempt_count+0x7d/0x80
> Mar 5 15:08:22 (none) user.warn kernel: [<c0115e1e>]
> finish_task_switch+0x2e/0x80
> Mar 5 15:08:22 (none) user.warn kernel: [<c01172ba>]
> ipipe_reenter_root+0x1a/0x60
> Mar 5 15:08:22 (none) user.warn kernel: [<c0155a2d>] xnshadow_relax+0x9d/0x100
> Mar 5 15:08:22 (none) user.warn kernel: [<c0155e08>]
> losyscall_event+0xe8/0x170
> Mar 5 15:08:22 (none) user.warn kernel: [<c0155d20>] ?
> losyscall_event+0x0/0x170
> Mar 5 15:08:22 (none) user.warn kernel: [<c0148150>]
> __ipipe_dispatch_event+0xd0/0x220
> Mar 5 15:08:22 (none) user.warn kernel: [<c010d54a>]
> __ipipe_syscall_root+0x3a/0xe0
> Mar 5 15:08:22 (none) user.warn kernel: [<c010320b>] system_call+0x2b/0x4c
> Mar 5 15:08:22 (none) user.warn kernel: =======================
> Mar 5 15:08:22 (none) user.warn kernel: ---[ end trace 37b08dd71b141ea9 ]---
> Mar 5 15:08:22 (none) user.emerg rtlogd: : StopScan()
>
> Thanks,
>
> Mark
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>
--
Philippe.
next prev parent reply other threads:[~2009-03-05 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 0:31 [Xenomai-help] ipipe error Mark Saiia
2009-03-05 9:55 ` Philippe Gerum [this message]
2009-03-05 11:45 ` Steven Seeger
2009-03-05 13:11 ` Gilles Chanteperdrix
2009-03-05 13:40 ` Steven Seeger
2009-03-05 17:12 ` Steven Seeger
2009-03-05 18:00 ` 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=49AFA197.9090704@domain.hid \
--to=rpm@xenomai.org \
--cc=mark.saiia@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.