Fillod Stephane wrote:
> 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
> Anyway, a legacy RTAI application which was fine with v2.3.2/2.6.20, is
> 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
> The patch against ksrc/skins/rtai/shm.c is somewhat defeating the
> 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);
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
> $ cat /proc/xenomai/version
> $ cat /proc/version
> Linux version 18.104.22.168 () (gcc version 4.1.1 20070105 (Red Hat
> 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.
> Xenomai-core mailing list
Xenomai-core mailing list