topic Re: Error loading Kernel in Operating System - HP-UX

Error loading Kernel

Manuel Guerrero — Fri, 16 Nov 2001 19:58:58 GMT

Hi:
During the installation of patch " PHKL_18543 " in the stage to load the " Kernel " it has given the following error me, " unsatisfied " pwrite " in cases out usr/conf/lib/libhp_ux.a[scall_stubs.oj ] ". Thanks

Re: Error loading Kernel

someone_4 — Fri, 16 Nov 2001 20:01:48 GMT

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.

Re: Error loading Kernel

Sanjay_6 — Fri, 16 Nov 2001 20:05:40 GMT

Hi Manuel,

Take a look at the thread below,

http://itrc.hp.com/cki/bin/doc.pl/sid=0b0b83861c0db078cf/screen=ckiSearchResults?mode=id&searchString=KBRC00000862

Hope this helps.

Regds

Re: Error loading Kernel

Michael Tully — Fri, 16 Nov 2001 20:06:51 GMT

Hi,

Did you try to re-load this patch from a patch bundle?? This is the patch from hell. I hope that this is a fresh installation of the system. If not you may have to break out your ignite tape(s)

-Michael

Re: Error loading Kernel

Jim Turner — Fri, 16 Nov 2001 20:10:27 GMT

Please don't say you were trying to *reinstall* PHKL_18543 . . .

Never, ever, ever reinstall PHKL_18543. It is a "Line In The Sand" (LITS) patch upon which countless subsequent kernel patches are baselined. If that's what you did, you're really pooched. See the attached file for instructions on recovering, and I hope you've got a few days of (formerly) free time on your hands.

If this error isn't the result of reinstalling PHKL_18543, reinstalling patch PHKL_25475 should clear the unsatisfied pwrite symbol error. Make sure you set swinstall options for reinstall fileset=ON, auto-select dependencies=OFF, and enforce scripts=OFF when you do the reinstall.

Cheers,
Jim

Re: Error loading Kernel

someone_4 — Fri, 16 Nov 2001 20:11:03 GMT

Why is this patch so difficult?
I am thinking I jumped the gun by throwing that doc up ther.e

Re: Error loading Kernel

someone_4 — Fri, 16 Nov 2001 20:12:10 GMT

Unsatisfied symbols pwrite/pread DocId: KBRC00003820 Updated: 8/31/00 9:55:00 AM

PROBLEM
Having the following error messages while building a kernel:
ld:unsatisfied symbol "pwrite" in file /usr/conf/lib/libhp-ux.a [scall_stubs.o]
ld:unsatisfied symbol "pread" in file /usr/conf/lib/libhp-ux.a [scall_stubs.o]
RESOLUTION
This is normally caused by a resinstall of PHKL_18543 which should
not be done! To solve these unsatisfied symbols you should reinstall
the PHKL_20349 patch:

1) Start swinstall without any other arguments (it will get up in
interactive mode).
2) After selecting the depot containing the patch PHKL_20349, edit the
following options:
* Reinstall fileset ... ON
* Auto-select dependcies ... OFF
* Enforce scripts ... OFF
3) Select just the patch PHKL_20349.
4) Run analysis phase.
5) Do the final install.

NOTE: Our labs update HP-UX patches as necessary; therefore you may not
find the versions of patches as noted above.

If you do not know how to determine the latest versions for an HP-UX patch,
work with your local Country Response Center to obtain the proper patches.

Re: Error loading Kernel

someone_4 — Fri, 16 Nov 2001 20:17:35 GMT

I just saw your post there Jim ..
ANd you have the same steps that I found. But mine is old and PHKL_25475 is the right patch. acording to the docs.

Richard

Re: Error loading Kernel

Rita C Workman — Fri, 16 Nov 2001 20:26:58 GMT

Hi Manuel,

There are links I could send you to...but...
As Jim Turner (hey buddy) mentioned this is a problem patch; and a known issue with HP. I myself (yes I hate to admit it..) hosed a small system with this little stinker.
May I suggest, since HP is well aware of this issue, that you place a call to HP Tech Support and they will probably have you run a patch list and send to them to evaluate. They can then advise you which patches you need to install in one depot to run and get your kernel back in line. [For me, my box was so hosed it took just over 30 patches in one depot...I hear it's around 6 or 7 patches now....but it was fixed and the kernel built]

Hope this helps...
Rit