Technical article 105656

SMP 5.0.0, 5.0.2 - Kernel trap type E in the routine checkfiletable().

OpenServer 5.0.0OpenServer 5.0.2

Written · Last revised

Problem

My SMP kernel panics with a trap type E.  I followed the
instructions in ta105619, "Panic/Crash Analysis if a dump
is available" and was able to determine that the trap occurs
in the function checkfiletable(), as the kernel stack before
the trap and my kernel stack trace look similar to the following:
# crash -d /dev/swap
> panic
 Kernel Stack before Trap:
 STKADDR   FRAMEPTR  FUNCTION   POSSIBLE ARGUMENTS
 e0000d6c  e0000d94  checkfilet (inode+0x3dc20,0x2000,0x1e00,0)
 e0000d9c  e0000dbc  devfs_clos (inode+0x3dc20,0x3,0x1,0)
 e0000dc4  e0000df0  closef     (file+0xffb4,u+0xe34)
 e0000df8  e0000e00  close      (0x80588e8,0x8058894,0,PND+0x63)
 e0000e08  e0000e28  systrap    (u+0xe34)
> trace
 KERNEL STACK TRACE FOR PROCESS 208:
 STKADDR   FRAMEPTR  FUNCTION   POSSIBLE ARGUMENTS
 e0000c60  e0000cdc  prf_task_s (0x4,0,inode+0x3dc20,0xe)
 e0000ce4  e0000cfc  cmn_err    (0x3,dmsize+0x210,0xe,u+0xd3c)
 e0000d04  e0000d30  k_trap     (u+0xd3c)
           e0000d3c  kern_trap  from 0xf018152a in checkfilet
   ax:fb840001 cx:fb84bff0 dx:fb84bfe4 bx:fb935c20 fl:    10212 ds: 160 fs:
 0
   sp:e0000d6c bp:e0000d94 si:    2000 di:f0981e00 err:       0 es: 160 gs:   0
 e0000d44  e0000d94  checkfilet (inode+0x3dc20,0x2000,0x1e00,0)
 e0000d9c  e0000dbc  devfs_clos (inode+0x3dc20,0x3,0x1,0)
 e0000dc4  e0000df0  closef     (file+0xffb4,u+0xe34)
 e0000df8  e0000e00  close      (0x80588e8,0x8058894,0,PND+0x63)
 e0000e08  e0000e28  systrap    (u+0xe34)
           e0000e34  scall_noke from     0x5a98
   ax:       6 cx:7ffffe00 dx:    2f9d bx: 80588e8 fl:      202 ds:  1f fs:   0
   sp:e0000e64 bp:7ffffe0c si: 8058894 di:       0 err:       6 es:  1f gs:   0

Cause

The checkfiletable() routine neglects to perform locking which is necessary in a multiprocessor environment.

Solution

This problem has been resolved in SCO OpenServer Release 5.0.4.

NOTE:     It is possible to do an in-place upgrade to SCO OpenServer 5.0.4
          from either SCO OpenServer Release 5.0.0 or 5.0.2.

See also

ta105619, "Panic/Crash Analysis if a dump is available."

From the Xinuos technical article database, record 105656. Reproduced with permission. The original is at www.sco.com/ta/105656, 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.