kernel rebuild fails - unsatisfied symbols

[Paul Gold]

hello all

K class running 10.20

after making some parameter changes (usual nfiles nflocks etc) I tried to run mk_kernel and got the following problem

---------
Compiling conf.c...
Loading the kernel...
/usr/ccs/bin/ld: Unsatisfied symbols:
st_ats_enabled (data)

/usr/ccs/bin/ld: (Warning) Linker features were used that may not be supported in future releases. The +vallcompatwarnings option can be used to display more details, and the ld(1) man page contains additional information. This warning can be suppressed with the +vnocompatwarnings option.

*** Error exit code 1

Stop.
config: make did an exit(1)

----------

I then tried

--------------

#find ./ -type f -exec grep -l st_ats_enabled {} \;


./master.d/scsi-tune
./space.h.d/scsi-tune.h
./lib/libhp-ux.a


next step
---------
#what scsi-tune

cant open scsi-tune (26)

#what scsi-tune.h

cant open scsi-tune.h

#what libhp-ux.a

cant open libhp-ux.a (26)


the libraries etc are there and permissions are okay, space on /stand seems okay (two kernels in there already and less than half space used)

I have searched using the help fuction but can find nothing on st_ats_enabled and far too many unrelated with something like libhp-ux.a

any ideas where to go from here, I guess libhpux -a is corrupt but will intalling latest library patch fix it?

regards
Paul Gold
CAST systems

[Stefan Farrelly]

If you kernel fails to build youre in trouble.

First thing to do is try to get back to a working kernel. Did you save your system file before you made changes ? If so restore it, and check if mk_kernel works. If so, great. Something must have been wrong with your changes, recheck them. If not, then your in big trouble. Try creating a new system file from the currently running kernel; /usr/lbin/sysadm/system_prep -v -s system
Then try to build a new kernel from this system file. If it doesnt work something is majorly wrong with your system - something in the kernel build dir (/usr/conf) or in /stand. You may need to recover these from a backup. If you cant get back to the point where your kernel will build your dead.

[Carsten Krege]

It appears as if you have the symbol available in libhpux.a, therefore you should try as a first step to remove the /stand/build directory (where most likely all the object files *.o are in and that might be obsolete, if the objects are in a different directory than /stand/build remove the object files only!) and retry the mk_kernel.

# rm -r /stand/build
# mk_kernel
(# kmupdate # if you want to use this kernel)

If successful this should recreate the build directory and create a build/vmunix_test.

If still unsuccessful you should verify that st_ats_enabled is defined in libhpux.a:

# cd /usr/conf/lib
# nm -x libhpux.a |grep st_ats_enabled

This should give you:
st_ats_enabled |0x400019e8|extern|data |$SHORTDATA$

Carsten

[Paul Gold]

Carsten

thanks

the kernel still did not build after clearing /stand/build

and it seems that st_ats_enabled is not defined in libhp-ux.a

# nm -x libhp-ux.a | grep st_ats_enabled
st_ats_enabled | |undef |data |

does this mean the libhp-ux.a is out of sync with the system, we had a reinstall about 6 weeks ago due to a melted disk, one of the operators restored data after system was rebuilt and mayhave overwritten a library

the system is up and running and reboots okay as I have not tried to move a different kernel in, but I do need to make these parameter changes for our applications to run

thanks

Paul

[Stefan Farrelly]

Yes, it certainly looks like your system is out of sync - ie. some of the files restored arent from the same date+time. You need to get to a point where you can build a kernel first, before you try to make your changes. Follow my advice in my first post to get it working - you may need to restore /usr/conf as well as /stand from a backup from the same date in order to get your kernel to build.

[Carsten Krege · Accepted solution]

Ok, now to the next step. You have the option to go back as Stefan suggests or to go forward. I propose to go forward, as you wouldn't know, how far back you would have to go.

The symbol "st_ats_enabled" is introduced by the stape patch. I recommend to re-install this or the latest stape patch and all its dependencies. The most current patch is PHKL_23790 for HPUX 11.00 (do you run 11.00??).

The most current dependent patches are:

PHKL_18543 PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20016 2nd CPU not recognized in G70/H70/I70
PHCO_21845 cumulative SAM/ObAM patch
PHKL_22589 LOFS, select(), IDS/9000 and umount race fix
PHCO_23651 fsck_vxfs(1M) cumulative patch
PHKL_23790 SCSI Tape (stape) cumulative
PHKL_24027 VxFS 3.1 cumulative patch
PHKL_24116 probe,sysproc,PM,VM,PA-8700 cumulative patch

You should make sure that you (re-)install them all in one swinstall run (you need to swcopy them in one depot)!

Optionally and perhaps easier for you, is to find out the current stape patch that you are using and to reinstall only this one (you should have resolved all the dependencies before).

# swlist -l product PH\* | grep stape
# swinstall -x reinstall=true -x autoreboot=true -s PHKL_XXXXX

In any case, make sure that you read the special installation instruction of the patches and that all dependent patches are installed.

Carsten

[Carsten Krege]

And of course, make a backup before installing patches. :) This is part of any patch installation instruction. Here it is absolutely necessary.

Carsten

[Paul Gold]

Carsten

thanks for all your help

stape was the one causing the problem, as a temporary measure I removed stape from my new kernel build and it compiled with no errors (did have a warning but thats unrelated and I know how to fix that one)

the reason for removal is that I have no stape patches according to swlist, I will be installing the latest bundle at the earliest opportunity

appreciate your help

Paul Gold
CAST systems