discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Discuss-gnuradio] fusb::_reap: Interrupted System Call


From: Jared Jensen
Subject: RE: [Discuss-gnuradio] fusb::_reap: Interrupted System Call
Date: Tue, 16 Oct 2007 13:37:28 -0400

That's an idea.  I do call usleep() occasionally in my other thread when I know I won't be processing for a while.  (Like when I want to let my buffer recover a little while after I run up to the end of it.)  Maybe the super high priority read thread is executing when a usleep() should return and I get this error.  I'll look into it.  Thanks for taking the time to look at it.  I'm not using any signaling between the two threads.  I just have that callback.  So hopefully it's just the usleep issue.  Thanks again.

Jared

> Date: Tue, 16 Oct 2007 10:07:17 -0700
> From: address@hidden
> To: address@hidden
> CC: address@hidden
> Subject: Re: [Discuss-gnuradio] fusb::_reap: Interrupted System Call
>
> On Tue, Oct 16, 2007 at 12:47:59PM -0400, Jared Jensen wrote:
> >
> > Eric,
> >
> > Ubuntu, Feisty. 2.6.20-16-generic. HP dv2000
> > laptop, Core 2 Duo, 1.6 GHz. 2 GB RAM, 160GB HDD 5400 RPM (But I'm not
> > doing much disk I/O at all).
> >
> > I get the error message
> > every 10-15 seconds or so. Sometimes I won't see it for minutes at a
> > time, and other times, I'll see it often; like multiple times in a few
> > seconds. Like I said, no data is missing (as far as I can tell), but
> > this pops up frequently; apparently from the libusb driver. I don't
> > get overruns, just this. Also, as I said, I can't see any missing
> > data, but I also can't 100% guarantee that I'm not losing some data, so
> > it concerns me a little.
>
> Without chasing through more code than I just did, I can't say with
> certainty if you're losing data or not, but I suspect that you're not.
>
> I would guess that you're using some kind of time keeping alarm that's
> setting a periodic interrupt, and that's what you're seeing (E.g.,
> sleep or alarm). Are you expecting to be getting a SIG* in this
> thread? If not, you may want to take a look at pthread_sigmask.
> Using threads and signals together is a bit of a black art.
>
> Eric


Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! Try now!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]