Technical article 105686

SMP 5.0.0, 5.0.2 - "PANIC: lock timeout" even though OSS437A is already applied on the system; sometimes the panic is not readable.

OpenServer 5.0.0OpenServer 5.0.2

Written · Last revised

Problem

I have installed Support Level Supplement (SLS) OSS437A on my SMP system, yet my system still experiences lock timeout panics. Sometimes the panic dump is not readable by the crash utility. When the panic dump happens to be readable by the crash utility, it looks something like this:

> panic
System Messages:
mem: total = 523900k, kernel = 20056k, user = 503844k
J        K swapdev = 1/41, swplo = 0, nswap = 1070000, swapmem = 535000k
M rootdev = 1/42, pipedev = 1/42, dumpdev = 1/41
kernel: Hz = 100, i/o bufs = 6652k
%CPU2     -             255     -       type=Pentium CPU with fpu
%CPU3     -             255     -       type=Pentium CPU with fpu
%CPU4     -             255     -       type=Pentium CPU with fpu

PANIC: lock timeout lock=00000401, owner=F019BF23 Trying to dump 130975 pages to dumpdev hd (1/41) at block 0, 1638 pages per '.' .

Panic String: lock timeout lock=%x, owner=%x
> trace
KERNEL STACK TRACE FOR PROCESS 370:
STKADDR   FRAMEPTR  FUNCTION   POSSIBLE ARGUMENTS
e0000ca0  e0000d14  prf_task_s (0x4,0,0x3,0x1)
e0000d1c  e0000d34  cmn_err
(0x3,cmn_mess1,0x401,lockb_failure+0xa)
e0000d3c  e0000df0  hung       (sysent+0x140,u+0xe34)
e0000df8  e0000e00  cxenix     (0x4,0x4028f8,0x20,0x4)
e0000e08  e0000e28  systrap    (u+0xe34)
          e0000e34  scall_noke from    0x1191c
  ax:    2428 cx:      20 dx:       5 bx:       4 fl:      206 ds:  1f fs:   0
  sp:e0000e64 bp:7fffee24 si:  4028f8 di:      20 err:    2428 es:  1f gs:   0
> user
PER PROCESS USER AREA FOR PROCESS 370
USER ID's:      uid: 0, gid: 0, real uid: 0, real gid: 0
        supplementary gids:
PROCESS TIMES:  user: 0, sys: 0, child user: 0, child sys: 0
PROCESS MISC:
        command: nsmsrv, psargs: /etc/vision/bin/nsmsrv -p7
        proc: P#370, cntrl tty: maj(??) min(??)
        start: Thu May 22 13:34:50 1997
        mem: 0x23, type: fork su-user
        proc/text lock: none
        current directory: I#97
OPEN FILES AND POFILE FLAGS:
          [ 0]: F#371        [ 1]: F#421        [ 2]: F#421
          [ 3]: F#426        [ 4]: F#407        [ 5]: F#1487
FILE I/O:
        u_base: 0x7ffff87e, file offset: 75, bytes: 0
        segment: data, cmask: 0022, ulimit: 2097151
        file mode(s): read
SIGNAL DISPOSITION:
        sig#      signal oldmask sigmask
           1: ignore        -
           2: ignore        -
           3: ignore        -
          13: ignore        -
          14:      0xfa4    -

Solution

This has been corrected with SLS OSS468A. Apply SLS OSS468A to your system.

See also

TA105203, "What is Support Level Supplement (SLS) OSS437A?"

TA109333, "What is the SLS OSS468A, the Networking and SMP Supplement for OpenServer 5.0.0 and 5.0.2?"

From the Xinuos technical article database, record 105686. Reproduced with permission. The original is at www.sco.com/ta/105686, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.