All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Fillod Stephane <stephane.fillod@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Xenomai v2.4-rc4: freeze with RTAI skin, fine with other skins
Date: Mon, 22 Oct 2007 11:53:12 +0200	[thread overview]
Message-ID: <471C7308.7020409@domain.hid> (raw)
In-Reply-To: <0B45E93C5FF65740AEAE690BF3848B7A4AB255@domain.hid>

Fillod Stephane wrote:
> Hi,
> 
> As Philippe has been suggesting it, I've been testing v2.4-rc4 on x86 
> (not favourite board though :) with the RTAI skin (not my favourite skin
> too).
> Anyway, a legacy RTAI application which was fine with v2.3.2/2.6.20, is
> now 
> freezing the box randomly in the first 30 seconds. On the other hand, 
> the programs from the testsuite are running stable. So we may rule out 
> a problem in the I-Pipe/kernel.
> 
> For the legacy RTAI application to load, the attached patch was
> necessary.
> The patch against ksrc/skins/rtai/shm.c is somewhat defeating the
> purpose
> of a lower XNCORE_PAGE_SIZE, so a better fix might be expected.
> 

This one should prevent -EINVAL from being returned. Hopefully.

--- ksrc/skins/rtai/shm.c	(revision 3095)
+++ ksrc/skins/rtai/shm.c	(working copy)
@@ -150,8 +150,7 @@
 	/* Account for the overhead so that the actual free space is
 	   large enough to match the requested size. */

-	heapsize += xnheap_overhead(heapsize, XNCORE_PAGE_SIZE);
-	heapsize = XNCORE_PAGE_ALIGN(heapsize);
+	heapsize = xnheap_rounded_size(heapsize, XNCORE_PAGE_SIZE);

 #ifdef CONFIG_XENO_OPT_PERVASIVE
 	err = xnheap_init_mapped(p->heap,

> The box is running FC5 on a pentium D, but kernel is compiled for UP.
> $ cat /proc/ipipe/version
> 1.10-09
> $ cat /proc/xenomai/version
> 2.4-rc4
> $ cat /proc/version
> Linux version 2.6.23.1 () (gcc version 4.1.1 20070105 (Red Hat
> 4.1.1-51))
> 
> The kernel config file is attached.
> 
> I'm currently stripping down the RTAI code out of the application
> in order to have a simple testbed reproducing the freeze.
> 
> In the mean time, does anyone have a clue where to look particularly?
> 

Hard to say at this point. Since the nucleus watchdog does not trigger,
you may want to try disabling X86_UP_IOAPIC while keeping X86_UP_APIC,
and arm the kernel NMI watchdog on the LAPIC (nmi_watchdog=2). You may
be lucky and have a backtrace after the freeze.

PS: maybe enabling all the nucleus debug options would catch something too.

> TIA
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core


-- 
Philippe.


  parent reply	other threads:[~2007-10-22  9:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22  9:16 [Xenomai-core] Xenomai v2.4-rc4: freeze with RTAI skin, fine with other skins Fillod Stephane
2007-10-22  9:29 ` Gilles Chanteperdrix
2007-10-22  9:53 ` Philippe Gerum [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-22  9:45 Fillod Stephane
2007-10-22 10:08 ` Philippe Gerum
2007-10-22 12:15 ` Gilles Chanteperdrix
2007-10-25 18:10 Fillod Stephane
2007-10-27 15:02 ` Philippe Gerum
2007-10-30 15:07 Fillod Stephane
2007-10-30 15:17 ` 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=471C7308.7020409@domain.hid \
    --to=rpm@xenomai.org \
    --cc=stephane.fillod@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.