[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference mr1pst::sco_unix

Title:sco_unix
Moderator:AVNGRS::BOELKE
Created:Mon Mar 26 1990
Last Modified:Thu May 22 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2574
Total number of notes:9709

2555.0. "Trap K on Prioris ZX6000" by SNOFS1::pcbu46.snl.dec.com::OGDEN (There's Nothing Quick Like A V8...) Fri Nov 29 1996 01:02

T.RTitleUserPersonal
Name
DateLines
2555.1Panic caused by printing to the parallel portCSCMA::EARNESTTue Dec 03 1996 16:2039
2555.2Update from SCOCSCMA::EARNESTFri Mar 14 1997 15:3145
    
My Pentium Pro panics with "PANIC: k_trap kernel mode trap type 0x0000000F."

KEYWORDS: panic trap f trapf 0x0000000F openserver v5.0.0 5.0.2 unix host desktr

RELEASE:  SCO OpenServer Enterprise System Release 5.0.0, 5.0.2
          SCO OpenServer Desktop System Release 5.0.0, 5.0.2
          SCO OpenServer Host System, Release 5.0.0, 5.0.2

PROBLEM:  Some systems are known to panic with the panic message:

                PANIC: k_trap   kernel mode trap type 0x0000000F

          This problem has only been experienced on Pentium Pro
          machines, up to this point.  It is most frequently associated
          with the SCO parallel driver and printing to a parallel port.
          It has also been associated with running the OS on a single 
          CPU without SCO SMP on a machine containing an APIC chipset 
          and multiple cpus.
        
SOLUTION: This issue is still under investigation.  Possible workarounds
          are listed below.  The problem is with the BIOS, but SCO has
          attempted to provide alternative solutions if the BIOS manufacturer
          has not yet fixed the problem.   Please note that the fix has
          not been tested at SCO because we have not been able to
          reproduce the problem.  
        
          Here are three possible fixes:
        
               1. Obtain a BIOS fix from the BIOS manufacturer.  Note this
                  solution is the most recommended if available.
        
               2. Install and license SMP.  This may create an environment
                  where the problem does not occur.
        
               3. Install a beta fix from SCO, which includes a replacement
                  trap.o  The fix will allow Trap Fs to occur without 
                  panic'ing the system.  Please contact SCO Technical Support
                  to arrange fix availability.
        
                  Note:  This is not an SLS; rather, it is a beta fix and as
                  such there is no guarantee to its fitness; the user can
                  install at their own discretion and risk.
        

2555.3Another updateCSCMA::EARNESTThu May 08 1997 11:3838
My Pentium Pro panics with "PANIC: k_trap kernel mode trap type 0x0000000F."

KEYWORDS: panic trap f trapf 0x0000000F openserver v5.0.0 5.0.2 unix host desktop enterprise k_trap cpu apic smp multiple kernel mode type pentium pro parallel port print lp driver intel reserved ERGREF 1976 ENGREF SCO-236-649 message erroross452a

RELEASE:  SCO OpenServer Enterprise System Release 5.0.0, 5.0.2
          SCO OpenServer Desktop System Release 5.0.0, 5.0.2
          SCO OpenServer Host System, Release 5.0.0, 5.0.2

PROBLEM:  Some systems are known to panic with the panic message:

                PANIC: k_trap   kernel mode trap type 0x0000000F

          This problem has only been experienced on Pentium Pro
          machines, up to this point.  It is most frequently associated
          with the SCO parallel driver and printing to a parallel port.
          It has also been associated with running the OS on a single 
          CPU without SCO SMP on a machine containing an APIC chipset 
          and multiple cpus.

SOLUTION: Possible workarounds are listed below.  The problem is with
          the BIOS, but SCO has attempted to provide alternative solutions
          if the BIOS manufacturer has not yet fixed the problem.  

          Here are three possible fixes:

               1. Obtain a BIOS fix from the BIOS manufacturer.  Note this
                  solution is the most recommended if available.

               2. Install and license SMP.  This may create an environment
                  where the problem does not occur.

               3. Install the SLS oss452 from SCO, which includes a replacement
                  trap.o.  The fix will allow Trap Fs to occur without 
                  panic'ing the system.  The SLS oss452 is available for 
                  downloading from SCO's Online Services.

SEE ALSO:  IT os/3252: "What is Support Level Supplement (SLS) OSS452A,
           the Trap F Supplement?"
2555.4OSS452A Patch AvailableCSCMA::EARNESTThu May 08 1997 11:39272
What is Support Level Supplement (SLS) OSS452A, the Trap F Supplement?

KEYWORDS: support level supplement sls OSS452A oss452a panic trapF trap f trapf 0x0000000F openserver v5.0.0 5.0.2 unix host desktop enterprise internet faststart 1.0.0 1.1.0 k_trap cpu apic smp multiple kernel mode type pentium pro parallel port print lp driver intel reserved ERGREF 1 976 ENGREF SCO-236-649 message error O bios

RELEASE:  SCO OpenServer Enterprise System Release 5.0.0, 5.0.2
          SCO OpenServer Desktop System Release 5.0.0, 5.0.2
          SCO OpenServer Host System Release 5.0.0, 5.0.2
          SCO Internet Faststart Release 1.0.0, 1.1.0

PROBLEM:  What is Support Level Supplement (SLS) OSS452A, the Trap F
          Supplement, and how do I install it?

SOLUTION: The attached cover letter describes the enhancements and corrections
          to known problems for SCO OpenServer Release 5.0 and Internet 
          FastStart Release 1.* found in, and the installation procedure for, 
          SLS OSS452A.


Dear SCO Customer,

The enclosed Support Level Supplement (SLS) OSS452A, prevents a panic with
the panic message:

                 PANIC: k_trap   kernel mode trap type 0x0000000F

which is known to occur on Pentium Pro machines, most notably while printing
to a parallel port.  It is most frequently associated with running SCO
OpenServer 5.0 on a single CPU without SCO SMP on a machine containing an
APIC chipset and multiple CPUs.  At this point, the occurrence of a trap F
can be considered to be a spurious event of no special significance to the
operating system.

This patch resolves the issue by acting on an occurrence of a trap F event
in a manner other than panicking the system.  When the patch is applied,
the response of the kernel to a trap F becomes tunable.  The description below 
of the tunability is appended to the file /etc/conf/pack.d/kernel/space.c.
By default, the tunable variable trapf_action is set to 2:

/*                                                 TRAP_F_PATCH 
 * The setting of trapf_action defines the behavior in the
 * event of a the kernel receiving a Trap F. Note that this
 * should never happen, and is probably the result of a
 * hardware problem with your system. Appropriate action
 * should be taken to trace and rectify the fault. The
 * following actions may be taken on receipt of a Trap F:
 *
 *      trapf_action     action
 *      ----------------------------------
 *           0           PANIC the kernel
 *           1           consume the Trap F silently
 *           2           report the error first time only
 *           3           report the error every time
 */
int trapf_action = 2;                           /* TRAP_F_PATCH */

If desired, the value of trapf_action may be modified to take on the values
0, 1, or 3.  Relink the kernel and reboot for the changes to take effect.

Note: Instead of applying this patch, a BIOS fix from the BIOS manufacturer
      may be obtained.  This is most highly recommended, as it will prevent
      these spurious trap F events from occurring.  Also, in the upcoming
      release of SCO OpenServer 5, the response of the kernel to a trap F
      will not be tunable, and will be as if trapf_action is set to the 
      value 3.


RELEASE INFORMATION

SLS OSS452A is intended for use on these products:

SCO OpenServer Enterprise System Release 5.0.0, 5.0.2
SCO OpenServer Desktop System Release 5.0.0, 5.0.2
SCO OpenServer Host System Release 5.0.0, 5.0.2
SCO Internet FastStart Release 1.0.0, 1.1.0


INSTALLATION AND REMOVAL INSTRUCTIONS

Installing patches on SCO OpenServer 5.0.x usually consists of two phases:
"Loading" and "Applying".  The instructions that follow enable you to both 
install the patch from distribution media or media image, as well as 
configure the patch to be installed from a remote SCO OpenServer 5.0.x
system over a TCP/IP network.


I. LOADING THE PATCH

1. Log in as root.

2. If you are installing this SLS from a media image, there is a file
   called oss452a.Z.  Uncompress this file with this command:

        # uncompress oss452a.Z

   Copy the file to the /tmp directory and name it VOL.000.000:

        # cp oss452a /tmp/VOL.000.000

   If you are installing this SLS from floppy disk media, skip this
   step and proceed to step 3.

3. Execute the command:
        
        # scoadmin software

   or double click on the Software Manager icon on the desktop.

4. Pull down the "Software" menu and select 
   "Patch Management-->Load Patch".

5. You will see the "Begin Load Patch" menu.  Be sure the
   local machine name is selected and choose "Continue".

6. You will see the "Select Media" menu. 

   a. If you are loading this SLS from floppy disk media, 
      select the appropriate floppy disk drive and
      choose "Continue".  Proceed to step 7.

   b. If you are loading this SLS from a media image per step 2,
      pull down the "Media Device" menu and select "Media Images",
      then choose "Continue".  You will then see the "Enter Image 
      Directory" menu.  Enter /tmp and choose "OK".

7. You will see the "Load Patch Preference" menu.  Choose "Full".

8. You will see the "Load Patch Progress" window.  If the patch loads
   successfully, you will see a "Message" window that states "Load 
   Patch complete".  Choose "OK".  You are then returned to the main 
   Software Manager window.

9. To apply the patch now, continue with step 2 under section II, 
   "Applying the Patch".  To exit the Software Manager now, select
   "Exit" from the "Host" menu.
      

II. APPLYING THE PATCH

1. Log in as root. Execute the command:

        # scoadmin software 

   or double click on the Software Manager icon on the desktop.

2. Pull down the Software menu and select "Patch Management-->Apply Patch".

3. You will see the "Begin Apply Patch" menu.  Be sure that the local
   machine name is selected and choose "Continue".

4. You will see the "Select Media" menu. The "Hard Disk" menu item 
   should already be selected.  Choose "Continue".

5. You will be presented with the "Select Patch-product to Apply" menu.
   Highlight the "Streams Lock Timeout and Protocol Data Supplement oss452a"
   patch and then choose "Full" to continue.

6. You will see the "Apply Patch Progress" window as the system applies
   the patch.

7. You will see an information window displaying the message:

      During this apply patch, the kernel was relinked. You must reboot
      your system to make this kernel effective.

   Click on "OK". 

8. You will see a "Message" window stating "Apply Patch Complete".  Choose "OK"
   and you will be returned to the Software Manager's main menu.  Exit the
   Software Manager by choosing "Exit" from the "Host" menu.

9. Log in as root on tty01, and shut down the system:

        # shutdown -g0 -y

   After shutting down and rebooting the machine, application of the patch
   is complete.


III. NOTES ON NETWORK INSTALLATION

To install the patch on other SCO OpenServer 5.0.* machines over the network,
first load the patch as in section I above on a designated installation 
server.  Then create the user "swadmin" on the installation server.

When running the Software Manager on the system where the patch will be
installed, you will be prompted for the source location of the patch in 
the "Begin Load Patch" window.  Be sure to choose "from another host" 
during this phase.  You will need to provide the name of the installation 
server, as well as the password of the "swadmin" user on the installation 
server, to initiate the installation process.


IV. PATCH REMOVAL


NOTE: Patches must be rolled back in the reverse order in which they were 
installed on a per-component basis.  Hence, if the "Trap F Supplement oss452a"
patch is not the most recent patch applied to the UNIX component of the
product, you will have to rollback all patches applied after the "Trap F
Supplement oss452a" patch prior to rollback of the "Trap F Supplement
oss452a" patch.

If you want to remove the patch, take these steps:

1. Log in as root. 

2. Execute the command:

        # scoadmin software

   or double click on the Software Manager icon in the desktop.

3. Pull down the "Software" menu and select 
   "Patch Management-->Rollback Patch".

4. You will see the "Begin Rollback Patch" menu, and be asked to select
   patched software to rollback. Select "SCO UNIX System V Operating System"
   and choose "Continue".

5. You will see the "Patch Selection" window. Make sure that the 
   "Trap F Supplement oss452a" patch is selected, and choose "Continue".

6. You will see the "Confirm Selected Patches" window. Choose
   "Rollback" to confirm removal of the "Trap F Supplement oss452a"
   patch.

7. You will see the "Rollback Progress" window, as the system 
   performs the rollback of the patch.

8. You will see an information window displaying the message:

           NOTE: During this rollback, the link kit wll be updated. Afterwards
                 you must relink your kernel and reboot your machine in order
                 to make this rollback effective.

      Press return to continue:

9. After pressing the <RETURN> key, you will see the "Rollback Progress"
   window, after which a "Message" window stating "Rollback Patch Complete"
   appears.  Choose "OK" and you will be returned to the Software Manager's 
   main menu. Exit the Software Manager by choosing "Exit" from the "Host" 
   menu.

10. Log in as root and relink the kernel:

        # cd /etc/conf/cf.d
        # ./link_unix -y

11. Log in as root on tty01, and shut down the system:

        # shutdown -g0 -y

    After shutting down and rebooting the machine, rollback of the patch
    is complete.

12. To also unload the patch, making it no longer available to be applied, 
    follow the steps in this section.  In step 3, choose:

        "Patch Management-->Unload Patch"

    instead of:
 
        "Patch Management-->Rollback Patch"


If you have questions regarding this SLS, or the product on which it is
installed, please contact your software supplier.  

We appreciate your business.

SCO Support Services