Kernel re-build problem

[Naveen Chenoli]

Hi All

I am getting the following error while trying to rebuild the kernel on a rp4440 running hpux 11.11

# mk_kernel -s system -o vmtest
Generating module: pfil...
Generating module: ipf...
Generating module: krm...
Compiling conf.c...
Generating module: swspBus...
Generating module: hsx...
Generating module: swsp...
Loading the kernel...
ld: Unsatisfied protected symbol "dumpdev_path_change" in file "mod_wk.d/hsx/smo
d.o"
1 errors.
*** Error exit code 1

Stop.
config: make did an exit(1)
#

Any ideas ??

Thanks,

Naveen Chenoli

[Nguyen Anh Tien]

Hi Naveen.
check this link (same your problem)
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=111105


Pay attension on Patches as Santosh saying
HTH
tienna

[Naveen Chenoli]

Hi Tienna,

Thanks for the response.. I checked the link... Its similiar but not exactly what I am getting...

Looks like some other patches is causing the issue,,,

[Mohanasundaram_1]

Hi Naveen,

Good to hear from you after such a long time.

Usually, such problems may have been caused due to an earlier patch installation or some other software installation.

Please let us know why you were rebuilding the kernel. Is the kernel rebuild failing without any modifications too?

Try testing by making a system file from the existing kernel, use system_prep command and then use this system file to create kernel. If this fails, it is clear the problem existed before your activity.

In such a case, check the swagent.log file for any previous installations and errors during them. Also confirm if all your filesets are in configured state.

# swlist -l fileset -a state

And finally, let me know how is life :-)

With regards,
Mohan.

[Naveen Chenoli]

Hi Mohan,

Great to hear from you too...

We are investigating on the possible patch issues..

I am in Qatar now and life is going well...

why dont u send ur contacts to nchenoli@gmail.com ...

Regards,

Naveen

[Steve Steel · Accepted solution]

Hi

Guess you are installing secure path .

Then you have missed patches which are needed - recheck the documants

To enable dump support on EVA devices with path failover,
the following software updates must be installed: PHKL_30219
and PHKL_30218. These two software updates can be installed
in any order. If either software update is not installed,
this new feature is not enabled in your system.




30219 installed this symbol

numbers are now

30219 and 30607


Steve Steel

[Mohanasundaram_1]

Hi Naveen,

Steve is probably correct. your error is on HSX module so it should be secure path for EVA which you are installing.

You need to ensure that all the pre-requisite patches or their later versions are in your system.

Otherwise the securepath installation fails and it is often dicey. Also if your system memory is more than 32GB, then there is a patch to prevent the system from crashing.

I will provide you the list if you require it.

With regards,
Mohan.

[Mohanasundaram_1]

Correction.............
the memory problem is in systems having 8GB or more. Please see the description of the problem.

--------------------------------------------
We have encountered a system crash while installing the Securepath 3.0d on the rp7420 systems. The securepath pre-requisite patches were loaded already.

Upon investigating the crash dump, it was found that sysmap memory fragmentation is causing this problem. Sysmap fragmentation is possible in systems having more than 8GB RAM. The customer systems are with 32GB RAM.

For peope who are interested in knowing more about this problem search for the string "kalloc: out of kernel virtual space" in HP's Knowledge base.

The below patches were loaded to resolve this issue.

PHKL_27094
PHKL_28122
PHKL_29468
PHKL_29696
PHKL_29890
PHKL_30033
PHKL_30034
PHKL_30035
PHKL_30036
PHKL_30044
PHKL_30216
PHKL_30286
PHNE_30367
PHKL_25233
PHKL_25652
PHKL_27096
--------------------------------------------

With regards,
Mohan.

[Naveen Chenoli]

Hi All,

Thanks for the replies...

Steve, you are right.. We just installed those patches 30218 and 30219 and the problem was resolved..

Mohan, Thanks for your inputs as well..

Best regards,

Naveen

[Naveen Chenoli]

The problem has been resolved after installing PHKL_30218 and PHKL_30219