Operating System - Tru64 Unix
1753640 Members
5263 Online
108798 Solutions
New Discussion юеВ

Re: pset_info shows a processor in off-line status and psradm cannot start it

 
WW346672
Occasional Advisor

Re: pset_info shows a processor in off-line status and psradm cannot start it

Hi,

Hereafter the the config of AS 1200:
Module Type Rev Name
System Motherboard 0 0000 mthrbrd0
Memory 512 MB DIMM 0 0000 mem0
Memory 512 MB DIMM 0 0000 mem0
Memory 512 MB DIMM 0 0000 mem0
Memory 512 MB DIMM 0 0000 mem0
CPU (4MB Cache) 3 003 cpu0
CPU (4MB Cache) 3 0003 cpu1
Bridge (IOD0/IOD1) 600 0032 iod0/iod1
PCI Motherboard a 0004 saddle0

Bus 0 iod0 (PCI0)
Slot Option Name Type Rev Name
1 PCEB 4828086 0005 pceb0
2 S3 Trio64/Trio32 88115333 0054 vga0
3 QLogic ISP10X0 10201077 0005 isp0


Bus 1 pceb0 (EISA Bridge connected to iod0, slot 1)
Slot Option Name Type Rev Name

Bus 0 iod1 (PCI1)
Slot Option Name Type Rev Name
1 NCR 53C810 11000 0002 ncr0
2 DECchip 21140-AA 91011 0022 tulip0

Hereafter the result of sh cpu:
Primary CPU: 00
Active CPUs: 00 01
Configuraed CPUs: 00 01
SROM Revision: V3.0 V3.0

No we did not upgrade the firmware after adding the second cpu.

Thanks
Vladimir Fabecic
Honored Contributor

Re: pset_info shows a processor in off-line status and psradm cannot start it

Looks like both CPUs are configured.
And also looks like you have enough licenses.
Not sure what can be the problem, but I would upgrade the firmware.
Upgrade the firmware and after that send output of:
>>> show config
# prsinfo -v
In vino veritas, in VMS cluster
peynet
Occasional Advisor

Re: pset_info shows a processor in off-line status and psradm cannot start it

we have exactly the same problem on AS1200 ruuning under 4.0e the firmware update was done after installing CPU
psrinfo and online -v reply to us the same as WW346672 question in november 2009

No solution for the moment

Regards,
Eric
peynet
Occasional Advisor

Re: pset_info shows a processor in off-line status and psradm cannot start it

Here is the solution for my problem

The problem is due to subsystem generic lockmode parameter wich is set to 1 in sysconfigtag
Commenting lockmode or setting to 0 and setting cpu-enable-mask to 3 solve the problem

--------------------------------------------The mode of the simple lock primitive package within the kernel. Four sets of locking primitives support various combinations of real-time (RT) kernel preemption, symmetric multiprocessing (SMP), and lock debugging with lock statistics.

When only RT is required (lockmode=1), the simple lock operations maintain a "preemption blocking" count.