PROBLEM
An attempt to generate a new kernel resulted in some "unsatisfied symbol"
error messages. The symbols were:
o pwrite
o pread
o lock_claim
o mlock_valid_args
o lock_disown
How can this problem be resolved?
CONFIGURATION
Operating System - HP-UX
Subsystem - System Administration
RESOLUTION
In this instance, the first two symbols - pwrite and pread - were
resolved by reloading patch: PHKL_22589
Note: If patch
PHKL_22589
has been installed, then
PHKL_18543
cannot be reloaded afterwards. Doing so will result in a
kernel gen failing with errors about the two unsatisfied
symbols referenced above.
The other symbols were found in other objects:
o lock_claim
This symbol was found in the lv_hp.o object in the liblvm.a
library. That object is changed by patch:
PHKL_23127
o mlock_valid_args
This symbol was found in vm_clic.o in /usr/conf/lib/libhp-ux.a.
PHKL_23183 changed this object.
o lock_disown
Same as "lock_claim" above.
Reloading these patches, and insuring that all the dependencies were
loaded as well, resolved the problem.
Some of the steps used to find out the location of the above symbols were:
1. Change directory to the directory that contains the libraries
used to generate a kernel:
# cd /usr/conf/lib
2. Use nm(1) to check the libraries for the symbol:
# nm *.a | grep lock_claim
3. If the symbol is found, then use nm(1) to find exactly which
library contains the symbol. After some trial and error,
this symbol is found in the liblvm.a library.
# nm liblvm.a | grep lock_claim
# nm liblvm.a | grep lock_disown
4. Next, use nm(1) to look at the library and find which object
in that library defines that symbol.
# nm liblvm.a | pg
Then search for lock_claim and lock_disown. It found them in
the lv_hp.o object.
5. Next, pull the object from the library using ar(1);
# ar x liblvm.a lv_hp.o
NOTE: This will not change the library. This will put the
lv_hp.o, or the object that was specified with the above
ar command - into the current directory.
6. Use what(1) to get information about the object. If a patch
has changed that object, then, usually, the what(1) command
will report that:
# what lv_hp.o
In this example, it reported that lv_hp.c was from patch
PHKL_22266
Therefore, that patch was checked in the patch catalog and found
to have been replaced by a later patch -
PHKL_23127
Reloading that patch resolved the problem with the unsatisfied
symbols.
