Operating System - HP-UX
1846610 Members
2270 Online
110256 Solutions
New Discussion

Re: Reboot after Panic: kalloc

 
R.Suresh
Frequent Advisor

Reboot after Panic: kalloc

Dear all,

I am having HP-9000 D270 server running
10.20,
Every day it is crashing by saying

Reboot after panic: kalloc:out of kernel virtual space.

Any kernel parameter to be tuned?

Thanks & Regards
R.Mahendran.

PDLS
4 REPLIES 4
Printaporn_1
Esteemed Contributor

Re: Reboot after Panic: kalloc

Hi,

Please try increase nproc.
Regards,
enjoy any little thing in my life
Edward Sedgemore
Trusted Contributor

Re: Reboot after Panic: kalloc


* Increasing 'nproc' - this kernel parameter controls the table that is overflowing.

Note: If you increase the table size by tweaking
`maxusers', you will also increase other table sizes. No great harm in that, but not necessary. 'nproc' is the
one.
Pedro Sousa
Honored Contributor

Re: Reboot after Panic: kalloc

Hi!
hope the following helps:
"A "kalloc: out of kernel virtual space" panic is typically caused due to sysmap fragmentation. This is fixed by increasing the size of the kernel parameter nproc.

Sysmap is sized by NPROC (NPROC * 2), so it should be increased to greater than 800, and monitored and increased further if sysmap rmap ovflo messages still appear.
Sysmap is a resource map used by the kernel to manage free areas of
virtual space available to the kernel. The map is a fixed size (in
pages) and address pairs. As kernel virtual space is allocated, sysmap is
updated appropriately."

good luck.

Congratulations for your new hat Edward!
Mark Mitchell
Trusted Contributor

Re: Reboot after Panic: kalloc