kernel panic with trap type 0x0000000D

[amalik]

Hi
I am running SCO Open Server network system. The system has paniced twice in last 10 hours with the following message.
Unexpected trap in kernel mode
panic: k_trap - kernel mode trap type is 0x0000000D

what can caused this trap and how can we fix this

Thanks

 

[Guest_imported]

This is from SCO site--
It may help you.

Check the hardware:
(1) Check for different types of memory chips between the motherboard and the add-on memory board. The chips should:


(A) have the same speed;
(B) have the same memory chip size.

For example, if the memory on the motherboard has 256K-size
chips while the add-on board has 1Meg-size chips (for 4Meg
RAM), then this may cause problems during installation.



(2) If memory checks out fine, then follow the steps listed below.
(2.1) Remove all hardware components that are not necessary for the installation of the operating system.


For example, remove any intelligent serial port, network
card, or any unsupported tape drive.


(2.2) Turn off all cache if possible.

For example, disable shadow ram, shadow bios, hi speed cache.


(2.3) Check the type of video card on the system. Try to get a supported type of video card. Supported video cards are listed in the Release Notes section of the SCO System V Operating System manuals.

For example, if it is a non-supported VGA type, make sure
autoswitching is disabled (turn off Auto-switch from VGA
to EGA mode). If the video card is a 16 bit card, try
putting it into 8 bit slot to avoid any DMA conflict.


(2.4) Verify that the hard disk controller card is supported. A list of supported hard disk controller cards is in the SCO System V Operating System Release Notes.

For SCSI Host adaptor, make sure the terminating resistors are
terminated properly. Only the logical end of the chain of the
SCSI bus are terminated. And for the SCSI hard disk, make sure
the target I.D. are jumpered correctly.

For example, for the first SCSI hard disk, the target I.D.
should be zero. And there should be no jumper in the back
of the hard disk. For the second hard disk, the target I.D.
can be set to one -- there should only be one jumper in the
back of the hard disk.