From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4B8C26F7.3020306@domain.hid> Date: Mon, 01 Mar 2010 21:43:35 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <4B86EDC2.7010905@domain.hid> <4B86FCBB.10203@domain.hid> <4B86FFA0.3000403@domain.hid> <4B870134.2040802@domain.hid> <4B87FC70.90903@domain.hid> <4B8C2490.1040604@domain.hid> <4B8C25B9.8090705@domain.hid> In-Reply-To: <4B8C25B9.8090705@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig7C181BFDE241B7C5490F9133" Sender: jan.kiszka@domain.hid Subject: Re: [Xenomai-help] mlockall error after calling mlockall() List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: "xenomai@xenomai.org" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7C181BFDE241B7C5490F9133 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Gilles Chanteperdrix wrote: > Jan Kiszka wrote: >> Charlton, John wrote: >>> I added some printk output to the cond.c file in xenomai-2.5.1 and it= shows that xnsync_sleep_on returned -ETIMEDOUT as it should: >>> Xenomai: registered exported object M1-1908 (mutexes) >>> Xenomai: registered exported object C1-1908 (condvars) >>> xnsynch_sleep_on returned: -110 >>> xnsynch_sleep_on returned: -110 >>> xnsynch_sleep_on returned: -110 >>> xnsynch_sleep_on returned: -110 >>> xnsynch_sleep_on returned: -110 >>> xnsynch_sleep_on returned: -110 >>> xnsynch_sleep_on returned: -4 >>> Xenomai: native: cleaning up cond "C1-1908" (ret=3D0). >>> Xenomai: unregistered exported object C1-1908 (condvars) >>> Xenomai: native: cleaning up mutex "M1-1908" (ret=3D0). >>> Xenomai: unregistered exported object M1-1908 (mutexes) >>> Xenomai: POSIX: destroyed thread df5a0800 >>> >>> I put the printk on line cond.c:433 after err is set in rt_cond_wait_= prologue(): >>> >>> info =3D xnsynch_sleep_on(&cond->synch_base, >>> timeout, timeout_mode); >>> if (info & XNRMID) >>> err =3D -EIDRM; /* Condvar deleted while pending. */ >>> else if (info & XNTIMEO) { >>> err =3D -ETIMEDOUT; /* Timeout. */ >>> } >>> else if (info & XNBREAK) { >>> err =3D -EINTR; /* Unblocked. */ >>> } >>> printk(KERN_DEBUG "xnsynch_sleep_on returned: %d\n", err); >>> >>> I put a printk in rt_cond_wait_inner() which is called directly by rt= _cond_wait() from user mode but did not see the output in the dmesg outpu= t for that one. >> One of our problems is the prologue/epilogue split up (both in kernel >> and user space): the epilogue can eat the error code or the prologue, >> including the -ETIMEDOUT. >=20 > Ah. My fault. Looks user-space is Ok though. Only kernel-space has a > problem. >=20 Both are affected. Could you help me with what issues 97323b3287b5ee8cad99a7fa67cd050bc51f76c4 should fix? Jan --------------enig7C181BFDE241B7C5490F9133 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkuMJvcACgkQitSsb3rl5xT2ugCfZlQfOOZQWT7vFmeAoHc02Q6E cG8An1K2nCquO661OJQVNlvzlUrlY0D6 =43iz -----END PGP SIGNATURE----- --------------enig7C181BFDE241B7C5490F9133--