topic Re: Changed kernel parms not activated in Operating System - HP-UX

Changed kernel parms not activated

Mark van Hassel — Wed, 16 Oct 2002 09:21:08 GMT

Hello,

We've changed some kernel parms on a RP8400 running HPUX 11.i but after the reboot the changes are not activated. SAM shows the old values and kmtune shows the old value as current and the new as planned. We've tried rebooting the system again, changed parameters and rebooted again, but to no avail. Another thing we notice is that 'lanscan' does not give any output.
Anyone experienced this before ?

Any help is appreciated,

Thanks.

Re: Changed kernel parms not activated

Pete Randall — Wed, 16 Oct 2002 09:33:03 GMT

Mark,

I hate to even ask, but did you re-build the kernel?

Pete

Re: Changed kernel parms not activated

Mark van Hassel — Wed, 16 Oct 2002 09:38:37 GMT

That's okay. I (SAM) did rebuilt the kernel. A strings of /stand/vmunix even show the correct new kernel parameters.

Re: Changed kernel parms not activated

T G Manikandan — Wed, 16 Oct 2002 09:45:15 GMT

If lanscan does not show any output how about

#lanscan /stand/vmunix.prev

Probably the lanscan is waiting for the activation of changes of the kernel.

Re: Changed kernel parms not activated

Balaji N — Wed, 16 Oct 2002 09:49:34 GMT

Just a thought.

After changes, did u compile the kernel? A query.

Also, see if there is a new kernel, system file in /stand directory and one .prev file as well.

Sorry if u have already checked them.

Regards
Balaji

Re: Changed kernel parms not activated

Pete Randall — Wed, 16 Oct 2002 09:52:15 GMT

Mark,

How about patches? Searching on just "lanscan" turned up these:
PHNE_26774
PHNE_25338
PHCO_22958

Pete

Re: Changed kernel parms not activated

Mark van Hassel — Wed, 16 Oct 2002 09:57:14 GMT

Thanks for the responses.
Not output from lanscan /stand/vmunix.prev. Kernel was compiled before reboot. It looks as if the correct vmunix file is there (hence the correct parameters that show from strings /stand/vmunix)but it is not activated.

Re: Changed kernel parms not activated

Jean-Louis Phelix — Wed, 16 Oct 2002 10:07:52 GMT

Hello,

Did you check your autoboot file ? Try :

lifcp /dev/rdsk/cxtydz:AUTO -

just to see if you really boot on /stand/vmunix.

Regards,

Jean-Louis.

Re: Changed kernel parms not activated

Telia BackOffice — Wed, 16 Oct 2002 10:12:08 GMT

Stop the boot process.

main -> bo pri
IPL y/n : y

IPL > hpux /stand/vmunix

BR,
Jannik

Re: Changed kernel parms not activated

T G Manikandan — Wed, 16 Oct 2002 10:26:52 GMT

I would recommened a kernel build from the command line.

/usr/lbin/sysadm/system_prep -s /stand/build/system
vi /stand/build/system
Edit the changes
/usr/sbin/mk_kernel -s /stand/build/system
mv /stand/build/system /stand/system
kmupdate /stand/build/vmunix_test
shutdown -r

Revert

Re: Changed kernel parms not activated

Pete Randall — Wed, 16 Oct 2002 10:35:12 GMT

Since a strings /stand/vmunix shows the changes, I doubt that a manually built kernel will be of any help. It really sounds like you're not booting the kernel you think you are, like Jean-Louis was suggesting.

The only other thing I can think of is the kernel parameters you were changing. What parameters were they and what values were you changing them from/to?

Pete

Re: Changed kernel parms not activated

Mark van Hassel — Wed, 16 Oct 2002 10:49:21 GMT

licp shows 'hpux -lq'.

Patches are installed except PHNE_26774 but that is an APA patch and we're not running APA on this system.

I will check if I can reboot the system again today.
The changes paramters are:

maxfiles -> 1536
nflocks -> 1200
ninode -> 16384
nproc -> 5120
max_mem_window ->7

Re: Changed kernel parms not activated

Pete Randall — Wed, 16 Oct 2002 10:58:38 GMT

Mark,

The changed parameters look reasonable enough. I'm not sure about max_mem_window, though. I looked at it in SAM, but there's no min/max info given for it. You're probably reasonably certain that 7 is a valid value, right?

Pete

Re: Changed kernel parms not activated

Joaquin Gil de Vergara — Wed, 16 Oct 2002 11:05:22 GMT

what kernel parameters do you change? static or dinamic?

if you compile a kernel and defer the reboot until you run kmupdate you must move the /stand/build/system.SAM to /stand/system. If not, you have old /stand/system and dinamic parameters will not be applied

Re: Changed kernel parms not activated

Joaquin Gil de Vergara — Wed, 16 Oct 2002 11:06:46 GMT

lanscan

see /etc/mnttab. Probably is corrupt

remove ir and run a mount -a to recreate

try now to run lanscan

Re: Changed kernel parms not activated

Mark van Hassel — Wed, 16 Oct 2002 11:16:17 GMT

The maximum number of memory windows is 8192, so that should not be a problem either.

Re: Changed kernel parms not activated

Mark van Hassel — Thu, 17 Oct 2002 09:02:28 GMT

We've performed T.G.'s procedure and executed 'hpux /stand/vmunix' from ISL but it did not solve the issue.
It's escalated to Hp's Wtec.

Re: Changed kernel parms not activated

Michael Tully — Thu, 17 Oct 2002 09:11:42 GMT

Hi Mark,

One thing I would like to suggest to you is definitely look at the latest firmware for this unit. There is a little nasty fix in it pertaining to system reboots. We had a problem a while ago where the system refused to boot. Might worth be looking at.

Cheers
Michael

Re: Changed kernel parms not activated

Clemens van Everdingen — Thu, 17 Oct 2002 09:34:41 GMT

Hi,

How do you see that the new parms are not activated ?

Because it looks like you booted from a correct /stand/vmunix.

C.

Re: Changed kernel parms not activated

Mark van Hassel — Thu, 17 Oct 2002 09:39:43 GMT

We will look into the formware issue, thanks.

In SAM we still see the old values, kmtune shows the old values as 'current' and the new values as 'planned'. The last and best check is that we cannot create more than 4 memory windows (the old kernel value).