discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] LIBUSB_ERROR_PIPE and "improperly" stopping gnura


From: Eleftherios(Lef) Kampianakis
Subject: Re: [Discuss-gnuradio] LIBUSB_ERROR_PIPE and "improperly" stopping gnuradio
Date: Wed, 5 Nov 2014 14:40:37 -0800

Thanks again for your (rapid) response!

1) I think there should be somekind of bug report on that although I dont really know how to do this
2) I was thinking of a workaround through lsmod (similar to modprobe in linux) to emulate the removal and re-insertion of USB, this way I could write a simple script and avoid the physical procedure which prohibits remote control of the USRP host. Any ideas on that?

3) When I execute a flowgraph that contains a WXGUI element and close the python window instead of killing the flowgraph, I can issue a next execution without problems. What's happening then and how can I use this for my 
purposes?

Best regards,
Lefteris









On Wed, Nov 5, 2014 at 2:00 PM, Sylvain Munaut <address@hidden> wrote:
Hi,

> Ok, what about the python script in my previous message? How can I write my
> code in order to prevent the LIB_USB_ERROR_PIPE message. No matter how I
> stop the gnuradio script (e.g. catch keyboard interrupt and issue stop() and
> wait as in my original post), I always get the same message.

Yes, CTRL-C sends a SIGSTOP which can be caught and so proper clean-up
is possible. (although obviously not happenning).


> My intuition
> due to that is that something is not cleaned up properly in UHD level. Any
> suggestions on that?

Not really no.

It's either in UHD, in libusb, in the OS, or even possibly in the FX3
firmware which is a pretty large area to search for a bug.

Whatever a userspace sw does, it should not be able to lockup access
to a device. When the process exits, all should be cleaned up by the
OS. So I'd look in the lower levels first.

Not so long ago, on linux with bladerf, doing sig-kill actually
triggered a but that caused a kernel panic IIRC ... so you see
unplug/replug is not that bad :p  USB3 is still quite new and a lot of
stuff is still buggy.

Cheers,

   Sylvain



--
Eleftherios(Lefteris) Kampianakis
Electronics and Computer Engineer
PHD Candidate and Researcher at Sensing Computing Communications Group (SGCC)
Department of Electrical Engineering
University of Washington
3927 Adams Lane, NE, Mercer Court D805B, 98105

reply via email to

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