Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Running Calibre xRC process killed

Status
Not open for further replies.

icactus2003

Newbie level 1
Joined
Nov 16, 2006
Messages
1
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
1,300
lvheap memory allocation failure

I have a user running running Calibre xRC (parasitic extraction tool) on AMD Opteron machines (dual core).
After running for more than 10 hours, the process was killed by itself.

I noticed the server was "hang" before the process got killed. Not be able to ssh or login physically on the machine.
Under normal condition, the process should be completed within 2 hours.

Below is the message appeared on terminal:-

INFO: Starting to process net u_sub_top_apa_1/u_sub_top_apa_2/u_core_apa/u_to
p_arm/USB/sw_wire_2358_BF_u_sub_top_apa_1\_u_sub_top_apa_2\_u_core_apa\_
u_top_arm\_USB_U37192_Y LVHEAP = 760/761/763 MALLOC = 57124/57124/57124
INFO: Starting to process net u_sub_top_apa_1/u_sub_top_apa_2/u_core_apa/u_to
p_arm/USB/sw_wire_7601_BF_u_sub_top_apa_1\_u_sub_top_apa_2\_u_core_apa\_
u_top_arm\_USB_U31725_Y LVHEAP = 760/761/763 MALLOC 57127/57127/57127
Killed
25666.238u 876.815s 11:27:45.91 64.3% 0+0k 0+0io 225168pf+0w


I found the following information in the manual;

Troubleshooting Virtual Memory Allocation Failures

The most common memory allocation error you might encounter when using Calibre tools is LVHEAP ALLOCATION FAILURE.

In most cases, the Calibre tool issues this error because the platform's swap is insufficient. Generally, you should set the platform's stacksize no larger than 8192 kilobytes. You can verify this by using the limit shell command on both HP‑UX and Solaris platforms. You can temporarily modify the stacksize in a C shell by typing the following in the shell: limit stacksize 8192

But when user did the above method and resend the job the similar problem occured.


Please help....really no idea what has goes wrong here....
 

calibre lvheap

give more information

os version
swap memory
ram
cpu
hdd size scsi or sata or ata

calibre version

may be have answer

Alcohol
 

calibre xrc res2

I faced similar problem. The extraction was taking too long almost 24 hrs and was getting killed after that. The problem is that once RAM is utilized it starts putting data on VM (HDD) and that takes too long. We had to increase VM and also by upgrading to newer version we saw significant improvement.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top