kmtune problem

[Richard Allen]

I have a L2000-44 running 11iV1 (HP-UX 11.11) and kmtune is giving me problems.

root@tuska:/->kmtune -q nflocks
kmtune: Cannot read number of current kernel parameters.
Parameter Current Dyn Planned Module Version
===============================================================================
nflocks - - 4096

It does not seem to be able to read the current value of any kernel parameters.

I have another machine thats Identical and all is well there.

root@strokkur:/->kmtune -q nflocks
Parameter Current Dyn Planned Module Version
===============================================================================
nflocks 4096 - 4096

Anyone seen this before ?

[Sameer_Nirmal]

Hi,

I haven't seen this before, but it's interesting problem.

The "current" value of a kernel parameter is queried from the running kernel. Apprently there is a problem (something broke in between to read the kernel structure) causing kmtune to flash that message.

You can try using "adb" as
# echo 'boot_string/S' | adb /stand/vmunix /dev/mem
This will show you the kernel you are booted from.
Now try to pull out the kernel parameter value using
# echo nflocks/D | adb /stand/vmunix /dev/mem

Check the kernel patch level (PHKL*) using
# what /stand/vmunix

If all looks OK, then I guess a reboot would cleared out the broken links and kmtune would work.

[Richard Allen]

No, rebooting does not help the problem.

However, adb seems to work fine.

root@tuska:/->echo 'boot_string/S' | adb /stand/vmunix /dev/mem
boot_string:
boot_string: disk(0/0/2/0.2.0.0.0.0.0;0)/stand/vmunix
root@tuska:/->echo nflocks/D | adb /stand/vmunix /dev/mem
nflocks:
nflocks: 4096

[Geoff Wild]

What it displayed when you run kmtune all by itself?

Rgds...Geoff

[Richard Allen]

# kmtune
kmtune: Cannot read number of current kernel parameters.
Parameter Current Dyn Planned Module Version
===============================================================================
NSTRBLKSCHED - - 2
NSTREVENT - - 50
NSTRPUSH - - 16
NSTRSCHED - - 0
STRCTLSZ - - 1024
STRMSGSZ - - 65535
[snip]

[Richard Allen]

I just installed a rather large patchbundle (GOLD patches) with no change :(

[Sameer_Nirmal]

Hi,

As adb works and I guess "sysdef" would work as well.

What you see in
# ll /usr/sbin/kmtune
# what /usr/sbin/kmtune

"kmtune" use gettune() and tuneinfo() functions to get the current values from running kernel. Check for header files in /usr/include/sys
types.h and dyntune.h

[Steven E. Protter]

Shalom Richard,

Your system file is corrupted, or perhaps your /stand filesystem is so close to fill it can't operate properly.

I'd look carefully at the file and consider restring the /stand fileystem.

SEP

[Richard Allen]

sysdef works fine.

root@tuska:/->ll /usr/sbin/kmtune
-r-xr-xr-x 1 bin bin 40960 Mar 26 2002 /usr/sbin/kmtune*
root@tuska:/->what /usr/sbin/kmtune
/usr/sbin/kmtune:
kmtune.c $Date: 2002/02/08 16:47:42 $Revision: r11.11/3 PATCH_11.11 (PHCO_26061)
$Revision: @(#) kmtune CUP11.11_BL2002_0325_17 PATCH_11.11 PHCO_26061
Mon Mar 25 19:14:52 PST 2002 $

This is identical output as from my other L2000 machine.

root@tuska:/->cksum /usr/include/sys/types.h
925851039 14104 /usr/include/sys/types.h
root@tuska:/->cksum /usr/include/sys/dyntune.h
1008158078 3020 /usr/include/sys/dyntune.h

Again, same files as on my other L2000 where everything works.

The /stand/system file looked OK but just to be sure, I copied the file from my other L2000, did a "mk_kernel -o /stand/vmunix" and the a reboot. No change.

I have however noticed the following in the dmesg output on the machine:

Starting the STREAMS daemons-phase 2
$Revision: vmunix: vw: -proj selectors: CUPI80_BL200
0_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000
_1108' Wed Nov 8 19:24:56 PST 2000 $KRS error 11 during initialization of dyna
mic tunables.
gettune(), settune(), and tuneinfo() cannot be supported.

Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 3145728 Kbytes, lockable: 2377336 Kbytes, available: 2734532 Kbyte
s

See that error 11 ? Strange.

[Steven Roth]

Richard,

The boot time error message you quoted indicates that the kernel registry database is corrupt. (That's where dynamic tunable information is stored.) No one has ever reported a problem like this to us before.

In order to solve this problem, it would be useful to understand the corruption better. I've attached a program that will print the contents of your kernel registry database. If you would be kind enough to send me (steve.roth at hp.com) its output, we can then figure out how best to resolve the issue.

Steve Roth
HP-UX Kernel Configuration

[Steven Roth · Accepted solution]

Richard sent me the information I requested, and we found the problem. In case anyone else is interested: the registry corruption occurs when root is using a non-default locale and is using Bourne shell (or any shell in which the 'date' command is not a builtin). Under these circumstances the timestamp string in the registry can be longer than the space allotted for it. The defect has been reported to the responsible team in HP (SR #8606433957).