Technical article 110003

When booting after installing SLS OSS471C, the message "UX: P6 update: Error: cannot bind to processor 1" appears.

OpenServer 5.0.4OpenServer 5.0.5

Written · Last revised

Problem

After installing Support Level Supplement (SLS) OSS471C, and rebooting the system, the following message is displayed on the console:

UX: P6 update: Error: cannot bind to processor 1

The system continues to boot without further incident and appears stable.

Cause

SLS OSS471B was implemented entirely within the kernel and did not use /dev/at*. However, SLS OSS471C is implemented mostly as the command /etc/p6update, which needs to make processor ioctls using /dev/at*, in order to lock onto (bind to) each CPU to update it. Otherwise, on a heterogeneous multiprocessor system, there is the danger that it would apply an update suited for one CPU to a CPU for which it is not suited.

When you install SLS OSS471C it updates the inittab placing a call to p6update at the beginning of the file. This is a problem because ifor_pmd(ADM) (the license policy manager deamon) has not started. Therefore, additional CPUs cannot be accessed. Placing this line directly after ifor_pmd(ADM) does not help either because it doesn't give ifor_pmd(ADM) enough time to initialize.

Solution

This problem has been fixed in SLS OSS471E. See ta105899, "What is SLS OSS471E, the Intel Pentium Pro and Pentium II Microcode Driver for SCO OpenServer 5.0.4 and 5.0.5?" for more information.

NOTE:     If you have OSS471C, as a workaround, you can take these steps.
          After installing SLS OSS471C, run the command:
/etc/p6update ( -v)

Also, edit /etc/conf/cf.d/init.base, as shown here in the before and after state.

Before:
p6u::sysinit:/etc/p6update </dev/console >/dev/console 2>&1
After:
p6u::sysinit:(sleep 5 ; /etc/p6update) </dev/console >/dev/console 2>&1
Relink the kernel.

See also

The manual page for ifor_pmd(ADM).

ta105899, "What is SLS OSS471E, the Intel Pentium Pro and Pentium II Microcode Driver for SCO OpenServer 5.0.4 and 5.0.5?"

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