From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: roderik.wildenburg@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Some problems with shared memory
Date: Fri, 29 May 2009 20:42:21 +0200 [thread overview]
Message-ID: <4A202C8D.9000605@domain.hid> (raw)
In-Reply-To: <5D63919D95F87E4D9D34FF7748CE2C2A0198FC6F@ARVMAIL1.mra.roland-man.biz>
roderik.wildenburg@domain.hid wrote:
>> All I want to hear is "yes, we ran the shm test without Xenomai, on
>> exactly the same kernel, on the same platform, and the shm
>> test worked".
>> Because Xenomai runs plain Linux mmap under the hood and do no
>> particular check on the mmap length. So, the problem is either that
>> Linux mmap on that particular machine with that particular
>> kernel does a
>> check on length, or that there is a subtle bug somewhere that I do not
>> want to investigate until I am usre that it is real.
>
>
> yes, we ran the shm test without Xenomai, on
> exactly the same kernel, on the same platform, and the shm
> test worked.
>
> This means :
> I took a plain 2.4.25 PPC-Kernel and started killtest without pagealigned shm size and got the error message :
> shm_open fails. errno=38 SHM:/testshm
> shm_open: Function not implemented
>
> Therefore I mounted a tmpfs on /dev/shm and killtest ran without any errormessage.
> To make shure the missing /dev/shm isn´t the reason for the mmap-error I took a xenomai-enhanced kernel, mounted /dev/shm and run (a xenomai-linked) killtest, but I still got the error :
> killtest2 # ./killtest -c
> createshm mmap: No such device or address
> shmsize = 100000; errno : 6 == Failed to create shm : -3
> killtest user exit !
>
> This I tried with Xenomai 2.3.5 and 2.4.7 (and got the same error).
> Even on a Xenomai-enhanced kernel a killtest, which was linked without Xenomai-libraries, run without error.
>
> Sorry for not having better news
> Roderik
Hi,
this should have been fixed in the 2.4.8 release, so please test it and
tell us whether it works for you.
--
Gilles.
next prev parent reply other threads:[~2009-05-29 18:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 9:31 [Xenomai-help] Some problems with shared memory roderik.wildenburg
2009-03-30 12:14 ` Gilles Chanteperdrix
2009-03-31 11:52 ` roderik.wildenburg
2009-04-06 8:47 ` roderik.wildenburg
2009-05-03 20:21 ` Gilles Chanteperdrix
2009-05-04 7:23 ` Wolfgang Denk
2009-05-04 8:49 ` Gilles Chanteperdrix
2009-05-04 15:24 ` Thomas Lockhart
2009-05-04 18:01 ` Wolfgang Denk
2009-05-04 18:33 ` Gilles Chanteperdrix
2009-05-05 12:16 ` roderik.wildenburg
2009-05-29 18:42 ` Gilles Chanteperdrix [this message]
2009-06-08 8:25 ` roderik.wildenburg
2009-06-08 20:36 ` Gilles Chanteperdrix
2009-06-09 6:30 ` roderik.wildenburg
2009-06-09 13:28 ` Philippe Gerum
2009-06-09 13:38 ` Philippe Gerum
2009-06-10 11:47 ` roderik.wildenburg
2009-06-12 14:06 ` Philippe Gerum
2009-06-16 13:20 ` roderik.wildenburg
2009-06-16 13:45 ` Philippe Gerum
2009-06-17 11:40 ` roderik.wildenburg
2009-06-17 14:19 ` Philippe Gerum
2009-06-18 8:37 ` roderik.wildenburg
2009-06-18 8:51 ` Philippe Gerum
2009-05-05 16:36 ` Thomas Lockhart
2009-05-05 19:03 ` Wolfgang Denk
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=4A202C8D.9000605@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=roderik.wildenburg@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.