Technical article 109806

After installing OSS469B, "WARNING: CPU2 boot failure" is displayed upon boot-up, or the system hangs at "E mp_setup", or panics at "G mp_picinit".

OpenServer 5.0.4

Written · Last revised

Problem

I am configuring a multi-processor system and have installed the software below in the following order:

1. SCO OpenServer Release 5.0.4
2. SCO SMP (Symmetrical Multiprocessing) Release 5.0.4
3. Release Supplement 5.0.4c (https://ftp.scoexpert.com/Supplements/rs504c/)
4. SLS OSS469B  (https://ftp.scoexpert.com/SLS/oss469b)

I have then relinked the kernel, but when rebooting the system, the following error messages appear:

E mp_setup
WARNING: CPU2 boot failure

and, as indicated, CPU2 does not work when the system is ready.

On some SMP systems, it has also been observed that the system may hang at the "E mp_setup" message or even panic at "G mp_picinit".

Solution

This problem has been fixed by Support Level Supplement (SLS) OSS469D.

If the system hung or paniced, reboot by typing "unix.old" at the boot prompt.

Check the /etc/conf/cf.d/stune file (see stune(F)) for the existence of an entry for the kernel parameter, MAXACPUS.

In most cases, this kernel parameter can be left set to its default value as specified in the file /etc/conf/cf.d/mtune (see mtune(F)), for example:

* MultiProcessing Parameters
*            Default  Minimum  Maximum
MAXACPUS        9       1       29

In this case, remove the MAXACPUS line from the /etc/conf/cf.d/stune file, relink the kernel and then reboot the system. The second CPU should now be active.

See also

ta105811, "What is the Release Supplement 504C for SCO OpenServer Release 5.0.4 (rs504c) and how can I obtain it?"

ta109975, "What is SLS OSS469D, the Networking and SMP Supplement for OpenServer 5.0.4?"

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