All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Yigal Goldberger <yigal_gold@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Fw: Re: signaling to a thread waiting on an event in the kernel
Date: Thu, 31 Dec 2009 11:45:59 +0100	[thread overview]
Message-ID: <1262256359.19080.524.camel@domain.hid> (raw)
In-Reply-To: <954372.96938.qm@domain.hid>

On Thu, 2009-12-31 at 02:24 -0800, Yigal Goldberger wrote:
> Hi,
> I found the issue - Nothing to do with the blocked thread (waiting on the signal ) .
> Just some bug in my application...It works just fine now.

Ok. Non-reg tests did not show any issue regarding this, here as well.
So issue closed. Thanks for your feedback.

> 
> Thanks,
> Yigal Goldbnerger.
> 
> --- On Mon, 12/28/09, Yigal Goldberger <yigal_gold@domain.hid> wrote:
> 
> > From: Yigal Goldberger <yigal_gold@domain.hid>
> > Subject: [Xenomai-help] Fw: Re: signaling to a thread waiting on an event in the kernel
> > To: xenomai@xenomai.org
> > Date: Monday, December 28, 2009, 7:57 PM
> > Hi,
> > CC'ing the mailing list .
> > 
> > --- On Mon, 12/28/09, Yigal Goldberger <yigal_gold@domain.hid>
> > wrote:
> > 
> > > From: Yigal Goldberger <yigal_gold@domain.hid>
> > > Subject: Re: [Xenomai-help] signaling to a thread
> > waiting on an event in the kernel
> > > To: "Philippe Gerum" <rpm@xenomai.org>
> > > Date: Monday, December 28, 2009, 6:01 PM
> > > Hi Philippe,
> > > Thanks for quickly responding .
> > > My system is a powerpc based board ( MPC8272 by
> > freesacle
> > > ).
> > > The kernel is 2.6.29.4 .
> > > Xenomai v2.4.8.
> > > 
> > > My app hangs on the RTDM syscall invoking
> > > rtdm_event_timedwait() from your
> > > driver .(It does not return from this function call
> > at
> > > all)
> > > The system does not lock up badly . My so called
> > Monitor
> > > process (the process that issues the
> > kill(Pid,SIGTERM),
> > > functions well and communicates fine.
> > > I'd like to mention that when the application process
> > is
> > > not blocked (in normal operation) it does respond to
> > the
> > > signal and terminates correctly , but when it is
> > "stuck"|
> > > such as on the infinite event wait it becomes non
> > responsive
> > > to external signals.
> > > 
> > > Thanks,
> > > Yigal.
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > --- On Mon, 12/28/09, Philippe Gerum <rpm@xenomai.org>
> > > wrote:
> > > 
> > > > From: Philippe Gerum <rpm@xenomai.org>
> > > > Subject: Re: [Xenomai-help] signaling to a
> > thread
> > > waiting on an event in the kernel
> > > > To: "Yigal Goldberger" <yigal_gold@domain.hid>
> > > > Cc: xenomai@xenomai.org
> > > > Date: Monday, December 28, 2009, 4:52 PM
> > > > On Mon, 2009-12-28 at 01:59 -0800,
> > > > Yigal Goldberger wrote:
> > > > > Hi,
> > > > > 
> > > > > I want to have the ability to restart a
> > process
> > > at all
> > > > times.
> > > > > I have a situation where a thread is waiting
> > on
> > > an
> > > > event in the kernel with : 
> > > > > rtdm_event_timedwait(&args,0,NULL)
> > > > 
> > > > >   - infinite wait (I need this infinite
> > > > wait ...) 
> > > > > 
> > > > > and I cannot restart it with  :
> > > > > 
> > > > > kill(Pid,SIGTERM) .
> > > > > 
> > > > > from a different process .
> > > > > 
> > > > > Suggestions are most welcome.
> > > > > 
> > > > 
> > > > Please be more specific:
> > > > 
> > > > - what happens when SIGTERM is sent, exactly?
> > does
> > > your app
> > > > hang on the
> > > > RTDM syscall invoking rtdm_event_timedwait()
> > from
> > > your
> > > > driver, or does
> > > > the entire system lock up badly?
> > > > - did you check whether rtdm_event_timedwait()
> > > returned
> > > > with an error
> > > > code, such as -EINTR?
> > > > - which platform, whick kernel release, which
> > Xenomai
> > > > release are you
> > > > running?
> > > > 
> > > > Btw, rtdm_event_wait(&event) is a shorthand
> > for
> > > > rtdm_event_timedwait(&event,0,NULL).
> > > > 
> > > > > Yigal Goldberger.
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > >       
> > > > > 
> > > > >
> > _______________________________________________
> > > > > Xenomai-help mailing list
> > > > > Xenomai-help@domain.hid
> > > > > https://mail.gna.org/listinfo/xenomai-help
> > > > 
> > > > 
> > > > -- 
> > > > Philippe.
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > > 
> > >
> > 
> > 
> > 
> >       
> > 
> > _______________________________________________
> > Xenomai-help mailing list
> > Xenomai-help@domain.hid
> > https://mail.gna.org/listinfo/xenomai-help
> > 
> 
> 
>       
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help


-- 
Philippe.




      reply	other threads:[~2009-12-31 10:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28 17:57 [Xenomai-help] Fw: Re: signaling to a thread waiting on an event in the kernel Yigal Goldberger
2009-12-31 10:24 ` Yigal Goldberger
2009-12-31 10:45   ` 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=1262256359.19080.524.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=xenomai@xenomai.org \
    --cc=yigal_gold@domain.hid \
    /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.