swinstall Proceed at your own risk!

[Ovidiu D. Raita]

Hi Bill,

I don't have a real clue I would only try to guess ....

Are 100% sure that the depot is not corrupted somehow. Have you tried a checksum on the L2k and A500? Do they match?

If the depot is not corrupted (I hope it is) then the script that comes with the patch might be buggy. You could try to set to false all enforce_script enforce_dependecies options.

Do you have any new core dump on the system? You could then find out which exec failed.If that exec does just a verification you could replace it with an "exit 0" script. I would do that only on a sandbox unless you want to "Proceed at your own risk!"

Regards,
Ovidiu

[Alan Riggs]

Bill, have you checked the state of PHKL_18543 and all of its filesets?

[Bill McNAMARA_1]

I'm not sure it's that..

The system is just randomly panicing at least twice a day.. I must have a hw failure somewhere.
Attached is a pdcinfo output.

# swverify PHKL_18543

======= 08/28/01 18:01:20 METDST BEGIN swverify SESSION
(non-interactive)

* Session started for user "root@kibo".

* Beginning Selection
* Target connection succeeded for "kibo:/".
* Software selections:
PHKL_18543.C-INC,l=/,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fa=HP-UX_B.11.00_32/64
PHKL_18543.CORE-KRN,l=/,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fa=HP-UX_B.11.00_32/64
PHKL_18543.CORE2-KRN,l=/,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fa=HP-UX_B.11.00_64
PHKL_18543.KERN2-RUN,l=/,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fa=HP-UX_B.11.00_64
PHKL_18543.VXFS-BASE-KRN,l=/,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fa=HP-UX_B.11.00_64
PHKL_18543.VXFS-PRG,l=/,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fa=HP-UX_B.11.00_32/64
* Selection succeeded.


* Beginning Analysis
* Session selections have been saved in the file
"/.sw/sessions/swverify.last".
* The analysis phase succeeded for "kibo:/".
* Verification succeeded.


NOTE: More information may be found in the agent logfile (location
is kibo:/var/adm/sw/swagent.log).

======= 08/28/01 18:01:25 METDST END swverify SESSION
(non-interactive)

[Bill McNAMARA_1]

I kinda doubt it's fully h/w problem (I've got uncommon lab prototype h/w installed!) because as mentioned installing the patch on the L2k fixed the exact same pim output. I'm sure this patch will fix the A, but just can't install it.

points will come!..

Later,
Bill

[Paula J Frazer-Campbell · Accepted solution]

Hi Bill

Have you tried making a change to kernel and doing a rebuild, and see if the panic goes away?

Paula

[Bill McNAMARA_1]

I'm going to allow the system to stay running after modifying the kernel, rebooting installing, by Proceeding at my own risk and rebooting.. if it panics again, I'll just reinstall everything...

I'll let you know..

Later,
Bill