From: Stephan Zimmermann <s.zimmermann@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] fata: removing non-linked element...
Date: Fri, 09 Feb 2007 15:04:34 +0100 [thread overview]
Message-ID: <45CC7F72.5020706@domain.hid> (raw)
In-Reply-To: <45CC68F3.1000003@domain.hid>
Jan Kiszka schrieb:
> Stephan Zimmermann wrote:
>> Hi,
>> I just saw the following errormessages while running some tests with my
>> application.
>>
>> "Xenoami: fatal: removing non-linked element, holder=ef9a5794
>> qslot=f96f70d0 at include/xenoami/nucleus/queue.h:422"
>> "Xenomai: Stuck on nucleus lock f96f6380"
>
> I guess you had to hand-copy the message. There should be some back
> trace following that is annoying to type. Maybe you can capture it with
> a serial console (if your machine still has "legacy" interfaces). Or,
> even better, you try to derive a demo code for triggering the bug.
Sorry, no Backtrace available, the machine crashes so abrupt, that I
just saw the console stop in the middle of a line (letters cut throgh
from left to right...). I am trying to work out some demo code.
By the way, same app on my Pentium M (same softwareversions), won't
crash but tells me " Xenomai: Switching MAINTASK to secondary mode after
exception #14 from user-space at 0xb7f5b352 (pid 9600)"
>> Followed by pressing the reset-button...
>>
>> I Run Xenomai 2.3 rev 2139 on AMD X2, kernel 2.6.17.14, debian sarge.
>>
>> May this be due to an misbehaviour in my app, or does it look like
>> something xenomai related? I am not sure how to interpret these messages.
>
> This is nothing your application should be allowed to cause.
>
> Jan
>
next prev parent reply other threads:[~2007-02-09 14:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 12:12 [Xenomai-help] fata: removing non-linked element Stephan Zimmermann
2007-02-09 12:28 ` Jan Kiszka
2007-02-09 14:04 ` Stephan Zimmermann [this message]
2007-02-13 13:36 ` Stephan Zimmermann
2007-02-13 13:42 ` Stephan Zimmermann
2007-02-13 14:07 ` Jan Kiszka
2007-02-13 14:25 ` Philippe Gerum
2007-02-13 14:28 ` Jan Kiszka
2007-02-13 14:47 ` Philippe Gerum
2007-02-13 16:55 ` Philippe Gerum
2007-02-13 18:17 ` Jan Kiszka
2007-02-13 18:58 ` Philippe Gerum
2007-02-16 12:12 ` Stephan Zimmermann
2007-02-16 17:06 ` Jan Kiszka
2007-02-16 17:58 ` Jan Kiszka
2007-02-16 18:15 ` Philippe Gerum
2007-02-16 18:25 ` Jan Kiszka
2007-02-16 18:34 ` Philippe Gerum
2007-02-16 18:38 ` Jan Kiszka
2007-02-16 18:47 ` Philippe Gerum
2007-02-22 13:27 ` Stephan Zimmermann
2007-02-22 13:50 ` Jan Kiszka
2007-02-22 15:49 ` Stephan Zimmermann
2007-02-16 17:11 ` Jan Kiszka
2007-02-09 13:44 ` Gilles Chanteperdrix
2007-02-09 14:08 ` Stephan Zimmermann
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=45CC7F72.5020706@domain.hid \
--to=s.zimmermann@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.