All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: xenoka09@domain.hid
Cc: Xenomai GNA <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] 2.5.3++ on Blackfin: Irritating warning
Date: Tue, 21 Dec 2010 10:24:46 +0100	[thread overview]
Message-ID: <1292923486.2007.50.camel@domain.hid> (raw)
In-Reply-To: <alpine.DEB.1.10.1012210952150.8962@domain.hid>

On Tue, 2010-12-21 at 10:03 +0100, Kolja Waschk wrote:
> Hi,
> 
> I'm in the process of upgrading my Blackfin uclinux dist base from 2009R1.1 to 2010R1. This also includes a kernel and Xenomai upgrade.
> 
> The kernel is now 2.6.34 with I-pipe 1.14.02. With Xenomai 2.5.3, my application told me "Xenomai: User-space support anterior to 2.5.2 detected" on startup. I looked into newer Xenomai and found that there might have been related code changes, so I tried 2.5.5.2 (and also upgraded to I-pipe 1.15-01, but that doesn't seem to make a difference).
> 
> Now with 2.5.5.2, the warning when starting the application is gone, but I still get one when killing the application using SIGINT for the first time. The attached small example allows me to reliably reproduce the problem (please inform me if attachment didn't get through, it's only 30 lines).
> 
> When starting it after system reboot and then killing it with Ctrl-C after a few seconds, the warning is printed:
> 
> / # /tmp/try
> press ctrl-c to stop
> press ctrl-c to stop
> press ctrl-c to stop
> ^CXenomai: User-space support anterior to 2.5.2 detected, may corrupt memory upon
> thread termination. Upgrade is recommended
> / #
> 
> The warning doesn't appear when starting and killing "try" a the second time.

Mmf, commit 90b3e7cf6 does not do what it says it does. It should read:

diff --git a/ksrc/nucleus/shadow.c b/ksrc/nucleus/shadow.c
index 5ac182b..449a9a4 100644
--- a/ksrc/nucleus/shadow.c
+++ b/ksrc/nucleus/shadow.c
@@ -2214,7 +2214,7 @@ static void handle_shadow_exit(void)
 	 */
 	if (thread->u_mode && !warned) {
 		warned = 1;
-#ifndef CONFIG_MMU
+#ifdef CONFIG_MMU
 		printk(KERN_WARNING
 		       "Xenomai: User-space support anterior to 2.5.2"
 		       " detected, may corrupt memory upon\n"
> 
> I also experience some other problems with debugging, console output duplication and (probably) memory fragmentation, maybe they're related but I have not been able to reproduce them with a small example yet.
> 
> Thanks in advance for any hints in advance!
> Kolja
> _______________________________________________ Xenomai-help mailing list Xenomai-help@domain.hid https://mail.gna.org/listinfo/xenomai-help

-- 
Philippe.




      reply	other threads:[~2010-12-21  9:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21  9:03 [Xenomai-help] 2.5.3++ on Blackfin: Irritating warning Kolja Waschk
2010-12-21  9:24 ` Philippe Gerum [this message]

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=1292923486.2007.50.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=xenoka09@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.