vmunix: mem: could not lock:

[DC.]

Hi,

One one of the itanium server rx 4640 with HPUX 11.23 v2 iam getting "vmunix: mem: could not lock:0x40f1fee" errors in syslog. This is something related to memory as it states. But can anyone tell me where to look for and what does this error mean.

thanks

[Bhushan Bumber]

Hi
Please check the memory usage by glance or sar. Also check the nproc and other related kernel parameters. I have faced the sililar situation but it didnt bring the server to crash or halt.You can also check the cstm messages to check if the memory is OK or use command set_fixed -l to check the EMS errors. If any hardware issues then contact HP.Normally a scheduled reboot solves the problem.

[Steven E. Protter]

Shalom,

http://www.hpux.ws/system.perf.sh

kctune
# displays kernel variables.

Analysis. What does the system, do and how new is it. Errors of this type are common on oracle database servers and systems running shared memory software with inadequate shmseg, shmmax and other important tunable's. While installation minimums were probably met they are not always set to real world values.

What bi-annual patch update is installed?

SEP

[whiteknight]

Kuldeep,

it's not a sign of bug. only a sign that someone is accessing /dev/mem.

Did you do anything like crashinfo -v ofiles which open /dev/mem or did anything at the time this message appear



WK

please assign point

[Joelmel Roche]

Hi,

The message comes from /dev/mem
driver when someone accesses a page which is locked. Not a problem
usually since EBUSY is returned so caller can and should retry.
The message comes from MEM_DEBUG which is enabled via MEMDRV_KFT
which is clearly defined on IA kernel.