Error creating a new kernel (out of memory)

[Marco Camacho_1]

Hi all.
when a try to build a new kernel after change the parameter mxdsiz_4bit, the next message appears:
"Cannot build a kernel using /usr(sbin/config. The standar output of the command is shown below:
Out of memory"

I´ll appreciate your comments and time.!!
Regards.

[Steven E. Protter]

Shalom,

Wow, never got that while building a kernel.

Sugguestions:
1) Shut down some applications and try again.
2) Make sure all the necessary files to build a kernel are acctually present on /stand
3) Change the parameter you changed back to its prior value and try again, you may have exceeded some limit.

What is the OS and patch level?

SEP

[Jaime Bolanos Rojas.]

Marco,

Did you already check this document in the ITRC site, looks much like the issue you are having:

KBRC00002650

Regards,

Jaime.

[Marco Camacho_1]

Thanks all.
This system is hp-ux 11.11

I have already sttoped some processes (Oracle, HP OVO and NNM) and i tryed to rebuilt with the same problem.

The contents of /stand is

bootconf ioconfig krs_tmp/ system.d/
build/ kernrel lost+found/ system.prev
dlkm/ krs/ rootconf vmunix*
dlkm.vmunix.prev/ krs_lkg/ system vmunix.prev*

how can i find the document you suggested ?


thanks all!

[Jaime Bolanos Rojas.]

Marco,

You want to go to Maintenance and Support for HP products link, then search technical knowledge base link, the in the drop down menu select search by Doc ID, the put the ID overthere.
I believe you need to have an HP contract tied to your profile ID to view the solution on the document.

Regards,

Jaime.

[Steven E. Protter]

Shalom,

http://irtc.hp.com
http://www1.itrc.hp.com/service/cki/enterService.do
Search technical knowlege base by doc id.

Search by document id:
KBRC00002650

I have no running HP-UX systems in my apartment(late here) so I suggest comparing the /stand components to a system that does have the ability to compile a kernel.

I also really think backing out the parameter change is a good idea. If you still can't generate a kernel then it eliminates illegal values as a possible cause.

[A. Clay Stephenson]

I seen this happen a number of times on the Forums --- and everytime, it's a result of setting one of the memory limits too low in a previous kernel build. You should be about to boot the previous kernel (vmunix.prev) and presumably its maxssiz and maxdsiz are large enough to allow you to build a new kernel. To be safe, the very first thing I would do is cp /stand/vmunix.prev to /stand/vmunix.safe so that when you build a new kernel, you will still have a known bootable kernel. Remember, maxXsiz and maxXsiz_64bit are set in bytes rather than KiB's, pages, or MIB's so set them to reasonable values. Maxssiz should be no larger than 32MiB and maxssiz_64bit should be no larger than 64MiB --- and these values are quite generous. Make sure that all of your _64bit values are at least as large as their 32-bit counterparts.

[Marco Camacho_1]

Clay.

To do your advice, do i only need to rename the vmunix.prev to vmunix and reboot system?
Of course, i already copied the actual file for backup.

The Doc id it seems not exists anymore.

thanks.

[A. Clay Stephenson · Accepted solution]

It's quite simple. Shutdown and reboot. Interrupt the normal boot process and at the firmware monitor, enter "BOOT PRI" to boot from the primary disk. You will see "Interact with ISL/IPL? (Y/N)". Respond with "Y". At the "ISL/IPL>" prompt, enter "hpux vmunix.prev".

Man hpux for details.

[Marco Camacho_1]

Thanks for your time and comments, we reboot the server with previuos Kernel as you suggested and we were able to modify the parameters with out the error message. thanks !!

[Marco Camacho_1]

We restore the server with previous Kernel, it seems has a bad configured parameters. Thanks