Re: [USRP-users] UHD 3.10.2 | X300 - High CPU load even for low samples rate

2017-10-20 Thread Kai-Uwe Storek via USRP-users 
Hey Marcus and Brent,

thanks for suggestions. I'm not working in a VM.

The benchmark tool underpins the behaviour:

If I use the UHD version of the debian distribution, everything seems normal:

--
/usr/lib/uhd/examples % ./benchmark_rate --args="address=192.168.10.2"
--rx_rate 20e6 --tx_rate 20e6
linux; GNU C++ version 6.3.0 20170221; Boost_106200; UHD_003.009.005-0-unknown


Creating the usrp device with: address=192.168.10.2...
-- X300 initialization sequence...
-- Determining maximum frame size... 1472 bytes.
-- Setup basic communication...
-- Loading values from EEPROM...
-- Setup RF frontend clocking...
-- Radio 1x clock:200
-- Initialize Radio0 control...
-- Performing register loopback test... pass
-- Initialize Radio1 control...
-- Performing register loopback test... pass
Using Device: Single USRP:
  Device: X-Series Device
  Mboard 0: X300
  RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv3 RX+GDB
  RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: WBXv3 RX+GDB
  TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv3 TX+GDB
  TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: WBXv3 TX+GDB

Setting device timestamp to 0...
Testing receive rate 20.00 Msps on 1 channels
Testing transmit rate 20.00 Msps on 1 channels
UUU
Benchmark rate summary:
  Num received samples:200137060
  Num dropped samples: 0
  Num overflows detected:  0
  Num transmitted samples: 200114096
  Num sequence errors: 0
  Num underflows detected: 3
  Num late commands:   0
  Num timeouts:0


Done!
--


If I use the the maint version:

--
~/gr_prefixes/stable/lib/uhd/examples % ./benchmark_rate
--args="address=192.168.10.2" --rx_rate 20e6 --tx_rate 20e6
linux; GNU C++ version 6.3.0 20170516; Boost_106200;
UHD_003.010.002.000-3-g122bfae1


Creating the usrp device with: address=192.168.10.2...
-- X300 initialization sequence...
-- Determining maximum frame size... 1472 bytes.
-- Setup basic communication...
-- Loading values from EEPROM...
-- Setup RF frontend clocking...
-- Radio 1x clock:200
-- Detecting internal GPSDO No GPSDO found
-- [DMA FIFO] Running BIST for FIFO 0... pass (Throughput: 1296.0MB/s)
-- [DMA FIFO] Running BIST for FIFO 1... pass (Throughput: 1299.4MB/s)
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- Performing timer loopback test... pass
-- Performing timer loopback test... pass
Using Device: Single USRP:
  Device: X-Series Device
  Mboard 0: X300
  RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv3 RX+GDB
  RX Channel: 1
RX DSP: 0
RX Dboard: B
RX Subdev: WBXv3 RX+GDB
  TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv3 TX+GDB
  TX Channel: 1
TX DSP: 0
TX Dboard: B
TX Subdev: WBXv3 TX+GDB

Setting device timestamp to 0...
Testing receive rate 20.00 Msps on 1 channels
Testing transmit rate 20.00 Msps on 1 channels
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
UDOReceiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...

UHD Error:
x300 fw communication failure #1
EnvironmentError: IOError: x300 fw poke32 - reply timed out
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...

UHD Error:
x300 fw communication failure #2
EnvironmentError: IOError: x300 fw poke32 - reply timed out
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continui

Re: [USRP-users] UHD 3.10.2 | X300 - High CPU load even for low samples rate

2017-10-20 Thread Marcus D. Leech via USRP-users 

On 10/20/2017 04:20 AM, Kai-Uwe Storek via USRP-users wrote:

Hey Marcus and Brent,

thanks for suggestions. I'm not working in a VM.

The benchmark tool underpins the behaviour:

If I use the UHD version of the debian distribution, everything seems normal:

Interesting.  This is definitely something to be followed up on.

I took a closer look at my own FG in this context, and indeed one of the 
CPUs is completely pegged.





--
/usr/lib/uhd/examples % ./benchmark_rate --args="address=192.168.10.2"
--rx_rate 20e6 --tx_rate 20e6
linux; GNU C++ version 6.3.0 20170221; Boost_106200; UHD_003.009.005-0-unknown


Creating the usrp device with: address=192.168.10.2...
-- X300 initialization sequence...
-- Determining maximum frame size... 1472 bytes.
-- Setup basic communication...
-- Loading values from EEPROM...
-- Setup RF frontend clocking...
-- Radio 1x clock:200
-- Initialize Radio0 control...
-- Performing register loopback test... pass
-- Initialize Radio1 control...
-- Performing register loopback test... pass
Using Device: Single USRP:
   Device: X-Series Device
   Mboard 0: X300
   RX Channel: 0
 RX DSP: 0
 RX Dboard: A
 RX Subdev: WBXv3 RX+GDB
   RX Channel: 1
 RX DSP: 1
 RX Dboard: B
 RX Subdev: WBXv3 RX+GDB
   TX Channel: 0
 TX DSP: 0
 TX Dboard: A
 TX Subdev: WBXv3 TX+GDB
   TX Channel: 1
 TX DSP: 1
 TX Dboard: B
 TX Subdev: WBXv3 TX+GDB

Setting device timestamp to 0...
Testing receive rate 20.00 Msps on 1 channels
Testing transmit rate 20.00 Msps on 1 channels
UUU
Benchmark rate summary:
   Num received samples:200137060
   Num dropped samples: 0
   Num overflows detected:  0
   Num transmitted samples: 200114096
   Num sequence errors: 0
   Num underflows detected: 3
   Num late commands:   0
   Num timeouts:0


Done!
--


If I use the the maint version:

--
~/gr_prefixes/stable/lib/uhd/examples % ./benchmark_rate
--args="address=192.168.10.2" --rx_rate 20e6 --tx_rate 20e6
linux; GNU C++ version 6.3.0 20170516; Boost_106200;
UHD_003.010.002.000-3-g122bfae1


Creating the usrp device with: address=192.168.10.2...
-- X300 initialization sequence...
-- Determining maximum frame size... 1472 bytes.
-- Setup basic communication...
-- Loading values from EEPROM...
-- Setup RF frontend clocking...
-- Radio 1x clock:200
-- Detecting internal GPSDO No GPSDO found
-- [DMA FIFO] Running BIST for FIFO 0... pass (Throughput: 1296.0MB/s)
-- [DMA FIFO] Running BIST for FIFO 1... pass (Throughput: 1299.4MB/s)
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- Performing timer loopback test... pass
-- Performing timer loopback test... pass
Using Device: Single USRP:
   Device: X-Series Device
   Mboard 0: X300
   RX Channel: 0
 RX DSP: 0
 RX Dboard: A
 RX Subdev: WBXv3 RX+GDB
   RX Channel: 1
 RX DSP: 0
 RX Dboard: B
 RX Subdev: WBXv3 RX+GDB
   TX Channel: 0
 TX DSP: 0
 TX Dboard: A
 TX Subdev: WBXv3 TX+GDB
   TX Channel: 1
 TX DSP: 0
 TX Dboard: B
 TX Subdev: WBXv3 TX+GDB

Setting device timestamp to 0...
Testing receive rate 20.00 Msps on 1 channels
Testing transmit rate 20.00 Msps on 1 channels
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
UDOReceiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...

UHD Error:
 x300 fw communication failure #1
 EnvironmentError: IOError: x300 fw poke32 - reply timed out
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...
Receiver error: ERROR_CODE_TIMEOUT, continuing...

UHD Error:
 x300 fw communication failure #2
 EnvironmentError: IOE

[USRP-users] second Gbps connection on single PC

2017-10-20 Thread Osvaldo Alcala (Ozzie) via USRP-users 
Hi,

I have an 10 Gbps card on my work station (recommended by Nate) which has 2 
lots. In 1 slot I have a X310 connected and its working fine with an ip address 
192.168.40.2

I want to use the second slot to connect the second X310, but just curios what 
ip address should I use? The gateway (pc 10 Gbps card) will be 192.168.40.1, so 
how do I deal with the second X310 as to not have any collisions?

Thank you

Oz
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] second Gbps connection on single PC

2017-10-20 Thread Brent Stapleton via USRP-users 
Hi Oz,

You can change the IP address of the second X310 to whatever you'd like by
following these instructions
. If
I understand your setup correctly, each of the interfaces in the system
(host or X310, 4 in total) should have its own IP address, and you'll
probably want each host-X310 pair to be on the same subnet.

Regards,
Brent

On Fri, Oct 20, 2017 at 11:35 AM, Osvaldo Alcala (Ozzie) via USRP-users <
usrp-users@lists.ettus.com> wrote:

> Hi,
>
>
>
> I have an 10 Gbps card on my work station (recommended by Nate) which has
> 2 lots. In 1 slot I have a X310 connected and its working fine with an ip
> address 192.168.40.2
>
>
>
> I want to use the second slot to connect the second X310, but just curios
> what ip address should I use? The gateway (pc 10 Gbps card) will be
> 192.168.40.1, so how do I deal with the second X310 as to not have any
> collisions?
>
>
>
> Thank you
>
>
>
> Oz
>
> ___
> USRP-users mailing list
> USRP-users@lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] UHD Freezing after Underruns/Late Samples and Freezing

2017-10-20 Thread Marcus D. Leech via USRP-users 

On 10/20/2017 07:25 PM, Richard Mcallister via USRP-users wrote:

Hi all,

I'm currently using 4 X310's with LFTXs to transmit. The flowgraph 
hasn't changed from last semester when I made it, but its attached. 
When I run it with more than one USRP, it will eventually crash and 
freeze. UHD will output a single U (underrun) and then continuously 
print L (late sample?). With 4 USRPs, this will happen almost immediately.


 I've tried running it on a different computer after system monitor 
showed that (roughly) for each USRP being used, one of the 16 cores 
would go to around 100% while the others stayed low. I also tried 
changing the Ethernet cable, with no success. No success. I've also 
tried using ethtool to add more TX/RX descriptors, and I've raised the 
sysctl rmem/wmem buffers as UHD indicates. Does anyone else have any 
good suggestions on what to try?


Thanks,

Rich McAllister


___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

What version of UHD?

You're using a 1GiGe interface to your X310s?


___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com