Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
16599 Discussions

Quartus 22.4 crash "Internal Error: Sub-system: VRFX2, File: /quartus/synth/vrfx2/vrfx2_xmr.cpp"

mpr90
Beginner
776 Views

When running synthesis on a design that synthesizes (and compiles) fine under Quartus Prime 19.2, I consistently get the following crash happening. It also crashes similarly under Quartus 23.1. Any ideas please?

 

Problem Details
Error:
Internal Error: Sub-system: VRFX2, File: /quartus/synth/vrfx2/vrfx2_xmr.cpp, Line: 254
ancestor_node
Stack Trace:
Quartus 0x8cf088: VRFX2_INST_GRAPH::dfs_paths(VRFX2_INST_NODE*, QTL_HASH_LITE<VRFX2_INST_NODE*, int, QTL_OPS<VRFX2_INST_NODE*, void> >*, QTL_HASH_LITE<VRFX2_INST_NODE*, VRFX2_INST_NODE*, QTL_OPS<VRFX2_INST_NODE*, void> >*, std::vector<Instance*, std::allocator<Instance*> >*) + 0x1ac (synth_vrfx2)
Quartus 0x8cf249: VRFX2_INST_GRAPH::find_common_ancestor_and_inst_paths(Netlist*, Netlist*, std::vector<Instance*, std::allocator<Instance*> >*, std::vector<Instance*, std::allocator<Instance*> >*) + 0x1bb (synth_vrfx2)
Quartus 0x8d202b: vrfx2_connect_global_net_to_port_or_portref(PortRef*, Port*, Net*, VRFX2_INST_GRAPH*, QTL_HASH_LITE<std::pair<Netlist*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, Port*, QTL_OPS<std::pair<Netlist*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, void> >*, QTL_HASH_LITE<std::pair<Netlist*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, Net*, QTL_OPS<std::pair<Netlist*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, void> >*) + 0x742 (synth_vrfx2)
Quartus 0x8d3d0f: vrfx2_process_global_net(Net*, VRFX2_INST_GRAPH*) + 0x304 (synth_vrfx2)
Quartus 0x8d4254: vrfx2_process_xmr_connections(BASEX_ELABORATE_INFO*, Array*, Netlist*) + 0x483 (synth_vrfx2)
Quartus 0x81665e: new_verific::VRFX2_EXTRACTOR::extract_hierarchy(char const*, std::vector<BASEX_ENTITY*, std::allocator<BASEX_ENTITY*> > const&, BASEX_ELABORATE_INFO*, bool, bool, bool, bool, bool) + 0x1264 (synth_vrfx2)
Quartus 0xfa337: QIS_RTL_STAGE::IMPL::elaborate_verific(QHD_PARTITION*, BASEX_ENTITY*, BASEX_ELAB_INFO_CORE&, std::vector<BASEX_ENTITY*, std::allocator<BASEX_ENTITY*> > const&) + 0x339 (synth_qis)
Quartus 0x10babd: QIS_RTL_STAGE::IMPL::elaborate(QHD_PARTITION&) + 0x2379 (synth_qis)
Quartus 0x10dcda: QIS_RTL_STAGE::elaborate(QHD_PARTITION&) + 0xc (synth_qis)
Quartus 0xa16eb: qis_elaborate + 0x246 (synth_qis)
Quartus 0x50fb7: TclNRRunCallbacks + 0x47 (tcl8.6)
Quartus 0x527df: TclEvalEx + 0x94f (tcl8.6)
Quartus 0xfa3a6: Tcl_FSEvalFileEx + 0x266 (tcl8.6)
Quartus 0xfa4be: Tcl_EvalFile + 0x2e (tcl8.6)
Quartus 0x2a8fc: qexe_evaluate_tcl_script(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0x3de (comp_qexe)
Quartus 0x2dd73: qexe_do_tcl(QEXE_FRAMEWORK*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::list<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, bool, bool) + 0x4c2 (comp_qexe)
Quartus 0x2ee7b: qexe_run_tcl_option(QEXE_FRAMEWORK*, char const*, std::__cxx11::list<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >*, bool) + 0x66e (comp_qexe)
Quartus 0x6d1ec: QCU::DETAIL::intialise_qhd_and_run_qexe(QCU_FRAMEWORK&, FIO_PATH const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char const*, std::__cxx11::list<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >*, bool) + 0x9c (comp_qcu)
Quartus 0x6d638: qcu_run_tcl_option(QCU_FRAMEWORK*, char const*, std::__cxx11::list<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >*, bool) + 0x343 (comp_qcu)
Quartus 0x409075: qsyn2_tcl_process_default_flow_option(ACF_VARIABLE_TYPE_ENUM, char const*) + 0x501 (quartus_syn)
Quartus 0x3421d: qexe_standard_main(QEXE_FRAMEWORK*, QEXE_OPTION_DEFINITION const**, int, char const**) + 0xba2 (comp_qexe)
Quartus 0x408ace: qsyn2_main(int, char const**) + 0x139 (quartus_syn)
Quartus 0x4e546: msg_main_thread(void*) + 0x10 (ccl_msg)
Quartus 0x4f764: msg_thread_wrapper(void* (*)(void*), void*) + 0x8c (ccl_msg)
Quartus 0x1f568: mem_thread_wrapper(void* (*)(void*), void*) + 0x98 (ccl_mem)
Quartus 0x10f3a: err_thread_wrapper(void* (*)(void*), void*) + 0x1e (ccl_err)
Quartus 0xb7f5: thr_thread_wrapper + 0x15 (ccl_thr)
Quartus 0x4f684: msg_exe_main(int, char const**, int (*)(int, char const**)) + 0xd8 (ccl_msg)
Quartus 0x40898e: main + 0x26 (quartus_syn)
System 0x21c87: __libc_start_main + 0xe7 (c)
Quartus 0x4088b9: _start + 0x29 (quartus_syn)

End-trace

Executable: quartus
Comment:
None

System Information
Platform: linux64
OS name: Ubuntu 18.04.6
OS version: 18

Quartus Prime Information
Address bits: 64
Version: 22.4.0
Build: 94
Edition: Pro Edition

 

0 Kudos
8 Replies
SyafieqS
Moderator
753 Views

Hi,


Do you mind attach the qar for me to replicate?

Need the design for further investigation.

Small design to replicate would be better.


0 Kudos
mpr90
Beginner
734 Views

Hi, I'm afraid I can't share the design as-is. Whilst it may be possible with some effort to reduce the design size and remove IP to allow sharing/reproduction, I'd like to know please if there are other things that I can do to gather forensics that may help to identify the culprit in this crash?

0 Kudos
SyafieqS
Moderator
690 Views

Internal error is normally a tool issue (most of it).

Thus, will be better if you can create small design replicating the error for further debugging.



0 Kudos
SyafieqS
Moderator
690 Views

Also, have you tried on 23.1 Pro?

Thus that resolve the issue?

Please let me know, otherwise I will need the small test case for investigation.


0 Kudos
mpr90
Beginner
633 Views

Running under Quartus 23.1 Pro had similar results: it also crashed.

It will take some time to get a test case together due to many other priorities, but I'll come back when I have one.

0 Kudos
SyafieqS
Moderator
659 Views

Let me know if there is any update from previous reply


0 Kudos
SyafieqS
Moderator
617 Views

Hello


Let me know if there is any update from your end.




0 Kudos
SyafieqS
Moderator
565 Views

As we do not receive any response from you on the previous question/reply/answer that we have provided. Please login to ‘https://supporttickets.intel.com’, view details of the desire request, and post a feed/response within the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support. The community users will be able to help you on your follow-up questions.


p/s: If any answer from community or Intel support are helpful, please feel free to mark as solution, give Kudos and rate 5/5 survey


0 Kudos
Reply