Remove Patches

[Sanjay Tailor]

Hello,

I would like to remove a Kernel patch(S) that I installed. If I use swremove will that automatically reconfigure the kernel and reboot the system?

I had run into a problem when installing General release (Dec 2000) patches. What eventually happened was that I ended up restoring my old kernel from backup. (The new kernel could not be made.) But when I check swlist -product PH* it shows me that the kernel patches were installed. I don't think they are in the kernel. My idea is to remove the patches and begin again. Is that wise to do?

Here is what happened:
1) I was installing the December General Release disk. The analysis had gone fine and was in the middle of installing patches. I got a I/O error (5) which said it could not copy a file for a kernel patch from the CD.

2) Called HP RC. They made me exit out of swinstall and try and load the June 2000 GR CD.
They instructed me to change options in the swinstall. This seemed to create a lot of error in the swagent.log file. I was forwarded to another CE who instructed me to continue loading patches from the June 2000 cd. I did so, but when it started to reconfigure the kernel, it said it had unsatisfied symbols. The CE said I need a patch for that. I loaded that patch (PHKL_23174) which caused error also. The CE said to go on. When the kernel was being built I got the following errors:

NOTE: Building a new kernel based on template file "/stand/system"
Compiling /stand/build/conf.c...
Loading the kernel...
/usr/ccs/bin/ld: Duplicate symbol "st_ats_enabled" in files /stand/build/conf.o
and /usr/conf/lib/libhp-ux.a(scsi_tape.o)
/usr/ccs/bin/ld: Found 1 duplicate symbol(s)
/usr/ccs/bin/ld: (Warning) Linker features were used that may not be supported i
n future releases. The +vallcompatwarnings option can be used to display more de
tails, 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)
config failure.
ERROR: The command "/usr/sbin/mk_kernel", which is used to rebuild
the kernel, has failed. Because kernel-related filesets were
installed, this command must be executed by "swinstall",
without failures, before the load can continue. Check the
above output for details about the failure.
NOTE: The Install Phase has suspended. Check the above output for
reasons.


* Aborting the Install Phase.

======= 03/17/01 15:00:39 CST END install AGENT SESSION (Aborted)
(pid=12409) (jobid=u002-0071)


======= 03/17/01 15:00:41 CST BEGIN install AGENT SESSION (pid=12625)
(jobid=u002-0071)

* Agent session started for user "root@u002.books.uic.edu".
(pid=12625)

======= 03/17/01 15:00:49 CST END install AGENT SESSION (Cancelled)
(pid=12625) (jobid=u002-0071)

#


We also found that the /stand was undersized and needs to be extended. At this point the CE said that my main concern was to expand the /stand dir. Not an easy task. He sadi it would be Ok to restore the old kernel from then. I did that. What I am worried about is: What is the state of my kernel? Will I be able to reconfigure it?

I tried the swlist -l fileset -a state

Many of them came back configured but some came back installed and 1 came back corrupt (PHKL_20850).

How would I use swconfig to fix this problem. Will bring my system back up to the level of patching that I have.
If I use swconfig, will it recongifure the kernel and reboot? At this point I am not sure of the state of my kernel. Whether I can reconfigure it and get a new kernel or not.

Any help is appreciated.

Thanks,

Sanjay

[James R. Ferguson]

Hi:

To remove a kernel patch, you can do the following:

# swremove -x autoreboot=true PHKL_xxxxx

This should cause the kernel to be regenerated sucessfully assuming that the patch that you are removing is the one that caused the problem in the first place.

...JRF...

[Printaporn_1]

Hi,

May be problem cause you're reinstall PHKL_18543 that will make mk_kernel file with unsatisfy symbol.
about /stand full this is because lot of files generate in /stand/build and when kernel compilation fail , the files will left there.
then you can remove files in /stand/build before next kernel compilation.