Re: [Discuss-gnuradio] diagnosing overflows

ha, that's a bit surprising, as Debian usually keeps their "linux-tools" package up to date, but for pretty new kernels, yes, might be necessary to build it yourself. Cheers, Marcus On 20.08.2017 00:08, Philip Hahn wrote: > Thank you Marcus and apologies for the late reply. As it turns out >

Re: [Discuss-gnuradio] diagnosing overflows

Thank you Marcus and apologies for the late reply. As it turns out perf is not included with Raspbian but can be compiled fairly easily: http://jireren.github.io/blog/2016/09/19/Compile-Perf/ -philip On Thu, Aug 10, 2017 at 9:15 AM, Marcus Müller wrote: > Hi philip, >

Re: [Discuss-gnuradio] diagnosing overflows

Hi philip, to identify such bottlenecks, it's often a nice clue to know which block consumes the most CPU. I don't know it the Linux perf counters work well on ARM (simply haven't tried), but if they do: There's a program called perf. Usage in short sudo sysctl kernel.perf_event_paranoid=-1 perf

Re: [Discuss-gnuradio] diagnosing overflows

Sean - OK, I understand what you mean now, thank you - the overflow is not reported until the pressure hits the source block. Cinaed - In this case it is not my flowgraph but gnss-sdr which I've run successfully on several platforms. In this case it is running on a Raspberry Pi 3. I anticipate

Re: [Discuss-gnuradio] diagnosing overflows

On 08/08/2017 07:56 PM, Philip Hahn wrote: > Folks, > > Is there a way to diagnose which block first reports an overflow in a > flowgraph? > > In my particular instance I am running a flowgraph which is overflowing > without pegging either RAM or CPU. It could also be an error in the

Re: [Discuss-gnuradio] diagnosing overflows

Hi Philip, Check out line 188: https://github.com/osmocom/gr-osmosdr/blob/master/lib/osmosdr/osmosdr_src_c.cc It would appear that other driver writers have followed the lead of Ettus and use the same letters to indicate the same error. I've only looked at this code for an entire five minutes,

Re: [Discuss-gnuradio] diagnosing overflows

Hi Sean, I am not using UHD blocks, I am using osmocom source/sinks. I did not see any warnings about changing buffer sizes. Thank you, philip On Tue, Aug 8, 2017 at 8:42 PM, Sean Horton wrote: > Unless I'm mistaken, only the usrp sink/source blocks report overflow

Re: [Discuss-gnuradio] diagnosing overflows

Unless I'm mistaken, only the usrp sink/source blocks report overflow (source) or underflow (sink). You can see this mentioned in uhd/docs/general.dox (uhd github repo). Did you listen to the warnings you get on startup about changing buffer sizes with a series of commands requiring sudo? That

[Discuss-gnuradio] diagnosing overflows

Folks, Is there a way to diagnose which block first reports an overflow in a flowgraph? In my particular instance I am running a flowgraph which is overflowing without pegging either RAM or CPU. Thank you, philip ___ Discuss-gnuradio mailing list