All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Bart Vissers <bvissers@e2mtechnologies.eu>
Cc: Michael Smith <2michael.smith@gmail.com>, xenomai@xenomai.org
Subject: Re: [Xenomai] Failed testsuite/latency
Date: Tue, 24 Feb 2015 15:37:49 +0100	[thread overview]
Message-ID: <54EC8CBD.6000500@xenomai.org> (raw)
In-Reply-To: <CAB+DZ3=s-pHrt=U_YN5qYo7Vtic9f-WfQQBwK3znBTdN_iVOmw@mail.gmail.com>

On 02/24/2015 02:28 PM, Bart Vissers wrote:
> Hi,
> 
> I ran into the exact same error. My setup:
> - xenomai_3.0rc3
> - Linux kernel 3.16.7 with ipipe-core-3.16-x86-2.patch
> I only deviated from the default build guide to build debian packages.
> 
> Attached, is the kernel config, dmesg log (no errors) and strace output.
> 

I can't reproduce it, so I will need more information.

Could you send the output of the following command on your target?

# xeno-config --info

I would also need a portion of the namelist of the latency binary, e.g.

$ nm $XENOMAI_ROOT/bin/latency | grep __wrap
         U __wrap_clock_gettime
         U __wrap_close
         U __wrap_fclose
         U __wrap_fprintf
         U __wrap_free
         U __wrap_fwrite
         U __wrap_ioctl
         U __wrap_kill
         U __wrap_open
         U __wrap_printf
         U __wrap_pthread_create
         U __wrap_pthread_join
         U __wrap_pthread_setname_np
         U __wrap_puts
         U __wrap_read
         U __wrap_sem_close
         U __wrap_sem_open
         U __wrap_sem_post
         U __wrap_sem_unlink
         U __wrap_sem_wait
         U __wrap_time
         U __wrap_timerfd_create
         U __wrap_timerfd_settime
         U __wrap_write

And finally, could you patch this snippet into the target kernel, then
report any message that might appear in the log once latency has exited
on failure?

diff --git a/kernel/cobalt/rtdm/fd.c b/kernel/cobalt/rtdm/fd.c
index 7f35ea3..a65f6a0 100644
--- a/kernel/cobalt/rtdm/fd.c
+++ b/kernel/cobalt/rtdm/fd.c
@@ -210,6 +210,8 @@ struct rtdm_fd *rtdm_fd_get(int ufd, unsigned int magic)
 	xnlock_get_irqsave(&fdtree_lock, s);
 	fd = fetch_fd(p, ufd);
 	if (fd == NULL || (magic != 0 && fd->magic != magic)) {
+		printk(XENO_WARNING "%s: bad ufd=%d, magic=%#x\n",
+		       __func__, ufd, fd ? fd->magic : 0xfefefefe);
 		fd = ERR_PTR(-EBADF);
 		goto out;
 	}

-- 
Philippe.


  reply	other threads:[~2015-02-24 14:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 12:30 [Xenomai] Failed testsuite/latency Michael Smith
2015-02-23 12:38 ` Gilles Chanteperdrix
2015-02-23 14:23   ` Michael Smith
2015-02-23 16:00 ` Philippe Gerum
2015-02-24 13:28   ` Bart Vissers
2015-02-24 14:37     ` Philippe Gerum [this message]
2015-02-25  8:33       ` Bart Vissers
2015-02-25  9:24         ` Philippe Gerum
2015-02-25  9:32           ` Gilles Chanteperdrix
2015-02-26  6:05             ` Michael Smith
2015-02-26  6:20           ` Michael Smith
2015-02-26  6:07         ` Michael Smith
2015-03-02 14:56         ` Philippe Gerum
2015-03-03 15:29           ` Philippe Gerum
2015-03-03 15:46             ` Philippe Gerum
2015-03-03 19:18               ` Philippe Gerum
2015-03-03 19:29                 ` Helder Daniel
2015-03-03 19:43                   ` Philippe Gerum
2015-03-05 12:04                     ` Helder Daniel
2015-03-05 13:33                       ` Philippe Gerum

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=54EC8CBD.6000500@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=2michael.smith@gmail.com \
    --cc=bvissers@e2mtechnologies.eu \
    --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.