Make sure the secondary processors are functioning properly.

If the server is already up, stop all processors except Processor 0. In Novell Remote Manager, click the Processor link under the Manage Hardware setting in the navigation frame. Click the Stop Processor link for each processor online except processor 0. (Processor 0 cannot not be taken offline.)

If the server is down, bring up the server and then stop all processors.

If the problem still occurs, go to Step 2. If not, go to Step 4.

To verify that this is not an interrupt issue, remove the PSM. Then reboot the server; only processor 0 will start.

The mps14.psm, cpqmpk.psm or *.psm in the startup.ncf file is the interrupt abstraction layer and communicates with the APIC (Advanced Programmable Interrupt Controller) rather than the PIC for interrupt handing in the machine.

If the problem still occurs, it not a multiprocessing issue.

If the problem no longer occurs, go to Step 3.

Make sure you have the latest machine updates (current ROM, BIOS, etc.).

If you confirm that your hardware is current and the problem still occurs, it’s possible that you are using a new version that wasn’t available at the time NetWare 6.5 was released. Whatever is different about the hardware requires a newer PSM to work with the machine.

Gather information as explained in Section 6.1, Using a Troubleshooting Methodology. View the startup.ncf and autoexec.ncf files to determine what software pieces are running. Check with the software vendors and developers and tell them what steps you have taken and give them enough information to duplicate the problem.