Set the MTU to 1500 and that fixed it, thanks for the help!
From: Marcus D. Leech [mailto:[email protected]] Sent: Friday, September 7, 2018 11:38 AM To: Harper, Andrew <[email protected]>; [email protected] Subject: Re: [USRP-users] USRP Source Block caught rx error code: 15 On 09/07/2018 09:48 AM, Harper, Andrew wrote: Here is the output: enp3s0 Link encap:Ethernet HWaddr 68:f7:28:42:64:6b inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::c469:ffbe:558:1d0c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:5000 Metric:1 RX packets:129757 errors:0 dropped:0 overruns:0 frame:0 TX packets:146186 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:60283078 (60.2 MB) TX bytes:63747906 (63.7 MB) Did you set the MTU to 5000? For 1GiGe, the default is 1500, and what I've found with RealTek ethernet controllers is that they're perfectly happy to accept a higher MTU *setting* but cannot actually deliver on it. ________________________________ From: Marcus D. Leech <[email protected]><mailto:[email protected]> Sent: Thursday, September 6, 2018 4:31:28 PM To: Harper, Andrew; [email protected]<mailto:[email protected]> Subject: Re: [USRP-users] USRP Source Block caught rx error code: 15 On 09/06/2018 04:01 PM, Harper, Andrew wrote: I'm running Xubuntu 16.04 on the hardware, i.e. not VM: Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial Ethernet info: description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@0000:03:00.0<mailto:pci@0000:03:00.0> logical name: enp3s0 version: 10 serial: 68:f7:28:42:64:6b size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-3_0.0.1 04/23/13 ip=192.168.10.1 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:27 ioport:3000(size=256) memory:f0d04000-f0d04fff memory:f0d00000-f0d03fff What is the frame error count on the interface? (rx errors when using ifconfig) ________________________________ From: USRP-users <[email protected]><mailto:[email protected]> on behalf of Marcus D. Leech via USRP-users <[email protected]><mailto:[email protected]> Sent: Thursday, September 6, 2018 3:43 PM To: [email protected]<mailto:[email protected]> Subject: Re: [USRP-users] USRP Source Block caught rx error code: 15 On 09/06/2018 03:29 PM, Harper, Andrew via USRP-users wrote: Hi, I am having a troubling error from my x310 USRP whenever I try to pull samples using the USRP source block. The error message I am getting is: [ERROR] [STREAMER] The receive packet handler caught a value exception. ValueError: Bad CHDR or packet fragment WARN: USRP Source Block caught rx error code: 15 [ERROR] [RX FLOW CTRL] Error unpacking packet: ValueError: Bad CHDR or packet fragment The most basic flowgraph that creates this error is a USRP Source connected directly to a QT Time plot. It also happens when I try to run: 1) uhd_cal_rx_iq_balance, 2) uhd_fft, 3) uhd_cal_tx_dc_offset, My gnuradio version is 3.7.13.4, UHD version is UHD 3.14.0.0-88-g6013a511, and i have just reinstalled both to make sure it is not a software issue. I am able to successfully run uhd_find_devices and uhd_usrp_probe. I am also able to run a USRP sink block without error, if that helps identify the problem. Anyone have a fix for this? Andrew What type of Ethernet interface do you have on your system? Is this a VM, or a on-the-hardware system? Is this on Windows or Linux?
_______________________________________________ USRP-users mailing list [email protected] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
