https://open-source-silicon.dev logo
a

Anuj Dubey

04/17/2022, 5:16 PM
My OpenLane runs are getting killed by the OOM killer during detailed routing. I am currently checking my RTL to find any inefficiencies, which is most likely the reason for this. But does anyone know some other way to unblock myself, like a flag in config.tcl, or changing some options in the OS, etc.? @User?
v

Vijayan Krishnan

04/17/2022, 5:21 PM
@User Child killed due to system resources. Mostly not have enough RAM for routing. What's your system RAM?
a

Anuj Dubey

04/17/2022, 5:22 PM
16 GB. I have tried this on higher config machine (128 GB) and the run went through. But I do not have access to that machine at the moment, and wanted to fix this in the current setup itself.
v

Vijayan Krishnan

04/17/2022, 5:23 PM
is design have memory modules?
a

Anuj Dubey

04/17/2022, 5:25 PM
Yes. 2 modules of 64x4 bits. That's not a lot, right?
Can I get some hint from the logs of the completed steps like synth, fp, etc.?
v

Vijayan Krishnan

04/17/2022, 5:26 PM
Memory modules required more RAM
a

Anuj Dubey

04/17/2022, 5:27 PM
I see. Okay, I'll try moving them out of the design and giving it another try.
a

Arman Avetisyan

04/17/2022, 7:24 PM
I got the same issue. Helped decreasing the utilization to like 25%
h

htamas

04/17/2022, 7:43 PM
@User You could add some swap (i.e. pagefile or disk-based memory) to your system. It will slow down your run but it will eventually go through.
a

Anuj Dubey

04/18/2022, 4:24 AM
@User: how can I do that?
a

Anuj Dubey

04/20/2022, 10:37 PM
Thanks @User, increasing the swap space did help me to get past the OOM kill point.
👍 1