On Tue, 2007-07-31 at 18:31 +0200, Jan Kiszka wrote:
> Philippe Gerum wrote:
> > 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
Correction: it would return -EAGAIN, so maybe the status leaks when a
restart condition has been encountered in the stat loop. Seems minor,
compared to ENOMEM.
> > either, though, but it does happen on the other site.
> OK, will look into it again once I found what breaks
> xnintr_edge_shirq_handler() here (2.4 and 2.3). Damn it.
Did somebody tell you about a guy named Sisyphus, already? :o>
Xenomai-core mailing list