Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 14686
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Spectre segmentation fault

Pavel2022

Dear Cadence support,

we encountered a problem with our new computing server (please see specs below) during Spectre simulation. When we use 64 GB (2x32 GB) RAM memory, spectre simulation is running without any problem. When we enhance RAM to 128 GB (4x32 GB), spectre will stop with a segmentation fault (log attached). Thank you for any advice how to resolve this problem.

HW:

OS:

We have tried the following RAM types with the same result:

log file:


**************************************************
Transient Analysis `tran': time = (0 s -> 1.025 s)
**************************************************
Finding DC approximate solution failed with try_fast_op=yes, continue running with try_fast_op=no.
Trying `homotopy = gmin' for initial conditions.

Internal error found in spectre during IC analysis, during transient analysis `tran'.
    FATAL (SPECTRE-18): Segmentation fault. Encountered a critical error during simulation. Run `mmsimpack' (see mmsimpack -h for detailed usage information) to package the netlist and log files as a compressed tar file. Then, contact your Cadence representative or submit a service request via Cadence Online Support, including the tar file and any other information that could help identify the problem. Encountered a critical error during simulation. Run `mmsimpack' (see mmsimpack -h for detailed usage information) to package the netlist and log files as a compressed tar file. Then, contact your Cadence representative or submit a service request via Cadence Online Support, including the tar file and any other information that could help identify the problem.

Version 21.1.0.132.isr1 64bit -- 11 Sep 2021

****ASSERTION STACK****
        0x649a013
        0x8861ac
        0x887107
        0x7f81984d5ce0
        0x1df8480
        0x1e0e679
        0x14ff97f
        0x17cc59a
        0x1beea71
        0x4dc4fbc
        0x4dc5188
        0x4dc5459
        0x7f81984cb1cf
        0x7f8197983dd3

****LIBRARIES****
        spectre/bin/64bit/spectre [0x400000]
        /lib64/libpthread.so.0 [0x7f81984c3000]
        /lib64/libc.so.6 [0x7f819794a000]

  • Pavel2022 said:
    Dear Cadence support

    I should point out that these forums are not "Cadence support". This is a community forum where users (and people from Cadence too) can help each other out. It seems rather odd to me that adding more memory would cause a segmentation fault - most likely it's some memory access issue that a small change in memory contents causes a somewhat random change in behaviour.

    You should report this by contacting customer support via http://support.cadence.com - you can log a case there. However, given that you're not using the latest hotfix, I would first suggest that you install the latest SPECTRE21.1 ISR (ISR10) as it's quite possible the issue has already been resolved. Determining what is wrong without a testcase is going to be very difficult - but certainly checking the latest hotfix first makes the most sense.

    Regards,

    Andrew

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.