- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi,
when I run synthesis and analysis in my project it crashes after 6min. The crash happens every time (with fresh sources and quartus project). I cannot share whole project and stack trace gives no clues where the problem could be. Please find below report:
Problem Details
Error:
*** Fatal Error: Segment Violation: faulting address=(nil), PC=(nil) : 0:
Module: quartus_syn
Stack Trace:
Err Handler 0x122f8: ERR_UNWINDER_BACKTRACE::get_stack_trace(void const**, int, int, void*) + 0xe0 (ccl_err)
Err Handler 0x8a1f6: msg_ie_get_call_stack(void*) + 0xc4 (ccl_msg)
Err Handler 0x8ba52: MSG_INTERNAL_ERROR::report_fatal(char const*, void*, bool) + 0x40 (ccl_msg)
Err Handler 0x14fd2: err_report_fatal_exception(char const*, void*, bool) + 0x6f (ccl_err)
Err Handler 0x15b1c: err_sigaction_handler + 0x191 (ccl_err)
System 0x12980: (pthread)
End-trace
Executable: quartus
Comment:
crash during synth
System Information
Platform: linux64
OS name: Ubuntu 18.04.1
OS version: 18
Quartus Prime Information
Address bits: 64
Version: 22.2.0
Build: 94
Edition: Pro Edition
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Wija,
Update:
The fix has been ported to 23.1, and will branch to 22.4 around next week for fix.
Regarding current version you are using, I am pending reply on requesting a workaround or possibly a patch. Let me know if that is okay.
링크가 복사됨
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Wija,
Seem this is valid bug as you had hit fatal error. Is it possible to create small test case replicating the issue?
This could help us to investigate and fix the issue
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi,
As I wrote before its not possible to create small test case in situation where Quartus gives mi no clue what part of code is it processing. Is it possible increase verbosity, or add patch with additional logs? With that, I will try to prepare the test case.
Regards,
Piotr
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Wija,
Understood, Since you are not able to attach the design, is it possible to attach the database here? You may refer to link below to compile database without sending your source design files.
https://www.intel.com/content/www/us/en/support/programmable/articles/000076181.html
We need at least some input other than the message to debug.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Wija,
Thank you. I will replicate the issue and let you know any findings.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
HI Wija,
Apologize for the delay as i was in a long holiday.
May I know what device you use? S10? A10?
Can just achieve the design with your top.sv and attach the qar here?
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
I am able to reproduce the issue.
Let me check this internally.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Wija,
I found a KDB related to your issue, Please take a look as this might resolve your issue.
https://www.intel.com/content/www/us/en/support/programmable/articles/000090049.html
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi,
I can't see any correlation between my case and KDB that you send.
1. I do not use import inside modport
2. I do not have localparam which depends on other parameter in the interface
3. I checked it on Quartus 22.2 and KDB was fixed since 22.1
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Wija,
Understood. I had filed a report to the developer for further debug and this is a real bug.
I will let you know once there is any update.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Wija,
This might be taking sometime and I will let you know once there is any update from engineering.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
HI Wija,
Update:
This issue is due to verific bug and developer escalated this to verific team for bug fixes.
Still pending more update and will let you know once there is any findings
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Wija,
Update: Developer just got the dump from Verific today that has the fix for this issue. They will test it on all their suites and have it checked in within a week. Will get back to you with findings
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Wija,
Update:
The fix has been ported to 23.1, and will branch to 22.4 around next week for fix.
Regarding current version you are using, I am pending reply on requesting a workaround or possibly a patch. Let me know if that is okay.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hello Wija,
Are you still following this discussion? Let me know if there is any update at your end.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi,
thank you for the update. Fix in Quartus 23.1 will be enough for me. I do not need workaround.
Thanks,
Piotr
