mk_kernel fails on 11i system after patch installs

[Gram Ludlow]

I'm trying to update an HPUX11i system. I installed the December 2003 patch bundles, and was in the process of installing other various security patches (via the patch check tool). but I cannot install any kernel filesets because mk_kernel fails. Here is the error:

# mk_kernel
Generating module: krm...
Generating module: rng...
Compiling /stand/build/conf.c...
Loading the kernel...
ld: Unsatisfied symbol "fss_find_any" in file /usr/conf/lib/libpset.a[pm_pset_swtch_epncf.o]
ld: Unsatisfied symbol "fss_maxgrp" in file /usr/conf/lib/libpset.a[pm_pset_balance_epncf.o]
ld: Unsatisfied symbol "fss_debt_toggle" in file /usr/conf/lib/libpset.a[pm_pset_balance_epncf.o]
3 errors.
*** Error exit code 1

I can't find a reference to this anywhere. I tried backing out the patches, but there are so many dependencies that I reasonably can't.

I'd not like to have to start from scratch again. Is there anything I can do?

[RAC_1]

Try kernel rebuilding through SAM.

Anil

[Dietmar Konermann · Accepted solution]

These symbols come with PHKL24257. So installing PHKL_30033 (which is the latest replacement) should fix that problem.

Best regard...
Dietmar.

[Gram Ludlow]

I got an error trying to rebuild the kernbel through SAM, something like "Exitied on error(1)"

[Gram Ludlow]

I got an error trying to rebuild the kernbel through SAM, something like "Exited on error(1)"

[Gram Ludlow]

I already had that patch installed. I'm going to remove it, and then mk_kernel, and then re-install it and see what happens! Thanks!

[MarkSyder]

Before you do that, could I recommend that you copy your most recent working vmunix to a safe name: e.g. /stand/vmunix.works

Mark Syder (like the drink but spelt different)

[Gram Ludlow]

It was indeed that patch that was causing the problem. For some reason, it will not install, then hangs up future kernel depot installations.

I'll proceed without installing that patch. I don't know if there is a prereq. that isn't installed (and improperly not detected), a bad download, or a bad patch bundle (very unlikely).
thanks for helping me track it down!

[Dietmar Konermann]

Gram,

hmm... with that patch being properly installed you should *not* get that errors. Please check if that patch is really in the libs:

# what /usr/conf/lib/libpm.a | pm_swtch

You should get a version >=PHKL_24257.

Best regards...
Dietmar.

[Dietmar Konermann]

Sorry... forgot the grep:

# what /usr/conf/lib/libpm.a | grep pm_swtch

[Gram Ludlow]

# what /usr/conf/lib/libpm.a | grep pm_swtch
pm_swtch.c $Date: 2002/05/16 11:07:30 $Revision: r11.11/9 PATCH_11.11 (PHKL_27091)

That's what I'm getting. Hmm, I think that is a preliminary patch for a problem in tftpd. I'll try roling that back yet, and see if I can then install the newer patch.

[Gram Ludlow]

Nope... no good. No matter how hard I try, I acnnot get PHKL_30032,33,34,35 and 36 to compile. They always fail with the above message!

[Eric Herberholz]

FYI: "fss_find_any", "fss_maxgrp", and "fss_debt_toggle" are in PHKL_27091, which has been superseded by PHKL_30033, which has the following dependencies:

PHKL_27093 PHKL_27094 PHKL_27093 PHKL_27094 PHKL_30032 PHKL_30034 PHKL_30035 PHKL_30036

Which have the following dependencies:
PHKL_25729 PHKL_29704 PHKL_30033

Do you have all of these patches either installed or in the bundle from which you are installing?

[Pamela Glueckstein]

I was having this same problem. It appears that if you have the Processor Sets product installed, PHKL_30032,33,34,35, and 36 have an "other dependency" on PHKL_30037.

Once PHKL_30037 was installed, 30032-36 went on without error.

[Eric Herberholz]

I had yet another customer who had these three symbols unsatisfied. This customer's problem was resolved by adding prm to the system file and then the mk_kernel worked successfully.

THE FOLLOWING IS JUST CONJECTURE AT THIS TIME: I'm suspecting that the removal of PRM may be removing the "prm" from the kernel, but then if the customer still wants to use PSETS, they will need to put the "prm" driver back into the kernel.

[McKesson SystemCare UNI]

Thanks for posting this fix! It seems obscure, but, putting 'prm' into my kernel allowed me to compile a new version.