My guess is that the error causes the FPGA to reset which causes a temporary interruption in the pHY and MAC and by the time you ping, it has reset and brought the PHY and MAC up.
Does this happen when you’re just streaming samples via rx_samples_to_file to /dev/null or tx_waveforms using the same sample rates? Sent from my iPhone > On May 26, 2021, at 9:30 AM, Jeff S <e070...@hotmail.com> wrote: > > It happened again. Here's the last few lines of my console output: > > [WARNING] [0/Radio#1] Attempting to set tick rate to 0. Skipping. > [WARNING] [0/Radio#0] Attempting to set tick rate to 0. Skipping. > [WARNING] [0/Radio#0] Attempting to set tick rate to 0. Skipping. > [WARNING] [0/Radio#1] Attempting to set tick rate to 0. Skipping. > > LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL[ERROR] > [UHD] An unexpected exception was caught in a task loop.The task loop will > now exit, things may not work.send: Network is unreachable > > When I noticed it, I did not cycle power, but I pinged: > > $ ping 192.168.40.2 > PING 192.168.40.2 (192.168.40.2) 56(84) bytes of data. > 64 bytes from 192.168.40.2: icmp_seq=1 ttl=32 time=0.674 ms > 64 bytes from 192.168.40.2: icmp_seq=2 ttl=32 time=0.689 ms > 64 bytes from 192.168.40.2: icmp_seq=3 ttl=32 time=0.679 ms > 64 bytes from 192.168.40.2: icmp_seq=4 ttl=32 time=0.682 ms > > and checked ifconfig: > > enp59s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 > inet 192.168.40.1 netmask 255.255.255.0 broadcast 192.168.40.255 > inet6 fe80::1329:ac3c:9d62:7672 prefixlen 64 scopeid 0x20<link> > ether 24:5e:be:52:5d:17 txqueuelen 1000 (Ethernet) > RX packets 57 bytes 4346 (4.3 KB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 375 bytes 1686170 (1.6 MB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > and went ahead and did a probe: > > $ uhd_usrp_probe > [INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; > UHD_4.0.0.0-104-g8f273305 > [INFO] [X300] X300 initialization sequence... > [INFO] [X300] Maximum frame size: 8000 bytes. > [INFO] [X300] Radio 1x clock: 200 MHz > [WARNING] [RFNOC::GRAPH] One or more blocks timed out during flush! > _____________________________________________________ > / > | Device: X-Series Device > | _____________________________________________________ > | / > | | Mboard: X310 > | | revision: 11 > | | revision_compat: 7 > | | product: 30818 > | | mac-addr0: 00:80:2f:26:5b:44 > | | mac-addr1: 00:80:2f:26:5b:45 > | | gateway: 192.168.10.1 > | | ip-addr0: 192.168.10.2 > | | subnet0: 255.255.255.0 > | | ip-addr1: 192.168.20.2 > | | subnet1: 255.255.255.0 > | | ip-addr2: 192.168.30.2 > | | subnet2: 255.255.255.0 > | | ip-addr3: 192.168.40.2 > | | subnet3: 255.255.255.0 > | | serial: 319ACEE > | | FW Version: 6.0 > | | FPGA Version: 38.0 > | | FPGA git hash: be53058 > | | > | | Time sources: internal, external, gpsdo > | | Clock sources: internal, external, gpsdo > | | Sensors: ref_locked > | _____________________________________________________ > | / > | | RFNoC blocks on this device: > | | > | | * 0/DDC#0 > | | * 0/DDC#1 > | | * 0/DUC#0 > | | * 0/DUC#1 > | | * 0/Radio#0 > | | * 0/Radio#1 > | | * 0/Replay#0 > | _____________________________________________________ > | / > | | Static connections on this device: > | | > | | * 0/SEP#0:0==>0/DUC#0:0 > | | * 0/DUC#0:0==>0/Radio#0:0 > | | * 0/Radio#0:0==>0/DDC#0:0 > | | * 0/DDC#0:0==>0/SEP#0:0 > | | * 0/Radio#0:1==>0/DDC#0:1 > | | * 0/DDC#0:1==>0/SEP#1:0 > | | * 0/SEP#2:0==>0/DUC#1:0 > | | * 0/DUC#1:0==>0/Radio#1:0 > | | * 0/Radio#1:0==>0/DDC#1:0 > | | * 0/DDC#1:0==>0/SEP#2:0 > | | * 0/Radio#1:1==>0/DDC#1:1 > | | * 0/DDC#1:1==>0/SEP#3:0 > | | * 0/SEP#4:0==>0/Replay#0:0 > | | * 0/Replay#0:0==>0/SEP#4:0 > | | * 0/SEP#5:0==>0/Replay#0:1 > | | * 0/Replay#0:1==>0/SEP#5:0 > | _____________________________________________________ > | / > | | TX Dboard: dboard > | | ID: UBX-160 v2 (0x007d) > | | Serial: 3183233 > | | _____________________________________________________ > | | / > | | | TX Frontend: 0 > | | | Name: UBX TX > | | | Antennas: TX/RX, CAL > | | | Sensors: lo_locked > | | | Freq range: 10.000 to 6000.000 MHz > | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB > | | | Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz > | | | Connection Type: QI > | | | Uses LO offset: No > | _____________________________________________________ > | / > | | RX Dboard: dboard > | | ID: UBX-160 v2 (0x007e) > | | Serial: 3183233 > | | _____________________________________________________ > | | / > | | | RX Frontend: 0 > | | | Name: UBX RX > | | | Antennas: TX/RX, RX2, CAL > | | | Sensors: lo_locked > | | | Freq range: 10.000 to 6000.000 MHz > | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB > | | | Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz > | | | Connection Type: IQ > | | | Uses LO offset: No > | _____________________________________________________ > | / > | | TX Dboard: dboard > | | ID: UBX-160 v2 (0x007d) > | | Serial: 31831F4 > | | _____________________________________________________ > | | / > | | | TX Frontend: 0 > | | | Name: UBX TX > | | | Antennas: TX/RX, CAL > | | | Sensors: lo_locked > | | | Freq range: 10.000 to 6000.000 MHz > | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB > | | | Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz > | | | Connection Type: QI > | | | Uses LO offset: No > | _____________________________________________________ > | / > | | RX Dboard: dboard > | | ID: UBX-160 v2 (0x007e) > | | Serial: 31831F4 > | | _____________________________________________________ > | | / > | | | RX Frontend: 0 > | | | Name: UBX RX > | | | Antennas: TX/RX, RX2, CAL > | | | Sensors: lo_locked > | | | Freq range: 10.000 to 6000.000 MHz > | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB > | | | Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz > | | | Connection Type: IQ > | | | Uses LO offset: No > > > ________________________________________ > From: Jeff S <e070...@hotmail.com> > Sent: Friday, May 21, 2021 8:40 AM > To: Marcus D Leech > Cc: USRP-users@lists.ettus.com > Subject: [USRP-users] Re: UHD Exception > > Marcus, > > When it happened, both the green RX LEDs went dark (I was looking at noise on > two channels, using TX/RX antenna inputs). I didn't try to ping, but just > stopped my flow graph, cycled power on the X310, restarted my flow graph, and > then everything was working again. If It happens again, I'll ping and check > the ifconfig, and report what I see. > > Thanks! > Jeff > ________________________________________ > From: Marcus D Leech <patchvonbr...@gmail.com> > Sent: Friday, May 21, 2021 7:59 AM > To: Jeff S > Cc: USRP-users@lists.ettus.com > Subject: Re: [USRP-users] UHD Exception > > Once this happens, is the X310 ping able? > > What does ifconfig say about the interface? > > Sent from my iPhone > >> On May 21, 2021, at 8:51 AM, Jeff S <e070...@hotmail.com> wrote: >> >> I've been running an X310 for quite a while, and recently got the following >> message: >> >> "[ERROR] [UHD] An unexpected exception was caught in a task loop.The task >> loop will now exit, things may not work.send: Network is unreachable" >> >> My current configuration is: >> >> Ubuntu 18.04 >> UHD UHD-4.0 (8f27330, 3/16/21) >> GNU Radio v3.8.2.0-112-ge20ffa3c >> QNAP Thunderbolt 3 to 10GbE Adapter >> >> I got the message once yesterday and once today. I have been using this >> configuration for weeks. How would I troubleshoot this exception? >> >> Regards, >> Jeff >> _______________________________________________ >> USRP-users mailing list -- usrp-users@lists.ettus.com >> To unsubscribe send an email to usrp-users-le...@lists.ettus.com > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-le...@lists.ettus.com _______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
