All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Kisdaroczi <kisda@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] crash after termination
Date: Mon, 22 Mar 2010 11:36:16 +0100	[thread overview]
Message-ID: <4BA74820.2090401@domain.hid> (raw)
In-Reply-To: <4BA4EF75.7010202@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]

Am 20.03.2010 16:53, schrieb Jan Kiszka:
> Stefan Kisdaroczi wrote:
>> hi all,
>>
>> after termination of my xenomai applications, my box crashed often (3 of 4 times) with xenomai 2.5.1.
>> Today I updated to current git-2.5, rebuilt xenomai and the kernel. Still crashes.
>> I have captured two traces over a serial connection. I have attached the kernel config, the two
>> traces and the cpuinfo (UP x86 Pentium III). Help is welcome. Thank you.
> 
> Both crashes seem to be caused by corrupted skbs. There are (at least)
> two uncommon network component in your kernel: ARCNET and ISDN. Do you
> make use of them or are they just passively loaded? If the former: Can

Just passively loaded.

> you retry without them? >(The Kernel's ISDN stuff is of, well, mixed
> quality, and ARCNET is so old and uncommon that the code /may/ have
> bit-rotted -

I disable them.

> just an attempt to detract the attention from Xenomai. :) )

I think the problem is in my apps, but I had some hope that
some changes for 2.5.2 (about thread cleanup,fork) would help.

> What other network components are actively involved in your scenario?

Only TCP/IP (non-realtime). Currently a dozen xenomai native tasks are
doing standard socket calls. If everything works, there will be about
60 tasks using socket calls, but its still a long way.

I focus now first on another problem I have in my apps with a shared heap,
so one question about that: There was no H_NONCACHED flag at the time I
did write some library code. I use a rt_heap as shared memory between 8
processes on x86. According to the documentation H_NONCACHED is only
relevant for ARM, is that true?

Thanks for the help Jan.
Stefan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

  reply	other threads:[~2010-03-22 10:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 15:46 [Xenomai-help] crash after termination Stefan Kisdaroczi
2010-03-20 15:53 ` Jan Kiszka
2010-03-22 10:36   ` Stefan Kisdaroczi [this message]
2010-03-23  8:00     ` Jan Kiszka
2010-03-23 13:25       ` Stefan Kisdaroczi
2010-03-23 17:06         ` Jan Kiszka
2010-03-23 17:15           ` Gilles Chanteperdrix
2010-03-23 17:23             ` Jan Kiszka
2010-03-24  2:54               ` [Xenomai-help] Problem in irq_handle robert165
2010-03-24 10:22                 ` Gilles Chanteperdrix
2010-03-25  2:55                   ` robert165
2010-03-25  7:55                     ` Gilles Chanteperdrix
2010-03-25 12:50                       ` robert165
2010-03-25 13:49                         ` Gilles Chanteperdrix
2010-03-25 14:28                           ` 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=4BA74820.2090401@domain.hid \
    --to=kisda@domain.hid \
    --cc=jan.kiszka@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.