Can't build kernel from SAM

[Albert Chen]

Hi, I am trying to build a new kernel through SAM on a new HP-UX 11.00 9000/800, and it constantly fails with the following error:

UNEXPECTED EXIT: process LANG=C LC_ALL=C /usr/sam/lbin/samx -C -p 1589 -s kc_sa_param /usr/sam/lib//kc.uui exited with a non-zero exit status.

sh: 3369 Memory fault

The path for kc.uui seems strange to me. The only parameters I have changed are max_thread_proc and nkthread. Any help appreciated, thanks.

[Rita C Workman]

It looks like the problem may be with SAM...

Try running swlist -l fileset -a state | more to make sure that all the patches are configured.
If you find something isn't swconfig

Just a thought,

[Darrel Louis]

Albert,

It could be that if this is a Ignited system you have two SAM patch versions on your system.
Check with "show_patches -as".
The swlist -l fileset -a state, might show the installed state of one of the patches.
It could be that your experiencing the problem fix described in the latetst SAM patch, if so, follow the instructions of the latest SAM patch.

[Kofi ARTHIABAH]

While you are checking for patch updates, if this is urgent, you might want to consider using the procedure for manually generating the kernel as outlined in pages 30 and 31 of the System Administrator Tasks : http://docs.hp.com/hpux/pdf/B2355-90672.pdf

good luck

[Steffi Jones_1]

Hi Albert,

this looks more like a sam issue than a kernel issue.
Check if you have a sam patch installed and if the patch is configured.
run swlist -l fileset -a state | grep -i sam

if it says installed and not configured on the right hand site, run swconfig PH...

You can regen a kernel manually with the mk_kernel command:

mk_kernel -s /stand/system
mv /stand/build/vmunix_test /stand/vmunix
reboot the box

Steffi jones

[Darrel Louis]

Albert,

Have you tried other options within SAM??

Patch description PHCO_21187
The previous patch, PHCO_19047, may fail to configure if installed simultaneously with other SAM-related filesets. The configure script will return a non-zero exit code and the log file /var/adm/sw/swagent.log will
contain the message:
ERROR: This fileset's configure script has called the SAM Task Manager Registration tool. The tools failed to register part of this filesets Task Manager tasks needed by SAM.

PHCO_19047 can be successfully configured by removing it and reinstalling it individually.
At run time, this problem can manifest itself in a number of ways, including such error messages as "tm_parser error", "da_parser error", "SAM internal error", or
"infrastructure error". The corrupted registration database may only affect tasks that are not normally run on the subject system, so that SAM will still run fine.
Due to the ambiguity of the run-time symptoms, it is necessary to check the swagent.log for configure failures.