All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [BUG] 2.4-rc1: modular nucleus cannot be	unloaded
Date: Tue, 31 Jul 2007 18:26:57 +0200	[thread overview]
Message-ID: <1185899217.6611.246.camel@domain.hid> (raw)
In-Reply-To: <46AF5F1E.7030009@domain.hid>

On Tue, 2007-07-31 at 18:11 +0200, Jan Kiszka wrote:
> Already a plain command sequence causes this problem:
> 
> # modprobe xeno_nucleus
> # rmmod xeno_nucleus
> rmmod: xeno_nucleus: Resource temporarily unavailable
> 
> Can anyone confirm?

Cannot reproduce it here. However, I got another report saying that
/proc/xenomai/stat would return -ENOMEM. Cannot reproduce it here
either, though, but it does happen on the other site.

>  This is unfortunately only a secondary issue that I
> came across while hunting more severe problems of my colleagues, ie. I
> don't have the time to look into detail ATM.
> 
> Jan
> 
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
-- 
Philippe.




  reply	other threads:[~2007-07-31 16:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 16:11 [Xenomai-core] [BUG] 2.4-rc1: modular nucleus cannot be unloaded Jan Kiszka
2007-07-31 16:26 ` Philippe Gerum [this message]
2007-07-31 16:31   ` Jan Kiszka
2007-07-31 16:47     ` Philippe Gerum
2007-07-31 16:51       ` Philippe Gerum
2007-07-31 16:56         ` Jan Kiszka
2007-07-31 17:16           ` Philippe Gerum
2007-08-01  9:10             ` Jan Kiszka
2007-08-01  9:21               ` Philippe Gerum
2007-08-01  9:26                 ` Jan Kiszka
2007-08-01  9:48                   ` Philippe Gerum
2007-07-31 18:51   ` Jan Kiszka

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