Technical article 110502

UW7/OSR6, How do I check that my system is running on more than one CPU?

OpenServer 6.0.0UnixWare 7.1.0UnixWare 7.1.1UnixWare 7.1.2UnixWare 7.1.3UnixWare 7.1.4

Written · Last revised

Problem

I know my system has more than one CPU; what can I check on my UnixWare 7/OpenServer6 system to see if they are all being used?

Solution

Several SCO UW7/OSR6 products are licensed so that they support more than one processor in a system by default.

With SCO UnixWare 7.1.4:
UnixWare 7.1.4:
          Small
        Business  Base  Business  Departmental  Enterprise Data Center
USERS     1        1       10          25           50        150
CPUs      1        1        4           4            6          8
MEMORY  1GB      2GB      4GB         8GB         16GB       32GB
These include, prior to UnixWare 7.1.4:

UnixWare 7 Messaging Edition (2 Processor) UnixWare 7 Departmental Edition (2 Processor) UnixWare 7 Enterprise Edition (4 Processors) UnixWare 7 Data Center Edition (8 Processors)

The following are licensed for one processor only:

UnixWare 7 Base Edition
UnixWare 7 Business Edition

Processor support may be expanded in all of the products above by purchasing additional Processor Upgrade license packages.

Purchasing the multiprocessor products above allows the license and
use of several CPUs on the system. The license is automatic on
installation, that is, you do not need to enter any license details
for extra processor support during or after the installation, as
you would have to if, for example, you purchased an additional
Processor upgrade pack. While the system is licensed, in order to
make use of the extra CPUs, the UnixWare "osmp" package must be
installed and the processors recognized by the system.

In the past, for certain manufacturers (Compaq and ICL being examples), it was necessary to have platform specific "osmp" modules installed. These were usually obtained in specific supplements or patches for those platforms, such as the Compaq PSM (Platform Support Module). However, this issue would now only apply to much older systems; more recent systems, even Compaq, should choose the "Intel PSM" at installation.

It is recommended that the "osmp" package be installed on multiprocessor systems at the same time the operating system is being installed, that is, at Initial System Load (ISL). If processors are physically added to a single-processor system at some later stage, the package can be loaded at that time with the SCOadmin "Application Installer" utility. See ta110311 (also referenced at the end of this article) for details.

As an example, with a dual CPU system, you would check the following:

(1) System BIOS

As you boot up your system, enter the BIOS (usually by pressing a key sequence such as <F2>), check how many CPUs it reports and their state. Depending on the particular system, some also display the various settings if configured to do so at boot time.

Some systems may also have a stage before the operating system starts when you can enter a hardware management interface to check the system components. Check what CPUs are reported here if applicable.

(2) Kernel type

If the operating system release of UnixWare 7 supports more than one processor, the kernel will have been compiled to support it. This can be seen by running the following command:

# /etc/conf/bin/idtype

It should return "mp". The usual type for a single-processor system is "atup".

(3) Check that the UnixWare 7 OSMP module is loaded

As the "root" user, run the command:

# pkginfo | grep osmp
system      osmp    OS Multiprocessor Support (OSMP)
(4) Check the DCU

Start "SCOadmin" from the UnixWare 7 GUI screen or by typing "scoadmin" at the command line. Choose "Hardware" and then "DCU", choose "Hardware Device Configuration" and look for the line similar to:

Y       MP Spec V1.1 Platfrm - - - - - -

Ensure the "Y" flag it is set to is activated.

(5) Check the state of the processors
# psrinfo -n
2

# psrinfo -v Status of processor 0 as of 08/31/99 09:59:01 Processor has been on-line since 08/27/99 17:05:39. The Pentium II processor has a i387 floating point processor. The following conditions exist: Device drivers are bound to this processor.

Status of processor 1 as of 08/31/99 09:59:01 Processor has been on-line since 08/27/99 17:07:04. The Pentium II processor has a i387 floating point processor. The following conditions exist: Device drivers are not bound to this processor.

Notice the processors are numbered starting at zero.

(6) Bring the processors on and off-line

The "psradm" command allows you to manipulate the state of the system processors, for example:

Check the current state:
# psrinfo
0 on-line since 09/01/99 17:12:35
1 on-line since 09/01/99 17:13:46
Bring the second processor off-line:
# psradm -v -f 1
UX:psradm: INFO: At 09/07/99 12:02:38, 1 was taken
off-line.
Check its status:
# psrinfo
0 on-line since 09/01/99 17:12:35
1 off-line since 09/07/99 12:02:38
Bring it back online:
# psradm -v -n 1
UX:psradm: INFO: At 09/07/99 12:02:53, 1 was brought
on-line.

You may also use the SCOadmin "Processor Manager" (within the "Hardware" option) to check and alter the processor states.

If a UnixWare LWP process has been bound to a particular CPU using the "pbind(1M)" command, it needs to be unbound before that processor can be taken off-line. If attempted, the processor is reported as "busy". See the "-P" option to the "ps(1)" command for bound process information.

(7) The rptm(1M) utility is also useful because at the top of the screen it shows per-processor load.

NOTE:     Troubleshooting:
          ---------------
          To run the server with a Single Processor Kernel:
To change the kernel type:
To use the Single Processor kernel:
1.  Put PSM=atup in /stand/boot
2.  Run "/etc/conf/bin/idtype"
Should return "mp".
3.  Run "/etc/conf/bin/idtype atup"
4.  Run "/etc/conf/bin/idtype"
Should return "atup".
5.  Run "/etc/conf/bin/idbuild -B"
6.  init 6

- To add the Kernel Memory Debugging Tool (kmdt) replace:

"/etc/conf/bin/idtype atup"
with:
"/etc/conf/bin/idtype kmdt atup"

This will enable "kmastat" within the "crash" command.

See:  http://uw714doc.xinuos.com/en/man/html.1M/crash.1M.html

A more detailed 'kmdt' is available from SCO Support in certain circumstances which will panic the server any time any kernel memory corruption is detected for diagnostic purposes.

Please note that the Emergency Recovery diskettes MUST be created before this package is installed as it will not be possible after.

See also

manual pages: psrinfo(1M), psradm(1M), pbind(1M), pexbind(1M),
priocntl(1), rtpm(1M).

ta110311, "UnixWare7, How do I install the OSMP package?"

ta111842, "How to check how many CPUs your system is licensed to use? "

From the Xinuos technical article database, record 110502. Reproduced with permission. The original is at www.sco.com/ta/110502, which is reachable but blocked from search engines.

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.