All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Webb <jeff.webb@nta-inc.net>
To: Xenomai <xenomai@xenomai.org>
Subject: [Xenomai] rtnet issue with xenomai-3.git next branch
Date: Tue, 16 Dec 2014 17:29:51 -0600	[thread overview]
Message-ID: <5490C06F.4080901@nta-inc.net> (raw)

I am testing the rtnet functionality in the 'next' branch of xenomai-3.git.  (I now also have Xenomai-2.6.4/rtnet.git running on the same machine for comparison.)  I am able to bring up the real-time interface (rt_e1000e) and use rtping as expected. As mentioned before, I have a primary non-rt ethernet interface running simultaneously (using the e1000e driver).   When I try to remove all the rtnet modules, I am unable to remove rtnet and rtipv4:

$ rmmod rtipv4 rtnet
rmmod: ERROR: Module rtipv4 is in use
rmmod: ERROR: Module rtnet is in use by: rtipv4

The messages are the same if I try to remove them individually.  This behavior does not occur with Xenomai-2.6.4/rtnet.git.

I also have issues when I try to load the rtudp and/or rtpacket modules:

$ sudo modprobe rtnet
$  sudo modprobe rtipv4
$ sudo modprobe rtpacket
modprobe: ERROR: could not insert 'rtpacket': Invalid argument
$ sudo modprobe rtudp
modprobe: ERROR: could not insert 'rtudp': Invalid argument

I thought that this triggered an I-pipe trace in the past, but I can't reproduce that at the moment.  The 'Invalid argument' error code is coming from rtdm_dev_register, right?

A superficial test of the "latency" program seems to run fine on this hardware/software configuration.

Here are some more details:

Hardware: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
Linux: release 3.14.17

   $ cat /proc/cmdline
   BOOT_IMAGE=/boot/vmlinuz-3.14.17-xenomai-3.git.2014.11.27 root=UUID=3ec85b09-cb5d-42fe-bec7-106935ecf29d ro biosdevname=0

Xenomai: from git://git.xenomai.org/xenomai-3.git next

   $ version
   Xenomai/cobalt v3.0-rc2 -- #7a81ea8 (2014-11-27 22:02:32 +0100)

   $ xeno-config --info|grep -i build
   Build args: --prefix=/usr --includedir=/usr/include/xenomai --mandir=/usr/share/man --with-testdir=/usr/lib/xenomai/testsuite --build x86_64-linux-gnu build_alias=x86_64-linux-gnu

OS: Ubuntu 14.04

Any help resolving these issues would be appreciated.

Thanks,

-Jeff


             reply	other threads:[~2014-12-16 23:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 23:29 Jeff Webb [this message]
2014-12-17 10:29 ` [Xenomai] rtnet issue with xenomai-3.git next branch Gilles Chanteperdrix
2014-12-17 10:59   ` Gilles Chanteperdrix
2014-12-18 21:59     ` Jeff Webb
2014-12-19 10:39       ` Gilles Chanteperdrix
2014-12-30 22:38       ` Gilles Chanteperdrix
2015-09-29  5:44       ` Gilles Chanteperdrix
     [not found] <CAB6vvjn7=j2LpfwVhVAQBPcYiK6a-owoCaFXqY00+JnU2jGm9A@mail.gmail.com>
2015-02-24  9:34 ` Gilles Chanteperdrix
  -- strict thread matches above, loose matches on Subject: below --
2015-02-24 10:39 Antoine Hoarau
2015-02-24 12:00 ` Antoine Hoarau
2015-02-24 12:51   ` Gilles Chanteperdrix
2015-02-24 12:50 ` Gilles Chanteperdrix
2015-02-25 10:23 Antoine Hoarau
2015-02-25 10:26 ` Antoine Hoarau
2015-02-25 10:36 ` Gilles Chanteperdrix
2015-02-25 10:47   ` Antoine Hoarau
2015-02-25 12:34     ` Gilles Chanteperdrix
2015-02-25 13:23 Antoine Hoarau
2015-02-25 20:46 ` Gilles Chanteperdrix
2015-02-25 21:11   ` Antoine Hoarau
2015-02-25 21:21     ` Gilles Chanteperdrix

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=5490C06F.4080901@nta-inc.net \
    --to=jeff.webb@nta-inc.net \
    --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.