cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
user123random
Adventurer
Adventurer
4,993 Views
Registered: ‎05-02-2017

Vivado crashes during startup

When I start Vivado by clicking the its logo icon or in terminal command-line mode, Vivado crashes after a short while with the following error log.

 

[linux@localhost]$ sh -c "unset LANG && unset QT_PLUGIN_PATH && source /opt/Xilinx/Vivado/2017.1/settings64.sh && vivado"

****** Vivado v2017.1 (64-bit)
  **** SW Build 1846317 on Fri Apr 14 18:54:47 MDT 2017
  **** IP Build 1846188 on Fri Apr 14 20:52:08 MDT 2017
    ** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.

start_gui
Abnormal program termination (11)
Please check '/home/linux/hs_err_pid5594.log' for details
[linux@localhost]$ cat /home/linux/hs_err_pid5594.log
#
# An unexpected error has occurred (11)
#
Stack:
/opt/Xilinx/Vivado/2017.1/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x923da9) [0x7f1e34daeda9]
/opt/Xilinx/Vivado/2017.1/tps/lnx64/jre/lib/amd64/server/libjvm.so(JVM_handle_linux_signal+0xb6) [0x7f1e34db53f6]
/opt/Xilinx/Vivado/2017.1/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x9209d3) [0x7f1e34dab9d3]
/usr/lib/libc.so.6(+0x33a90) [0x7f1e6dee9a90]
/opt/Xilinx/Vivado/2017.1/tps/lnx64/jre/lib/amd64/libawt_xawt.so(+0x42028) [0x7f1e15c09028]
/opt/Xilinx/Vivado/2017.1/tps/lnx64/jre/lib/amd64/libawt_xawt.so(+0x42288) [0x7f1e15c09288]
/opt/Xilinx/Vivado/2017.1/tps/lnx64/jre/lib/amd64/libawt_xawt.so(Java_sun_awt_X11_XRobotPeer_getRGBPixelsImpl+0x17c) [0x7f1e15c0167c]
[0x7f1e24e4e4cf]

 

I found it is relevant to https://bugs.openjdk.java.net/browse/JDK-8170519 but I am not sure.

Any advice ?

0 Kudos
13 Replies
thakurr
Moderator
Moderator
4,963 Views
Registered: ‎09-15-2016

Hi @user123random

 

Please check the below link of AR:

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

 

Regards

Rohit

 

 ---------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------

Regards
Rohit
----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------

0 Kudos
prathikm
Moderator
Moderator
4,952 Views
Registered: ‎09-15-2016

Hi @user123random,

 

Can you please attach the environment report report_environment -file <your_path>/env.txt?

 

Regards,

Prathik

0 Kudos
user123random
Adventurer
Adventurer
4,948 Views
Registered: ‎05-02-2017

I have attached env.txt as below.

 

 

0 Kudos
nupurs
Moderator
Moderator
4,939 Views
Registered: ‎06-24-2015

@user123random,

 

Which OS are you using?

 

Make sure you are using supported OS:
• Red Hat Enterprise Workstation/Server 7.2 and 7.3 (64-bit)

• Red Hat Enterprise Workstation 6.6, 6.7, and 6.8 (64-bit)

• SUSE Linux Enterprise 11.4 and 12.2 (64-bit)

• Cent OS 7.2 and 7.3 (64-bit)

• Cent OS 6.7 and 6.8 (64-bit)

• Ubuntu Linux 16.04.1 LTS (64-bit)

Thanks,
Nupur
--------------------------------------------------------------------------------------------
Google your question before posting. If someone's post answers your question, mark the post as answer with "Accept as solution". If you see a particularly good and informative post, consider giving it Kudos (click on the 'thumbs-up' button).
0 Kudos
prathikm
Moderator
Moderator
4,930 Views
Registered: ‎09-15-2016

Hi @user123random,

 

The env.txt file shows -

 

| Platform                  | unknown                                   |
| Operating System          | unknown 

 

Regards,
Prathik
-----------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helps to resolve your query.
Helpful answer -> Give Kudos
-----------------------------------------------------------------------------------------------

0 Kudos
user123random
Adventurer
Adventurer
4,893 Views
Registered: ‎05-02-2017

Thanks. It is not an OS-specific problem.

 

It seems like it is a bug of gnome using wayland.

Using Vivado with gnome using Xorg had solved this problem, at least for now.

 

By the way, I am using Arch Linux x86-64 platform.

nupurs
Moderator
Moderator
4,824 Views
Registered: ‎06-24-2015

@user123random,

 

Glad to know that the issue is resolved.

Please mark your answer as "Accept as Solution" so that it can help other users.

Thanks,
Nupur
--------------------------------------------------------------------------------------------
Google your question before posting. If someone's post answers your question, mark the post as answer with "Accept as solution". If you see a particularly good and informative post, consider giving it Kudos (click on the 'thumbs-up' button).
0 Kudos
tcmichals
Visitor
Visitor
3,389 Views
Registered: ‎01-18-2018

I'm having the same issue using Ubuntu 17.10; by default Wayland is enabled.   Using X, the crash does not occur.

 

When Wayland is used the following crash occurs:

 

# An unexpected error has occurred (11)
#
Stack:
/home/tcmichals/projects/Xilinx/Vivado/2017.4/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x923da9) [0x7fccfd057da9]
/home/tcmichals/projects/Xilinx/Vivado/2017.4/tps/lnx64/jre/lib/amd64/server/libjvm.so(JVM_handle_linux_signal+0xb6) [0x7fccfd05e3f6]
/home/tcmichals/projects/Xilinx/Vivado/2017.4/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x9209d3) [0x7fccfd0549d3]
/lib/x86_64-linux-gnu/libc.so.6(+0x37140) [0x7fcd3acfb140]
/home/tcmichals/projects/Xilinx/Vivado/2017.4/tps/lnx64/jre/lib/amd64/libawt_xawt.so(+0x42028) [0x7fccde4fe028]
/home/tcmichals/projects/Xilinx/Vivado/2017.4/tps/lnx64/jre/lib/amd64/libawt_xawt.so(+0x42288) [0x7fccde4fe288]
/home/tcmichals/projects/Xilinx/Vivado/2017.4/tps/lnx64/jre/lib/amd64/libawt_xawt.so(Java_sun_awt_X11_XRobotPeer_getRGBPixelsImpl+0x17c) [0x7fccde4f667c]

 

0 Kudos
anatoli
Moderator
Moderator
3,346 Views
Registered: ‎06-14-2010

Hello @user123random and @tcmichals,

 

Thanks for letting us know and for sharing this workaround.

I've just create an Answer Record with this info, so that this can help other users with the same problem in the future.

The AR # is 70442. It will be publicly released shortly as it first needs to be technically reviewed by the experts.

 

Can you please mark your response as "Accepted Solution", so  the topic can be completed then and can help other users in the future? We appreciate your help.

 

 

Have a nice day.

 

 

Kind Regards,
Anatoli Curran,
Xilinx Technical Support
------------------------------------------------------------------------------------------------

Don’t forget to reply, kudo, and accept as solution.

If starting with Versal, take a look at our Versal Design Process Hub and our
Versal Blogs

------------------------------------------------------------------------------------------------
tcmichals
Visitor
Visitor
2,317 Views
Registered: ‎01-18-2018

might want to add instructions on how to switch for wayland to xorg.  i.e

https://itsfoss.com/switch-xorg-wayland/

 

mark.harfouche
Observer
Observer
2,176 Views
Registered: ‎11-05-2014

One person seems to have found the culprit:

https://twitter.com/edgetriggered/status/918852297077207045/photo/1

 

I tried:

 

sudo cp /usr/lib/jvm/java-1.8.0-openjdk/jre/lib/amd64/libawt_xawt.so  /opt/Xilinx/Vivado/2018.1/tps/lnx64/jre/lib/amd64/libawt_xawt.so

Seems to be stable for 5 minutes.

mark.harfouche
Observer
Observer
2,158 Views
Registered: ‎11-05-2014

I seem to have spoken too soon.

 

It is still crashing on my computer. I don't think my proposed fix is a real one, especially since the two `.so` files were probably compiled differently.

 

 

0 Kudos
mark.harfouche
Observer
Observer
2,121 Views
Registered: ‎11-05-2014

I tried to link the jre directory to my system openjdk implementation.

 

There still seemed to be some problems. After looking it at more deeply, it seems to be an underlying issue with OpenJDK 8 (or 1.8).

 

It seems it will be fixed in OpenJDK 11 (or 1.11)

 

https://bugzilla.redhat.com/show_bug.cgi?id=1402819

 

 

0 Kudos