Search Text         
Search Tips?
Search By   And   Or   Boolean   Exact Match   TA #
Search In   Whole Doc   Keywords Sort By  
Product   Sub Product  

View Technical Articles (sorted by Product) New/Updated in the last:    7 days      14 days      30 days             
TA # Date Created Date Updated Resolved Issue?   Printer Friendly Version of This TA   Print Article
  E-mail This TA   E-mail Article
109675 10/01/1998 01:37 PM 05/17/2001 11:53 AM
Yes No
The command "sconf -v" causes my system to panic with "trap type 0x0E".
Keywords
openserver open server osr5 v5 5.0.4 sconf -v Scfgioctl two SCSI host adapters release supplement panic crash trace /etc/default/boot defbootstr scsi.noscan
Release
SCO OpenServer Enterprise System Release 5.0.4
SCO OpenServer Host System Release 5.0.4
SCO OpenServer Desktop System Release 5.0.4

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).

Related Articles
•  SCO Advanced File and Print Server permissions.
•  ARCserve/Open won't find my SCSI tape drive when my boot hard disk is on an IDE/EIDE controller.
•  What network cards does SCO AHS Release 5.2.0 support?
•  What is SLS OSS463B, the Multiple SCSI Install N0 and BTLD Supplement?
Back to Search ResultsBack to Search Results