Technical article 105292

Does the Compaq ProLiant 5000 work with SCO Open Server?

OpenServer 5.0.0OpenServer 5.0.2

Written · Last revised

Problem

Does the Compaq ProLiant 5000 work with SCO Open Server?  Are
there known problems and workarounds?

Solution

Yes, this combination has been tested by Compaq. There are three known issues, which all have workarounds:

A. Non-recognition of the second or other properly licensed CPUs.

B. System panic with kernel trap 6 or E if there are unlicensed CPUs present.

C. Hang condition under certain stress situations (also seen on SCO OpenServer 5).

Following are the workarounds:

A. To correct the problem, use the following procedure to disable the Systempro/XL driver. This allows SCO Open Server 3.0 to recognize the SCO Intel multiprocessing (MPS) driver, which is the correct multiprocessing driver for the ProLiant 5000. Note that this procedure needs to be repeated each time SCO MPX 3.0 is installed.

NOTE: Before performing this procedure, for Intel MPS support, SCO Advanced Hardware Supplement (AHS) 3.4 must be installed, followed by SCO Support Level Supplement (SLS) UOD421A.

1. Log in as root.
2. Change directory to /etc/conf/sdevice.d:
cd /etc/conf/sdevice.d

3. Modify the sysproxl file and change the Y in the second column to N.

From:
sysproxl    Y    1    0    0    0    0    0    0    0
To:
sysproxl    N    1    0    0    0    0    0    0    0

4. Relink the kernel and reboot the system for the changes to take effect.

cd /etc/conf/cf.d
./link_unix -y
shutdown -i6

B. The number of system processors installed in the ProLiant 5000 must not exceed the number of system processors licensed under SCO Open Server Release 3.0. Remove the additional processors until the number of processors in the ProLiant 5000 match the number of processors licensed under SCO Open Server Release 3.0.

C. The hanging situation can be eliminated by modifying the APIC driver to reduce the amount of time spent waiting for the APIC hardware to deliver inter-processor interrupts. This problem is unlikely to occur with less than four CPUs, and has only been seen in laboratory test situations.

NOTE: The problem does not occur when SCO OpenServer Release 5.0 is installed using Compaq SmartStart 3.0 or later.

To modify the APIC driver and relink the UNIX kernel, perform either of the following procedures, depending on the release of Open Server installed in the server.

For Open Server Release 3.0 systems:
------------------------------------

IMPORTANT: For Intel MPS support, first install SCO Advanced Hardware Supplement (AHS) 3.4, and then install SCO Support Level Supplement (SLS) UOD421A before performing this procedure.

1. Log in as root.
2. Change the directory to /etc/conf/pack.d/apic:
cd /etc/conf/pack.d/apic

3. Make a backup copy of the existing driver:

cp Driver.o Driver.o.orig

4. Invoke the SCO patch utility, _fst, with the write option:

/etc/_fst -w Driver.o

5. Verify that the original code has not already been modified:

apic_await_intcmd+0x7?ia
The correct response should be:
apic_await_intcmd+0x7:   mov     [epb-0x4], 0x5f5e100
6. Change the delay value:
apic_await_intcmd+0xa?W0x5f5e10
The correct response should be:
apic_await_intcmd+0xa: 0x5f5e100 = 0x5f5e10

7. Verify that the code has been properly modified:

apic_await_intcmd+0x7?ia
The correct response should be:
apic_await_intcmd+0x7:   mov     [epb-0x4], 0x5f5e10

8. Exit the patch utility by pressing <Ctrl><d>.

9. Relink the kernel, and reboot the system for the changes to take effect:

cd /etc/conf/cf.d
./link_unix -y
shutdown -i6
For OpenServer Release 5.0 systems:
------------------------------------

NOTE: When SCO OpenServer Release 5.0 is installed using Compaq SmartStart Release 3.0 (or later), this procedure is applied during the installation of SmartStart Release 3.0.

1. Log in as root.
2. Change the directory to /etc/conf/pack.d/apic:
cd /etc/conf/pack.d/apic

3. Make a backup copy of the existing driver:

cp Driver.o Driver.o.orig

4. Invoke the SCO patch utility, _fst, with the write option:

/etc/_fst -w Driver.o

5. Verify that the original code has not already been modified:

apic_await_intcmd+0x10?ia
The correct response should be:
apic_await_intcmd+0x10:  mov     edi, 0x5f5e100
6. Change the delay value:
apic_await_intcmd+0x11?W0x5f5e10
The correct response should be:
apic_await_intcmd+0x11: 0x5f5e100 = 0x5f5e10

7. Verify that the code has been properly modified:

apic_await_intcmd+0x10?ia
The correct response should be:
apic_await_intcmd+0x10:  mov     edi, 0x5f5e10

8. Exit the patch utility by pressing <Ctrl><d>.

9. Relink the kernel and reboot the system for the changes to take effect.

cd /etc/conf/cf.d
./link_unix -y
shutdown -i6

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