Technical article 109675

The command "sconf -v" causes my system to panic with "trap type 0x0E".

OpenServer 5.0.4

Written · Last revised

Problem

I have installed SCO OpenServer Release 5.0.4 and Release
Supplement 504C (rs504c) onto a system with two SCSI host
adapters.  When I execute the command "sconf -v", the system
panics with "trap type 0x0E."

If I remove the Release Supplement 504C, or only have one SCSI host adapter configured, this panic does not occur.

A stack trace using crash(ADM) indicates that the panic occurred
within the Scfgioctl kernel routine.  For example:
# crash
> trace
KERNEL STACK TRACE FOR PROCESS 16:
STKADDR   FRAMEPTR  FUNCTION   POSSIBLE ARGUMENTS
e0000ab4  e0000bc8  prf_task_s (0x4,0,0x8047e08,0xe)
e0000bd0  e0000bec  cmn_err    (0x3,dmsize+0x25c,0xe,u+0xc2c)
e0000bf4  e0000c20  k_trap     (u+0xc2c)
          e0000c2c  kern_trap  from 0xf001547e in kstrcpy
  ax:       0 cx:ffffffff dx:f0888a44 bx: 8047e08 fl:    10246 ds: 160
fs:   0
  sp:e0000c5c bp:e0000cec si:f0888a44 di:       0 err:       0 es: 160
gs:   0
e0000c34  e0000cec  kstrcpy    (u+0xd74,0x1,0x4e0,u+0x1148)
e0000cf4  e0000d8c  Scfgioctl  (0x2700,0xd,0x8047ec4,0x3)
e0000d94  e0000dbc  devfs_ioct (inode+0x4290,0xd,0x8047ec4,0x3)
e0000dc4  e0000de8  ioctl      (0,0x2,0x8047e80,u+0xe10)
e0000df0  e0000e10  systrap    (u+0xe1c)
          e0000e1c  scall_noke from 0x8003066e
  ax:      36 cx:8005bccc dx:8005be98 bx:       0 fl:      212 ds:  1f
fs:   0
  sp:e0000e4c bp: 8047ed0 si:       2 di: 8047e80 err:      36 es:  1f
gs:   0

Solution

In order to prevent this panic, add the boot option "scsi.noscan"
(see bootstring(HW) for details) to the DEFBOOTSTR entry in the
file /etc/default/boot.  For example:
DEFBOOTSTR=hd(40)unix scsi.noscan

Reboot the system for this change to take effect.

See also

The manual page for crash(ADM).

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