kernel build exitcode 71

[Ami Hofman]

i modified some kernel parameters, i then
tired to build a new kernel from sam and
what i got is something like :

make returned exitcode 71
cannot build kernel with /usr/sbin/config

what should i do to compile those kernel changes???

[Stefan Farrelly]

On your system the transaction-links are _not_ installed, and SAM expects to find make in /usr/bin.

Install a softlink from /usr/ccs/bin/make to /usr/bin/make and it should work.

[CHRIS_ANORUO]

Do a cd /usr/bin;
then "ln -s /usr/ccs/bin/make make"
Try the kernel build again.

[Ami Hofman]

the link is there and it still doesn't work.
i made kernel changes before and it all went
well until today.
the exact message is :
Cannot build a kernel using /usr/sbin/config
The standard output of the command is shown:

Stop.
config: make did an exit(1)

The command exitted with exitcode _71

i'm doing every thing from within sam so
what happened ????

[Victor BERRIDGE]

There is something I didnt understand:
You modified some kernel parameters (using vi I presume) THEN used sam to build a new kernel?
Is that so?
If so this could be the reason, because sam if I remember right does some coherence check before building a new kernel...

[CHRIS_ANORUO]

Are you super-user (root)? Check if /usr/conf directory is owned by bin with bin as the group also.
You have to be root to build the kernel.

[Ami Hofman]

sure guys i'm not that crazy.
i'm in super user mode.
and no i don't make the changes with vi and
then activate sam.
all the process from the begining to the end
is done from sam :
sam => Kernel Configuration =>
Configurable Parameters
make the changes and then :
Action => Process New Kernel

i have done it before a zilion times and
nothing went wrong.
this is the first time i get the error
message and i done it exactly as before.

[Victor BERRIDGE]

We are only trying to help you...
This may sound silly but last week on a aix box I found myself in almost the same situation: I have been called because the system backup could no more be done, It took me 2 days to realize that the message on building a new bootable kernel failed on a strip function call, you know what it was?
Some guy (?) made an ll>unix
So the error ...
No joke!
So I you know look on your system if you had a good system.prev file to move in /stand/build
rename to system
/usr/sbin/mk_kernel -S system
and see if it works till here
then try
/usr/lbin/sysadm/system_prep -s system
and again
/usr/sbin/mk_kernel -S system

[CHRIS_ANORUO]

DOWNLOAD AND INSTALL THESE KERNEL PATCHES PHKL_14013 AND PHKL_17060 WITH THEIR DEPENDENCIES OR THE LATEST KERNEL PATCH.

[Cheryl Griffin]

Ami,
Check for extra files in /stand/build:
*.o files and any conf* files, system.SAM conf.SAM.c (and potentially vmunix_test) can be removed.

[Ami Hofman]

sorry for the last one, your help
is greatly appreciated.
it failed after mk_kernel s system
the exact output was :

Generating module: krm...
Compiling conf.c...
Loading the 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]
ld: Unsatisfied symbol "wsio_get_service" in file /usr/conf/lib/libpci.a[superio_centif.o]
3 errors.
*** Error exit code 1

Stop.
config: make did an exit(1)

i didn't mention before that i am doing
that on a j5000 running hpux 11.0

thanks

[Cheryl Griffin]

Ami,

Missing symbols means you missing some patch dependencies. One sec and I will find the appropriate patches....

[Cheryl Griffin]

Ami,

pwrite is defined in sys_gen.o that comes from PHKL_18543.

Check for these patches. This list includes all dependencies and are the most current. If that goes against your patch strategy, you could check the patch catalog for previous versions. The two important patches for pwrite and pread are PHKL_18543 and PHKL_20349.

PHKL_18543 PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20016 2nd CPU not recognized in G70/H70/I70
PHKL_20674 fix VxFS unmount hang & MMF, sync panics
PHCO_20882 fsck_vxfs(1M) cumulative patch
PHCO_21187 cumulative SAM/ObAM patch
PHKL_21392 VxFS performance, hang, icache DPFs
PHKL_21532 boot,JFS,IOperf,PA8600,3Gdata,NFS,IDS,PM,VM

Still searching for the fix for wsio_get_service.

[Cheryl Griffin]

The message stated "ld: Unsatisfied symbol "wsio_get_service" in file /usr/conf/lib/libpci.a/"

Patch: PHKL_21276 Superio Parallel driver fixes contains /usr/conf/lib/libpci.a(superio_centif.o).

It has no other patch dependencies.

[Ami Hofman]

i can't even install the pathces, the
swinstall session aborts and agian the
log file says the same error message as
before.
i'm lost what can i to get out of
that loop.

[Stefan Farrelly]

your stuffed. no matter how much you try to 'patch' the kernel source I doubt you will manage to even build a kernel at all now. Ive been in this situation before, only 2 ways to resolve;
1. mv /usr/conf /usr/conf.old and copy over from another similar system (hardware model and OS and patch level if possible) all of /usr/conf then try to build a kernel, it should work. If you have cloned systems as we do then it will work.
2. restore /usr/conf from a previous backup. Then you should be able to build a kernel successfully (may have to try a few backups).
Once you manage to get the kernel build working then you should reapply the latest patch bundle (XSWGRxxSxx) and may have to reinstall any apps that require kernel rebuilds (Digas, OnlineJFS, lan cards etc.)

Only other option is to completely rebuild the server! The above method has worked for me many times, saves a complete rebuild.

[Ami Hofman]

hi,
i tried to copy /usr/conf from another
machine (same model,os and patch level)
and tired to restore /usr/conf
i tried several versions but i'm sorry
to say nothing worked, i still
get the same error message while
trying to compile the kernel.
is there any thing else that i can do
beside reinstall os all over again.

[Stefan Farrelly]

as well as copying /usr/conf also copy /stand/* (but not vmunix). If /usr/conf didnt work then the problem probably lies in a file under /stand.

I hope this works. If not your facing a restore (of /usr/conf and /stand from an old backup) or else a complete reinstall.

[Vincente Fernandes]

I suggest to boot from "/stand/vmunix.prev".
copy /stand/vmunix.prev /stand/vmunix.
Boot from /stand/vmunix, make the kernel changes and try to rebuild the kernel by running "mk_kernel". If the build is successful then it will create a binary named "vmunix_test" in the "/stand/build" dir. For more details refer to man page "mk_kernel". Hope this helps

[DAVID NEWELL]

Ami,

If you are still getting the error message about unsatisfied symbols only when you try to regen a new kernel.
Load patch PHKL_20349 which will put them back into the system.
Has a call like this recently and this resolved the issue. The mk_kernel the patch generated worked once they were reloaded.

[Rita C Workman]

Ami,
Have you gotten this fixed yet...????

Please let me know, as I am having exact same error .... I have gotten it to build a new kernel (no errors when it builds finally).... but it won't boot from it. It just keep panicking and rebooting itself...

Let me know (rworkman@wvbep.org)
Thanks,

[Mark Mitchell]

If you are using 11.0, can you try and back out the build and load the old kernel. 11.0 should have already backed it up for you. And I would wait on the Patches. If you are using hfs, you don't need them and some of them touch way too much. I try to avoid the shotgun approach when it comes to patches. So what parameters were you changing?

[Rita C Workman]

I've tried that...didn't help.
I can get it to build a new kernel now (without errors..) but the new kernel will not boot up right. Just panics and reboots until interupted, then I go back to my old "good kernel" to reboot.
I was just trying to load the 6/00 patch bundle to bring the old box more current when I hit this...No changes to parms; just patch upgrade.
**************
On bootable/older vmunix. I get Warning: Could not open Kernel Symbol Table...but it does boot up.
On bad vmunix..(goes too fast to catch it all..) I saw System Panic: Out of Kernel Virtual Space....
I'm open to any suggestions.....tx

[Rita C Workman]

Ami,
Don't know what your resolution to this has been....but even though I could get it to create a kernel...the kernel (vmunix) is makes is un-bootable.
I am looking at re-igniting the box.

Regards,

[Rita C Workman]

Ami...I hope you read this...It's fixed. I actually got it repaired.
Can't say for sure if it's the same problem you have but here's how the final resolution came about.
Worked with HP Tech (Eric Herberholz...My Hero !!)
First we checked and found some patches installed but not configured so I ran
swconfig *....still no good.
He had me run check_patches command which creates a report in /tmp/check_patches.report.
I sent him this file..and he along with an engineer (?? My nameless Hero !) discovered that a patch PHKL_18543 had been installed twice. Well they sent me a list of 34 kernel patches that had their object overwritten by the older version of this patch.
I just hated to have to re-ignite this box and have to start over...
So I downloaded all 34 patches....(even the one recalled patch)..and I loaded all of them into one depot...I turned on both re-installation options and let it rip....
It seemed to take forever...but I had nothing to lose here....
And it worked ! My kernel rebuilt and is totally bootable....
I'm walking on clouds now...!!!
Regards - and I hope this helps ya !!