UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Visitor mhirota
Visitor
2,033 Views
Registered: ‎09-13-2017

Vivado 2016.4 Linux crash during Phase 7 Resynthesis

I am running the vivado build from the command line, using a TCL script, and it gets through a large portion of the build to the point where it says:

Phase 7 Resynthesis
Abnormal program termination (11)
Please check '/path/redacted/hs_err_pid5606.log' for details

Looking at that referenced file shows its contents:

#
# An unexpected error has occurred (11)
#
Stack:
/lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7ff9186004b0]
/lib/x86_64-linux-gnu/libc.so.6(strlen+0x26) [0x7ff918656746]
/lib/x86_64-linux-gnu/libc.so.6(+0x39bb9) [0x7ff918604bb9]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_common.so(HUTEnv::setEnv(char const*, char const*)+0xe) [0x7ff919725bde]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_place.so(HAOPAbcJobManager::HAOPAbcJobManager()+0x94f) [0x7ff8f69bc4bf]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_place.so(HAOPAbcOpt::HAOPAbcOpt(std::string, std::string)+0x2a5) [0x7ff8f69e1685]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_place.so(HAOPFlow::resynthesis(std::string, std::set<std::string, std::less<std::string>, std::allocator<std::string> >&, std::string)+0x6d) [0x7ff8f6a589cd]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_place.so(HAOPFlow::doabc(HDPLTask&, std::string, std::string, HANENetlist*, bool, bool)+0xcb) [0x7ff8f6a58dfb]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_place.so(HAOPFlow::optDesignMod()+0x5fe) [0x7ff8f6a5d39e]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_place.so(HAOPFlow::optimize()+0x1a0) [0x7ff8f6a5d830]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_vivadotasks.so(+0x306717) [0x7ff8e5d08717]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_vivadotasks.so(+0x308e14) [0x7ff8e5d0ae14]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_common.so(+0x5f8f37) [0x7ff9196b0f37]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(+0x331f5) [0x7ff9145af1f5]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(+0x76bbe) [0x7ff9145f2bbe]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(+0x7e767) [0x7ff9145fa767]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(TclEvalObjEx+0x77) [0x7ff9145b1327]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_commontasks.so(+0x2d0924) [0x7ff91059e924]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(+0x331f5) [0x7ff9145af1f5]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(+0x34d6b) [0x7ff9145b0d6b]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(+0xad531) [0x7ff914629531]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(+0x3491c) [0x7ff9145b091c]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(Tcl_EvalEx+0x16) [0x7ff9145b1276]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(Tcl_FSEvalFileEx+0x1d2) [0x7ff914615d02]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_commontasks.so(+0x2edfb2) [0x7ff9105bbfb2]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_common.so(+0x5f8f37) [0x7ff9196b0f37]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(+0x331f5) [0x7ff9145af1f5]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(Tcl_EvalObjv+0x32) [0x7ff9145af7e2]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(TclEvalObjEx+0x322) [0x7ff9145b15d2]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_commontasks.so(+0x30bef9) [0x7ff9105d9ef9]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_commontasks.so(+0x304d43) [0x7ff9105d2d43]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_common.so(+0x5f8f37) [0x7ff9196b0f37]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(+0x331f5) [0x7ff9145af1f5]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(Tcl_EvalObjv+0x32) [0x7ff9145af7e2]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(TclEvalObjEx+0x322) [0x7ff9145b15d2]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_commonmain.so(+0x6430) [0x7ff918eb3430]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/libtcl8.5.so(Tcl_Main+0x1d5) [0x7ff91461c175]
/opt/Xilinx/Vivado/2016.4/lib/lnx64.o/librdi_common.so(+0x631d09) [0x7ff9196e9d09]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba) [0x7ff9180ac6ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7ff9186d23dd]

Seems like a straight-forward crash to me, but I'm unsure how to log this with Xilinx (and whether I need to collect more build logs).

 

I'm attempting to contact Xilinx support, but I get a run-around on the website because it always says:

 

"""According to our records, you are a first time user. We will need to collect some additional information about you to ensure you receive the proper level of access and service.

 

Please click Next to continue. For additional support, please contact websupport_sponsor@xilinx.com ."""

 

Which I then complete, and have received an email saying:

 

"""Your Xilinx Service Portal account is now available. Once your service request is submitted via the portal a support agent will contact you to begin work on your request."""

 

 

 

However, every time I attempt to login, I get the same "first time user" page. :(

0 Kudos
9 Replies
Moderator
Moderator
2,000 Views
Registered: ‎09-15-2016

Re: Vivado 2016.4 Linux crash during Phase 7 Resynthesis

Hi @mhirota,

 

- Did you check project mode/in GUI for this issue?

- Is it possible to share the test-case/design files with us to reproduce this termination problem?

- Did you try using different synthesis directives? 

 

>>Seems like a straight-forward crash to me, but I'm unsure how to log this with Xilinx (and whether I need to collect more build logs).

Yes, this looks to be termination issue as mentioned in this debug AR. 

- Which exact Linux distribution are you using?

- Can you try this with our latest Vivado release 2017.2?

 

i am not sure on the web account > you can try to contact websupport_sponsor@xilinx.com as mentioned in the webpage.

 

--------------------------------------------------------------
Please mark the appropriate answer as "Accept as solution" if information provided is helpful.
Give 'Kudos' to a post which you think is useful and reply oriented.
--------------------------------------------------------------

0 Kudos
Scholar watari
Scholar
1,980 Views
Registered: ‎06-16-2013

Re: Vivado 2016.4 Linux crash during Phase 7 Resynthesis

Hi @mhirota

 

I'm sure that you are faced with following problem.

Please refer it.

https://forums.xilinx.com/t5/Implementation/Vivado-2017-1-Abnormal-program-termination/td-p/763275

 

Thank you.

Best regards

0 Kudos
Visitor mhirota
Visitor
1,967 Views
Registered: ‎09-13-2017

Re: Vivado 2016.4 Linux crash during Phase 7 Resynthesis

@prathikm I am using Ubuntu 16.04.3 server:  

 

Linux vivadobuilder 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

 

I am unable to use 2017.2 because the project owner has locked us into 2016.4.

 

0 Kudos
Visitor mhirota
Visitor
1,966 Views
Registered: ‎09-13-2017

Re: Vivado 2016.4 Linux crash during Phase 7 Resynthesis

@watari Thank you for the related issue.  I agree that it looks to be the same.  It seems for now I have found a workaround -- just add this to my TCL script I'm using for the build:

set_param general.maxThreads 1

However, like I say -- this is just a workaround and I would rather see a fix in 2016.4 version (and 2017.2 if the bug exists there too) so that I can take advantage of the 16 cores that my build server has.

0 Kudos
Scholar watari
Scholar
1,954 Views
Registered: ‎06-16-2013

Re: Vivado 2016.4 Linux crash during Phase 7 Resynthesis

Hi @mhirota

 

According to "AR#54242" and "AR#66184", "Ubuntu" needs to install some additional libraries.

Have you already installed them ?

 

BTW, can you change OS from Ubuntu to ex. CentOS ? Can you use virtual machine on Ubuntu 2016.4.3 ?

 

[URL]

https://www.xilinx.com/support/answers/54242.html

https://www.xilinx.com/support/answers/66184.html

 

[Note]

We don't have similar issue on CentOS 6.9 and 7.3.

But it may that we don't use "resynthesis" command on tcl script.

 

Thank you.

Best regards,

 

0 Kudos
Visitor mhirota
Visitor
1,950 Views
Registered: ‎09-13-2017

Re: Vivado 2016.4 Linux crash during Phase 7 Resynthesis

I haven't installed "additional libraries" -- but neither can I find a listing for Ubuntu 16.04 nor do I think I need them because I'm not using DocNav, Lab Tools, or HW Server...

 

At any rate, I doubt it is an installation issue if I'm able to workaround it using an option to disable multi-threading in the resynthesis (and other portions) of the build.

 

Thank you for the suggestions though!

0 Kudos
Highlighted
1,470 Views
Registered: ‎06-04-2015

Re: Vivado 2016.4 Linux crash during Phase 7 Resynthesis

Thank you @mhirota for your fix. This worked for me.

The Ubuntu update fix (i.e., apt-get update; apt-get upgrade) listed on another thread did not work for me.

0 Kudos
Visitor stefanct
Visitor
368 Views
Registered: ‎02-05-2019

Re: Vivado 2016.4 Linux crash during Phase 7 Resynthesis


@mhirota wrote:

@watari Thank you for the related issue.  I agree that it looks to be the same.  It seems for now I have found a workaround -- just add this to my TCL script I'm using for the build:

set_param general.maxThreads 1

However, like I say -- this is just a workaround and I would rather see a fix in 2016.4 version (and 2017.2 if the bug exists there too) so that I can take advantage of the 16 cores that my build server has.


And it seems like it does not always help. In my case (also with 2016.4) the crash was replaced with what seems to be an endless loop (I have waited about 5 times the usual time of that step).

0 Kudos
Moderator
Moderator
355 Views
Registered: ‎03-16-2017

Re: Vivado 2016.4 Linux crash during Phase 7 Resynthesis

Hi @stefanct ,

yes, it will not help all the time. All crashes are almost different with different root causes.

Hence, i will recommend you to create a new thread with your query so we can debug it asap. 

Regards,
hemangd

Don't forget to give kudos and mark it as accepted solution if your issue gets resolved.
0 Kudos