Technical article 113402

I am receiving panics with "PANIC: k_trap kernel mode trap type 0x0000000F" at random intervals during installation.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6OpenServer 5.0.7

Written · Last revised

Problem

I am receiving panics with "PANIC: k_trap kernel mode trap type 0x0000000F" at random intervals during installation.

Cause

It could be possible that there is a hardware problem with the server.

Solution

Check the following to ensure that the server is correctly configured:

a) Perform a BIOS check.  You may wish to reset the BIOS to the
   default values, disable the internal/external CPU cache to see
   if OpenServer will install if the server runs slower.

In 3.2v4.2 there is also a "cache=/n" bootstring parameter. More detail is given on this issue in ta104329, "Generic advice for installing SCO UNIX operating system."

If the disk is IDE, set the BIOS IDE to run slower, less efficiently. You may have to reduce the cylinder size from 1024 to 1023 for IDE disks to install 3.2v4.2.

Check the PCI Interrupts to ensure that none can be allocated over ISA interrupts, which can cause a conflict.

If applicable, try turning off the built-in Power Management monitoring.

Check with your manufacturer to see if there is a new BIOS available.

b) Check to see if there are any dip switches on the motherboard. If the original documentation is not available, visit the following website for more information:

http://www.motherboards.org

c) Perform a Low Level format of the disk drive.

d) Check the leads, cabling, RAM and processor seating inside the server.

See also

ta104329, "Generic advice for installing SCO UNIX operating system."

ta105303, "My Pentium Pro panics with "PANIC: k_trap kernel mode trap type 0x0000000F.""

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