From: Paolo Minazzi <Paolo.Minazzi@mitrol.it>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] fault in ppd_lookup_inner
Date: Wed, 25 Mar 2015 10:11:13 +0100 [thread overview]
Message-ID: <55127BB1.7040804@mitrol.it> (raw)
In-Reply-To: <20150325090354.GG15125@hermes.click-hack.org>
Il 25/03/2015 10:03, Gilles Chanteperdrix ha scritto:
> On Wed, Mar 25, 2015 at 09:59:52AM +0100, Paolo Minazzi wrote:
>> Il 25/03/2015 09:36, Gilles Chanteperdrix ha scritto:
>>> On Wed, Mar 25, 2015 at 09:21:24AM +0100, Paolo Minazzi wrote:
>>>> Hello all,
>>>> I'm stressing an arm IMX6 boardwith
>>>> - kernel 3.0.35
>>>> - I-pipe 1.18-13
>>>> - xenomai 2.6.3
>>> Do you observe the same behaviour with Xenomai 2.6.4 ?
>>>
>> I have added all fix of 2.6.4 to my 2.6.3 (seeing changelog) but I have the
>> same behaviour.
>> It is not easy see the problem.
> Why not simply testing 2.6.4, with everything, not only what appear
> as fixes?
>
> Also, do you have the same problem if you dlopen something more
> innocuous than libvncserver ?
>
I understand ... I port the fix to avoid compatililityproblem.
I made only ksrc changes, so my user space is 100% compatible.
I understand that you do not agree with me because you prefer a clean 2.6.4.
I can try an other library. Do you mean a smaller library?
This is a strange test. I'm trying it because in the past I have had
some memory corruption that make system instable.
I would like to be sure about it.
Paolo
next prev parent reply other threads:[~2015-03-25 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 8:21 [Xenomai] fault in ppd_lookup_inner Paolo Minazzi
2015-03-25 8:36 ` Gilles Chanteperdrix
2015-03-25 8:59 ` Paolo Minazzi
2015-03-25 9:03 ` Gilles Chanteperdrix
2015-03-25 9:07 ` Gilles Chanteperdrix
2015-03-25 9:11 ` Paolo Minazzi [this message]
2015-03-25 9:20 ` Gilles Chanteperdrix
2015-03-25 9:51 ` Paolo Minazzi
2015-03-25 13:28 ` Philippe Gerum
2015-03-25 14:23 ` Paolo Minazzi
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=55127BB1.7040804@mitrol.it \
--to=paolo.minazzi@mitrol.it \
--cc=gilles.chanteperdrix@xenomai.org \
--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.