All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Webb <jeff.webb@domain.hid>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Xenomai v2.2.3
Date: Wed, 20 Sep 2006 13:24:20 -0500	[thread overview]
Message-ID: <45118754.3000001@domain.hid> (raw)
In-Reply-To: <1158768864.5043.31.camel@domain.hid>

Philippe Gerum wrote:
> On Wed, 2006-09-20 at 09:44 -0500, Jeff Webb wrote:
> 
>> Switching to xenomai-2.2.3/linux-2.4.32 (ipipe-1.2) fixed this problem.
> 
> Could you try running 2.2.3 stock + fpu fix patch over 2.4.33.3/1.3-00,
> and 2.2.3 stock over 2.4.33.3/1.2-08 ? I'm trying to find out if there
> is a dependency on the kernel version, and/or the Adeos release, and/or
> the fpu issue, for the segfault bug. TIA,

I just tested two more builds.  Both of them have the segfault bug.  Here is a summary of the results thus far:

Latency test works:
  linux-2.4.32, adeos-ipipe-2.4.32-i386-1.2-07.patch

Latency test segfaults:
  linux-2.4.33.3, adeos-ipipe-2.4.33-i386-1.3-00.patch
  linux-2.4.33.3, adeos-ipipe-2.4.33-i386-1.2-07.patch
  linux-2.4.33.3 (+ FPU fix patch), adeos-ipipe-2.4.33-i386-1.3-00.patch

All of these are with xenomai-2.2.3.  The last one has the FPU fix patch applied.  So, it appears to be something in the newer kernel version...

Thanks,

Jeff




  reply	other threads:[~2006-09-20 18:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-18  7:28 [Xenomai-core] Xenomai v2.2.3 Philippe Gerum
2006-09-18 21:58 ` [Xenomai-help] " Jeff Webb
2006-09-19 22:01   ` Jeff Webb
2006-09-20  9:24     ` Philippe Gerum
2006-09-20 14:44       ` Jeff Webb
2006-09-20 15:22         ` Philippe Gerum
2006-09-20 16:14         ` Philippe Gerum
2006-09-20 18:24           ` Jeff Webb [this message]
2006-09-20 18:33             ` Philippe Gerum
2006-09-20 20:02               ` Jeff Webb
2006-09-20 20:19                 ` Jeff Webb

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=45118754.3000001@domain.hid \
    --to=jeff.webb@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.