Fail to rebuild the kernel

[Jeffrey Li]

After having an incomplete install for a driver and remove it, I fail to rebuild a kernel on HP-UX 11.00 N-class system. Here is the error output.

# mk_kernel -o /stand/vmunix -s /stand/system
Generating module: krm...
Compiling /stand/build/conf.c...
Loading the kernel...
ld: I/O error, file "xport_diag.o": Invalid argument
Fatal error.
*** Error exit code 1

Stop.
config: make did an exit(1)

I need your guys help.

Thanks,

Jeff
10/20

[Bill Hassell]

The I/O error may be due to a problem on the root disk in the /stand volume. Try running the command:

dd if=/dev/vg00/lvol1 of=/dev/null bs=32k

and see if an error is reported. If so, the disk has a bad spot and you'll need to plan on replacing the disk. As it is in vg00, start with a full backup of vg00 files, then install Ignite/UX and create a backup with make_recovery or make_net_recovery.

[wyan lowe]

had a similar sounding problem -
hp support recommended a networking patch
that contained a good version of "libhp-ux.a" (something like that)
that contained all the .o files...

installed the patch: phne_19936 (had a 10.20 machine)

was then able to recompile the kernel,
but when trying to mirror the vg00, got stale problems

more than likely, it's a bad spot on the disk....
will have to replace sometime

[Jeffrey Li]

Thank you, Bill.

I follow your instruction but no error is reported. The disk is good. By the way I still
can reboot the system using the current kernel.

I don't have any idea about that.

[Victor BERRIDGE]

Hi Jeffrey
Im surprised by your procedure...
Have you tried to compile your kernel the safest way => using sam?
If its because you want to modify with vi, why arent you in /stand/build?
This is how I do it:
cd /stand/build
/usr/lbin/sysadm/system_prep -s system
vi system # you customize what needed
/usr/sbin/mk_kernel -s system
mv /stand/vmunix /stand/vmunix.YYMMDD
mv /stand/system /stand/system.YYMMDD
mv vmunix_test /stand/vmunix
mv system /stand/system

Then reboot...
lets say it was to add a new driver:
strings /stand/vmunix| grep new_driver

I would say that before compiling a new kernel you should be shure you have a backup one ready...

[Jeffrey Li]

Thank you, Wyan and Victor.

Wyan may be right. I review the previous posts that reply Ami Hofman's question. I run chuck_patches command and read its output file in /tmp/check_patches.report. The patch PHKL_18543.CORE2-KRN (HPUX 11.00) object module, /usr/conf/lib/libhp-ux.a(all of .o files), cksum values don't match. I is requested to reinstall the patch using the option ' -x reinstall=true'. But I still fail to reinstall the patch with the same compiling error, because the reinstallation of the PHKL patch need to build a new kernel.

I send an Email to HP Tech and hope them to fix it.

[Devbinder Singh Marway]

What you can try is commenting out the DBGS line in /usr/conf/gen.config.sys . In here you should see xport_diag.o . Then re-generate the kernel and if successful , uncomment the line back agin . I believe the DBGS is for debugging.

[Rita C Workman]

If you are feeling your problem may be similar to Ami's - I am wondering if it is the same instance that I had (by the way Ami never responded...so I hope he got his fixed), and I got mine fixed.

My kernel problem occurred because somehow (I have no idea how) I managed to install the PHKL_18543 patch twice. And somehow this little beauty of a patch overwrote the object files of about 30 other patches. I had to first check and see what patches were installed and which were just configured. Than I ran swconfig to get these installed....still had a mess....Finally ran the check_patches and sent the report to HP for review and they came back with a list of patches that had to be re-downloaded (all 30+ of them), put all these into 1 depot and install them. It was a pain, cause I had to dig around to find all the patches I needed, but find them I did.
Then, it was after all this that the kernel built and works...
I highly recommend running the check_patches and sending it to HP, cause it does sound to me like that is what has happened (your object files have been overwritten and gotten out of 'sync')...

Regards and hope the best for ya !!

[Jeffrey Li]

I run the check_patches command and sent /tmp/check_patches.report to HP support guy. He gave me a list of patches that need to be reinstalled.

After reinstall PHKL_18543 and thr other 42 patches, the system recover now. :-)