HPUX system crashing at multi-user boot - single user mode boot ok...

[Steve Reece_3]

I have an HP-UX system that's crashing when coming up in multi-user mode.  When it boots in single-user mode, it comes up ok.

It objects to a kernel module prior to the crash, then crashes with a "panic: kalloc: out of kernel virtual space" error.

The physical memory in the system hasn't changed.

Any ideas please?

Starting the STREAMS daemons-phase 1
Create STCP device files
Starting the STREAMS daemons-phase 2
         $Revision: vmunix:    vw: -proj    selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_11
8 'CUPI80_BL2000_1108'  Wed Nov  8 19:24:56 PST 2000 $
Memory Information:
    physical page size = 4096 bytes, logical page size = 4096 bytes
    Physical: 2095104 Kbytes, lockable: 1501920 Kbytes, available: 1740160 Kbytes

NOTICE: vpath loading v1.6.0.9  (Feb  3 2005 14:36:35)

NOTICE: vpath loading successfully

mod_obj_load: Undefined symbol drmfgl_wrapper in loadable module /stand/dlkm/mod.d/gvid_info.
WARNING: MOD: mod_obj_load: Processing symbol table in module /stand/dlkm/mod.d/gvid_info failed

System Panic:

linkstamp:          Tue Aug 2 08:45:26 BST 2005
_release_version:   @(#)     $Revision: vmunix:    vw: -proj    selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build'
-- cupi80_bl2000_1108 'CUPI80_BL2000_1108'  Wed Nov  8 19:24:56 PST 2000 $
panic: kalloc: out of kernel virtual space

PC-Offset Stack Trace (read across, top of stack is 1st):
  0x0020e958  0x00493160  0x0016e10c
  0x001991ac  0x0049a3d4  0x0019925c
  0x00199524  0x00097e9c  0x00550b44
  0x0054ebd0  0x0054b5a0  0x0054bc10
  0x0054c5d4  0x0014d9dc  0x00033f64
End Of Stack

[Patrick Wallek]

What version of HP-UX are you running?  What model of system is this?

[Steve Reece_3]

I believe it's 11.11 and it's on an rp3440.

[Patrick Wallek]

If you have a support contract have a look at this:

https://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?spf_p.tpst=kbDocDisplay&spf_p.prp_kbDocDisplay=wsrp-navigationalState%3DdocId%253Demr_na-c01096262-3%257CdocLocale%253Den%257CcalledBy%253DSearch_Result&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken

For this particular issue apparently a couple of the semaphore kernel parameters were too large.  

"To resolve this issue, we decreased semmnu and semume to half of their value."

[donna hofmeister]

perhaps it would be good to ask what changed?  was the kernel recently modified?  were kernel parms changed?  was software added?

[Steve Reece_3]

I agree Donna - that's my first port of call.  Unfortunately, I don't know the answer I'm afraid.