usrp-users@lists.ettus.com
Discussion and technical support related to USRP, UHD, RFNoC
View all threadsx310 IP build failure
Wondering if anyone has seen this issue or knows what I may have wrong here. Trying to get familiar with RFNOC and the build process so I have pulled down the latest git, switched to rfnoc-devel, init'd and updated the submodule. I have installed vivado 2015.4 and have a full license and am running under Ubuntu 16 LTS. I sourced the setupenv.sh and then ran make X310_RFNOC_HG. By the way I also did the disable dash reconfig thing just in case.
It starts the IP generation for the 10 gig and then without any error it fails. Below is a snippet of the last bits before it dies. I also attached the error log and the ip build log.
Just as a data point I just did the same exact setup under Ubuntu 12 LTS and it did not fail so it seems that there is some issue with 16 LTS??
Thanks
Jeff
......
Finished RTL Optimization Phase 2 : Time (s): cpu = 00:00:25 ; elapsed = 00:00:25 . Memory (MB): peak = 1581.988 ; gain = 734.895 ; free physical = 29303 ; free virtual = 63061
Report RTL Partitions:
+-+--------------+------------+----------+
| |RTL Partition |Replication |Instances |
+-+--------------+------------+----------+
+-+--------------+------------+----------+
Start RTL Component Statistics
Finished RTL Component Statistics
Start RTL Hierarchical Component Statistics
Finished RTL Hierarchical Component Statistics
Start Part Resource Summary
Parent process (pid 8304) has died. This helper process will now exit
BUILDER: Releasing IP location: /home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma
/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/ip/ten_gig_eth_pcs_pma/Makefile.inc:41: recipe for target '/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out' failed
make[1]: *** [/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out] Error 139
Makefile:65: recipe for target 'X300_HG' failed
make: *** [X300_HG] Interrupt
On 09/26/2016 03:13 PM, Long, Jeffrey P. via USRP-users wrote:
Wondering if anyone has seen this issue or knows what I may have wrong
here. Trying to get familiar with RFNOC and the build process so I
have pulled down the latest git, switched to rfnoc-devel, init’d and
updated the submodule. I have installed vivado 2015.4 and have a full
license and am running under Ubuntu 16 LTS. I sourced the setupenv.sh
and then ran make X310_RFNOC_HG. By the way I also did the disable
dash reconfig thing just in case.
It starts the IP generation for the 10 gig and then without any error
it fails. Below is a snippet of the last bits before it dies. I also
attached the error log and the ip build log.
Just as a data point I just did the same exact setup under Ubuntu 12
LTS and it did not fail so it seems that there is some issue with 16 LTS??
Thanks
Jeff
……
Finished RTL Optimization Phase 2 : Time (s): cpu = 00:00:25 ; elapsed
= 00:00:25 . Memory (MB): peak = 1581.988 ; gain = 734.895 ; free
physical = 29303 ; free virtual = 63061
Report RTL Partitions:
+-+--------------+------------+----------+
| |RTL Partition |Replication |Instances |
+-+--------------+------------+----------+
+-+--------------+------------+----------+
Start RTL Component Statistics
Finished RTL Component Statistics
Start RTL Hierarchical Component Statistics
Finished RTL Hierarchical Component Statistics
Start Part Resource Summary
Parent process (pid 8304) has died. This helper process will now exit
BUILDER: Releasing IP location:
/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma
/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/ip/ten_gig_eth_pcs_pma/Makefile.inc:41:
recipe for target
'/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out'
failed
make[1]: ***
[/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out]
Error 139
Makefile:65: recipe for target 'X300_HG' failed
make: *** [X300_HG] Interrupt
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
This looks like a bug in libpthread, possibly tripped-over by the Vivado
library that is next in the stack.
You should probably talk to Xinlinx support about this.
Yeah that is usually a waste of time. A quick search right now on libpthread and 2015.4 yielded similar issues. The canned Xilinx response is update to 2016.X, this fixes the issue. Unfortunately we can't do that here. They also won't even entertain my posts since I am using the very non-standard and unsupported Ubuntu 16 LTS. I have had this problem before. If you happen to be so unlucky that your version of vivado crashes then the only thing to do is roll back or forward in UHD till you find something that works. Switching around Oss is also an option albeit a pain.
I am going to try the 2015.4 update 2 patch. Do you happen to know if that will be OK from the setupenv.sh perspective?
Thanks
Jeff
From: USRP-users [mailto:usrp-users-bounces@lists.ettus.com] On Behalf Of Marcus D. Leech via USRP-users
Sent: Monday, September 26, 2016 3:21 PM
To: usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: Re: [USRP-users] x310 IP build failure
On 09/26/2016 03:13 PM, Long, Jeffrey P. via USRP-users wrote:
Wondering if anyone has seen this issue or knows what I may have wrong here. Trying to get familiar with RFNOC and the build process so I have pulled down the latest git, switched to rfnoc-devel, init'd and updated the submodule. I have installed vivado 2015.4 and have a full license and am running under Ubuntu 16 LTS. I sourced the setupenv.sh and then ran make X310_RFNOC_HG. By the way I also did the disable dash reconfig thing just in case.
It starts the IP generation for the 10 gig and then without any error it fails. Below is a snippet of the last bits before it dies. I also attached the error log and the ip build log.
Just as a data point I just did the same exact setup under Ubuntu 12 LTS and it did not fail so it seems that there is some issue with 16 LTS??
Thanks
Jeff
......
Finished RTL Optimization Phase 2 : Time (s): cpu = 00:00:25 ; elapsed = 00:00:25 . Memory (MB): peak = 1581.988 ; gain = 734.895 ; free physical = 29303 ; free virtual = 63061
Report RTL Partitions:
+-+--------------+------------+----------+
| |RTL Partition |Replication |Instances |
+-+--------------+------------+----------+
+-+--------------+------------+----------+
Start RTL Component Statistics
Finished RTL Component Statistics
Start RTL Hierarchical Component Statistics
Finished RTL Hierarchical Component Statistics
Start Part Resource Summary
Parent process (pid 8304) has died. This helper process will now exit
BUILDER: Releasing IP location: /home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma
/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/ip/ten_gig_eth_pcs_pma/Makefile.inc:41: recipe for target '/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out' failed
make[1]: *** [/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out] Error 139
Makefile:65: recipe for target 'X300_HG' failed
make: *** [X300_HG] Interrupt
USRP-users mailing list
USRP-users@lists.ettus.commailto:USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
This looks like a bug in libpthread, possibly tripped-over by the Vivado library that is next in the stack.
You should probably talk to Xinlinx support about this.
Hi Jeff,
I ran into this same problem on my Ubuntu 16.04 LTS when starting to work
with Xilinx. It seems to be related to more recent Intel processors. I also
tried an installation of Vivado 2016.X and built a demo application for the
Zynq as a sanity check, but the same issue showed up again (I'd be
interested to hear if that solves the problem for you). Here's some hits I
found online about the problem:
https://www.reddit.com/r/FPGA/comments/4olc29/is_anyone_running_vivado_2016x_on_a_recent_ubuntu/
https://forums.xilinx.com/t5/Synthesis/Vivado-crash-on-Ubuntu-16-04/td-p/699642/page/2
I HAVE had success running Xilinx in a Docker container. I currently do all
my FPGA builds from this container. I've attached a tar of the Dockerfile
and a readme, in case it can help you too. This should work with vivado
from the command line or from GUI. I have only tested using the Xilinx
license available for the e310, which is not nodelocked... If you need to
build for the X300 series, you may need to handle licensing a bit
differently. But at the very least, you should be able to test and confirm
if the Vivado build works OK on your machine.
Regards,
EJ
On Mon, Sep 26, 2016 at 4:05 PM, Long, Jeffrey P. via USRP-users <
usrp-users@lists.ettus.com> wrote:
Yeah that is usually a waste of time. A quick search right now on
libpthread and 2015.4 yielded similar issues. The canned Xilinx response is
update to 2016.X, this fixes the issue. Unfortunately we can’t do that
here. They also won’t even entertain my posts since I am using the very
non-standard and unsupported Ubuntu 16 LTS. I have had this problem before.
If you happen to be so unlucky that your version of vivado crashes then the
only thing to do is roll back or forward in UHD till you find something
that works. Switching around Oss is also an option albeit a pain.
I am going to try the 2015.4 update 2 patch. Do you happen to know if that
will be OK from the setupenv.sh perspective?
Thanks
Jeff
From: USRP-users [mailto:usrp-users-bounces@lists.ettus.com
usrp-users-bounces@lists.ettus.com] *On Behalf Of *Marcus D. Leech via
USRP-users
Sent: Monday, September 26, 2016 3:21 PM
To: usrp-users@lists.ettus.com
Subject: Re: [USRP-users] x310 IP build failure
On 09/26/2016 03:13 PM, Long, Jeffrey P. via USRP-users wrote:
Wondering if anyone has seen this issue or knows what I may have wrong
here. Trying to get familiar with RFNOC and the build process so I have
pulled down the latest git, switched to rfnoc-devel, init’d and updated the
submodule. I have installed vivado 2015.4 and have a full license and am
running under Ubuntu 16 LTS. I sourced the setupenv.sh and then ran make
X310_RFNOC_HG. By the way I also did the disable dash reconfig thing just
in case.
It starts the IP generation for the 10 gig and then without any error it
fails. Below is a snippet of the last bits before it dies. I also attached
the error log and the ip build log.
Just as a data point I just did the same exact setup under Ubuntu 12 LTS
and it did not fail so it seems that there is some issue with 16 LTS??
Thanks
Jeff
……
Finished RTL Optimization Phase 2 : Time (s): cpu = 00:00:25 ; elapsed =
00:00:25 . Memory (MB): peak = 1581.988 ; gain = 734.895 ; free physical =
29303 ; free virtual = 63061
Report RTL Partitions:
+-+--------------+------------+----------+
| |RTL Partition |Replication |Instances |
+-+--------------+------------+----------+
+-+--------------+------------+----------+
Start RTL Component Statistics
Finished RTL Component Statistics
Start RTL Hierarchical Component Statistics
Finished RTL Hierarchical Component Statistics
Start Part Resource Summary
Parent process (pid 8304) has died. This helper process will now exit
BUILDER: Releasing IP location: /home/jplong/proj/uhd/fpga-
src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma
/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/ip/
ten_gig_eth_pcs_pma/Makefile.inc:41: recipe for target
'/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/
build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out'
failed
make[1]: *** [/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/
build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out]
Error 139
Makefile:65: recipe for target 'X300_HG' failed
make: *** [X300_HG] Interrupt
USRP-users mailing list
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
This looks like a bug in libpthread, possibly tripped-over by the Vivado
library that is next in the stack.
You should probably talk to Xinlinx support about this.
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
EJ-
Thanks good to hear I am not nuts but this is a bummer. Yes a VM should work and I have done this before and will do it again if I have to. Have you tried the glibc configured with –disable-lock-elision thing mentioned in those links?
By the way I rolled back to a UHD that builds with 2014.4 and that failed too.
Thanks
Jeff
From: EJ Kreinar [mailto:ejkreinar@gmail.com]
Sent: Monday, September 26, 2016 4:33 PM
To: Long, Jeffrey P.
Cc: Marcus D. Leech; USRP-users@lists.ettus.com
Subject: Re: [USRP-users] x310 IP build failure
Hi Jeff,
I ran into this same problem on my Ubuntu 16.04 LTS when starting to work with Xilinx. It seems to be related to more recent Intel processors. I also tried an installation of Vivado 2016.X and built a demo application for the Zynq as a sanity check, but the same issue showed up again (I'd be interested to hear if that solves the problem for you). Here's some hits I found online about the problem:
https://www.reddit.com/r/FPGA/comments/4olc29/is_anyone_running_vivado_2016x_on_a_recent_ubuntu/
https://forums.xilinx.com/t5/Synthesis/Vivado-crash-on-Ubuntu-16-04/td-p/699642/page/2
I HAVE had success running Xilinx in a Docker container. I currently do all my FPGA builds from this container. I've attached a tar of the Dockerfile and a readme, in case it can help you too. This should work with vivado from the command line or from GUI. I have only tested using the Xilinx license available for the e310, which is not nodelocked... If you need to build for the X300 series, you may need to handle licensing a bit differently. But at the very least, you should be able to test and confirm if the Vivado build works OK on your machine.
Regards,
EJ
On Mon, Sep 26, 2016 at 4:05 PM, Long, Jeffrey P. via USRP-users <usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com> wrote:
Yeah that is usually a waste of time. A quick search right now on libpthread and 2015.4 yielded similar issues. The canned Xilinx response is update to 2016.X, this fixes the issue. Unfortunately we can’t do that here. They also won’t even entertain my posts since I am using the very non-standard and unsupported Ubuntu 16 LTS. I have had this problem before. If you happen to be so unlucky that your version of vivado crashes then the only thing to do is roll back or forward in UHD till you find something that works. Switching around Oss is also an option albeit a pain.
I am going to try the 2015.4 update 2 patch. Do you happen to know if that will be OK from the setupenv.sh perspective?
Thanks
Jeff
From: USRP-users [mailto:usrp-users-bounces@lists.ettus.com] On Behalf Of Marcus D. Leech via USRP-users
Sent: Monday, September 26, 2016 3:21 PM
To: usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: Re: [USRP-users] x310 IP build failure
On 09/26/2016 03:13 PM, Long, Jeffrey P. via USRP-users wrote:
Wondering if anyone has seen this issue or knows what I may have wrong here. Trying to get familiar with RFNOC and the build process so I have pulled down the latest git, switched to rfnoc-devel, init’d and updated the submodule. I have installed vivado 2015.4 and have a full license and am running under Ubuntu 16 LTS. I sourced the setupenv.sh and then ran make X310_RFNOC_HG. By the way I also did the disable dash reconfig thing just in case.
It starts the IP generation for the 10 gig and then without any error it fails. Below is a snippet of the last bits before it dies. I also attached the error log and the ip build log.
Just as a data point I just did the same exact setup under Ubuntu 12 LTS and it did not fail so it seems that there is some issue with 16 LTS??
Thanks
Jeff
……
Finished RTL Optimization Phase 2 : Time (s): cpu = 00:00:25 ; elapsed = 00:00:25 . Memory (MB): peak = 1581.988 ; gain = 734.895 ; free physical = 29303 ; free virtual = 63061
Report RTL Partitions:
+-+--------------+------------+----------+
| |RTL Partition |Replication |Instances |
+-+--------------+------------+----------+
+-+--------------+------------+----------+
Start RTL Component Statistics
Finished RTL Component Statistics
Start RTL Hierarchical Component Statistics
Finished RTL Hierarchical Component Statistics
Start Part Resource Summary
Parent process (pid 8304) has died. This helper process will now exit
BUILDER: Releasing IP location: /home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma
/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/ip/ten_gig_eth_pcs_pma/Makefile.inc:41: recipe for target '/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out' failed
make[1]: *** [/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out] Error 139
Makefile:65: recipe for target 'X300_HG' failed
make: *** [X300_HG] Interrupt
USRP-users mailing list
USRP-users@lists.ettus.commailto:USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
This looks like a bug in libpthread, possibly tripped-over by the Vivado library that is next in the stack.
You should probably talk to Xinlinx support about this.
USRP-users mailing list
USRP-users@lists.ettus.commailto:USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
I did not try a glibc rebuild.
Just a thought: I admit there's a bit of a docker learning curve but I
would highly encourage docker over a VM :) I found it to be extremely
responsive (zero bootup time, etc) and it supports running the Vivado GUI
without any problems. Plus, you can link the container into your local
rfnoc prefix so all the build outputs are in-place in your directory. Very
convenient
EJ
On Sep 26, 2016 4:46 PM, "Long, Jeffrey P." jplong@mitre.org wrote:
EJ-
Thanks good to hear I am not nuts but this is a bummer. Yes a VM should
work and I have done this before and will do it again if I have to. Have
you tried the glibc configured with –disable-lock-elision thing mentioned
in those links?
By the way I rolled back to a UHD that builds with 2014.4 and that failed
too.
Thanks
Jeff
From: EJ Kreinar [mailto:ejkreinar@gmail.com]
Sent: Monday, September 26, 2016 4:33 PM
To: Long, Jeffrey P.
Cc: Marcus D. Leech; USRP-users@lists.ettus.com
Subject: Re: [USRP-users] x310 IP build failure
Hi Jeff,
I ran into this same problem on my Ubuntu 16.04 LTS when starting to work
with Xilinx. It seems to be related to more recent Intel processors. I also
tried an installation of Vivado 2016.X and built a demo application for the
Zynq as a sanity check, but the same issue showed up again (I'd be
interested to hear if that solves the problem for you). Here's some hits I
found online about the problem:
https://www.reddit.com/r/FPGA/comments/4olc29/is_anyone_
running_vivado_2016x_on_a_recent_ubuntu/
https://forums.xilinx.com/t5/Synthesis/Vivado-crash-on-
Ubuntu-16-04/td-p/699642/page/2
I HAVE had success running Xilinx in a Docker container. I currently do
all my FPGA builds from this container. I've attached a tar of the
Dockerfile and a readme, in case it can help you too. This should work with
vivado from the command line or from GUI. I have only tested using the
Xilinx license available for the e310, which is not nodelocked... If you
need to build for the X300 series, you may need to handle licensing a bit
differently. But at the very least, you should be able to test and confirm
if the Vivado build works OK on your machine.
Regards,
EJ
On Mon, Sep 26, 2016 at 4:05 PM, Long, Jeffrey P. via USRP-users <
usrp-users@lists.ettus.com> wrote:
Yeah that is usually a waste of time. A quick search right now on
libpthread and 2015.4 yielded similar issues. The canned Xilinx response is
update to 2016.X, this fixes the issue. Unfortunately we can’t do that
here. They also won’t even entertain my posts since I am using the very
non-standard and unsupported Ubuntu 16 LTS. I have had this problem before.
If you happen to be so unlucky that your version of vivado crashes then the
only thing to do is roll back or forward in UHD till you find something
that works. Switching around Oss is also an option albeit a pain.
I am going to try the 2015.4 update 2 patch. Do you happen to know if that
will be OK from the setupenv.sh perspective?
Thanks
Jeff
From: USRP-users [mailto:usrp-users-bounces@lists.ettus.com
usrp-users-bounces@lists.ettus.com] *On Behalf Of *Marcus D. Leech via
USRP-users
Sent: Monday, September 26, 2016 3:21 PM
To: usrp-users@lists.ettus.com
Subject: Re: [USRP-users] x310 IP build failure
On 09/26/2016 03:13 PM, Long, Jeffrey P. via USRP-users wrote:
Wondering if anyone has seen this issue or knows what I may have wrong
here. Trying to get familiar with RFNOC and the build process so I have
pulled down the latest git, switched to rfnoc-devel, init’d and updated the
submodule. I have installed vivado 2015.4 and have a full license and am
running under Ubuntu 16 LTS. I sourced the setupenv.sh and then ran make
X310_RFNOC_HG. By the way I also did the disable dash reconfig thing just
in case.
It starts the IP generation for the 10 gig and then without any error it
fails. Below is a snippet of the last bits before it dies. I also attached
the error log and the ip build log.
Just as a data point I just did the same exact setup under Ubuntu 12 LTS
and it did not fail so it seems that there is some issue with 16 LTS??
Thanks
Jeff
……
Finished RTL Optimization Phase 2 : Time (s): cpu = 00:00:25 ; elapsed =
00:00:25 . Memory (MB): peak = 1581.988 ; gain = 734.895 ; free physical =
29303 ; free virtual = 63061
Report RTL Partitions:
+-+--------------+------------+----------+
| |RTL Partition |Replication |Instances |
+-+--------------+------------+----------+
+-+--------------+------------+----------+
Start RTL Component Statistics
Finished RTL Component Statistics
Start RTL Hierarchical Component Statistics
Finished RTL Hierarchical Component Statistics
Start Part Resource Summary
Parent process (pid 8304) has died. This helper process will now exit
BUILDER: Releasing IP location: /home/jplong/proj/uhd/fpga-
src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma
/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/ip/
ten_gig_eth_pcs_pma/Makefile.inc:41: recipe for target
'/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/
build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out'
failed
make[1]: *** [/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/
build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out]
Error 139
Makefile:65: recipe for target 'X300_HG' failed
make: *** [X300_HG] Interrupt
USRP-users mailing list
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
This looks like a bug in libpthread, possibly tripped-over by the Vivado
library that is next in the stack.
You should probably talk to Xinlinx support about this.
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
EJ-
Thanks I will play with the docker thing a little. A coworker tells me that it can be tough in case you need to run the GUI (which I do for other projects) but I will still play with it.
I can report that the glibc fix in the links you sent does work. They recommend installing to Xilinx’s library but I could not figure out how to do that so I did a regular system install and that seems a little scary however everything seems to work so far. Hopefully that will last me till we move to 2016.X someday…..
Thanks again,
Jeff
From: EJ Kreinar [mailto:ejkreinar@gmail.com]
Sent: Monday, September 26, 2016 6:34 PM
To: Long, Jeffrey P.
Cc: usrp-users@lists.ettus.com; Marcus D. Leech
Subject: RE: [USRP-users] x310 IP build failure
I did not try a glibc rebuild.
Just a thought: I admit there's a bit of a docker learning curve but I would highly encourage docker over a VM :) I found it to be extremely responsive (zero bootup time, etc) and it supports running the Vivado GUI without any problems. Plus, you can link the container into your local rfnoc prefix so all the build outputs are in-place in your directory. Very convenient
EJ
On Sep 26, 2016 4:46 PM, "Long, Jeffrey P." <jplong@mitre.orgmailto:jplong@mitre.org> wrote:
EJ-
Thanks good to hear I am not nuts but this is a bummer. Yes a VM should work and I have done this before and will do it again if I have to. Have you tried the glibc configured with –disable-lock-elision thing mentioned in those links?
By the way I rolled back to a UHD that builds with 2014.4 and that failed too.
Thanks
Jeff
From: EJ Kreinar [mailto:ejkreinar@gmail.commailto:ejkreinar@gmail.com]
Sent: Monday, September 26, 2016 4:33 PM
To: Long, Jeffrey P.
Cc: Marcus D. Leech; USRP-users@lists.ettus.commailto:USRP-users@lists.ettus.com
Subject: Re: [USRP-users] x310 IP build failure
Hi Jeff,
I ran into this same problem on my Ubuntu 16.04 LTS when starting to work with Xilinx. It seems to be related to more recent Intel processors. I also tried an installation of Vivado 2016.X and built a demo application for the Zynq as a sanity check, but the same issue showed up again (I'd be interested to hear if that solves the problem for you). Here's some hits I found online about the problem:
https://www.reddit.com/r/FPGA/comments/4olc29/is_anyone_running_vivado_2016x_on_a_recent_ubuntu/
https://forums.xilinx.com/t5/Synthesis/Vivado-crash-on-Ubuntu-16-04/td-p/699642/page/2
I HAVE had success running Xilinx in a Docker container. I currently do all my FPGA builds from this container. I've attached a tar of the Dockerfile and a readme, in case it can help you too. This should work with vivado from the command line or from GUI. I have only tested using the Xilinx license available for the e310, which is not nodelocked... If you need to build for the X300 series, you may need to handle licensing a bit differently. But at the very least, you should be able to test and confirm if the Vivado build works OK on your machine.
Regards,
EJ
On Mon, Sep 26, 2016 at 4:05 PM, Long, Jeffrey P. via USRP-users <usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com> wrote:
Yeah that is usually a waste of time. A quick search right now on libpthread and 2015.4 yielded similar issues. The canned Xilinx response is update to 2016.X, this fixes the issue. Unfortunately we can’t do that here. They also won’t even entertain my posts since I am using the very non-standard and unsupported Ubuntu 16 LTS. I have had this problem before. If you happen to be so unlucky that your version of vivado crashes then the only thing to do is roll back or forward in UHD till you find something that works. Switching around Oss is also an option albeit a pain.
I am going to try the 2015.4 update 2 patch. Do you happen to know if that will be OK from the setupenv.sh perspective?
Thanks
Jeff
From: USRP-users [mailto:usrp-users-bounces@lists.ettus.com] On Behalf Of Marcus D. Leech via USRP-users
Sent: Monday, September 26, 2016 3:21 PM
To: usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: Re: [USRP-users] x310 IP build failure
On 09/26/2016 03:13 PM, Long, Jeffrey P. via USRP-users wrote:
Wondering if anyone has seen this issue or knows what I may have wrong here. Trying to get familiar with RFNOC and the build process so I have pulled down the latest git, switched to rfnoc-devel, init’d and updated the submodule. I have installed vivado 2015.4 and have a full license and am running under Ubuntu 16 LTS. I sourced the setupenv.sh and then ran make X310_RFNOC_HG. By the way I also did the disable dash reconfig thing just in case.
It starts the IP generation for the 10 gig and then without any error it fails. Below is a snippet of the last bits before it dies. I also attached the error log and the ip build log.
Just as a data point I just did the same exact setup under Ubuntu 12 LTS and it did not fail so it seems that there is some issue with 16 LTS??
Thanks
Jeff
……
Finished RTL Optimization Phase 2 : Time (s): cpu = 00:00:25 ; elapsed = 00:00:25 . Memory (MB): peak = 1581.988 ; gain = 734.895 ; free physical = 29303 ; free virtual = 63061
Report RTL Partitions:
+-+--------------+------------+----------+
| |RTL Partition |Replication |Instances |
+-+--------------+------------+----------+
+-+--------------+------------+----------+
Start RTL Component Statistics
Finished RTL Component Statistics
Start RTL Hierarchical Component Statistics
Finished RTL Hierarchical Component Statistics
Start Part Resource Summary
Parent process (pid 8304) has died. This helper process will now exit
BUILDER: Releasing IP location: /home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma
/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/ip/ten_gig_eth_pcs_pma/Makefile.inc:41: recipe for target '/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out' failed
make[1]: *** [/home/jplong/proj/uhd/fpga-src/usrp3_rfnoc/top/x300/build-ip/xc7k325tffg900-2/ten_gig_eth_pcs_pma/ten_gig_eth_pcs_pma.xci.out] Error 139
Makefile:65: recipe for target 'X300_HG' failed
make: *** [X300_HG] Interrupt
USRP-users mailing list
USRP-users@lists.ettus.commailto:USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
This looks like a bug in libpthread, possibly tripped-over by the Vivado library that is next in the stack.
You should probably talk to Xinlinx support about this.
USRP-users mailing list
USRP-users@lists.ettus.commailto:USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com