| Author |
CPU Pegging |
Galen
Member
Posts: 16
Joined: 19.08.13 |
| Posted on August 20 2013 11:40 |
|
|
I have installed FreeAXP 2.4.1.502 and restored our backups (7.3-2) to the new virtual disks. The CPU is maxed out on one core. I installed IDLE v1.2 and the CPU usage subsided to normal levels. This works fine until I shutdown my PC. After rebooting the PC and restarting the virtual AXP system, the CPU is again maxed out on one core. Doing the install of IDLE v1.2 again, resolves the problem until I need to reboot the PC. When i shut down the AXP and exiting the emulator and then restart the AXP system and the emulator, the CPU usage is at normal levels. Rebooting again restores the CPU issue.
What do I need to do to keep the settings of IDLE v1.2 after I have rebooted the PC? |
|
|
| Author |
RE: CPU Pegging |
Bruce Claremont
Moderator
Posts: 623
Joined: 07.01.10 |
| Posted on August 21 2013 08:42 |
|
|
|
This link might be helpful: https://forum.stromasys.com/userforum/index.php?t=msg&th=105&start=0&S=abfcd19b842992d137c720b40bc15e7a |
|
|
| Author |
RE: CPU Pegging |
Galen
Member
Posts: 16
Joined: 19.08.13 |
| Posted on August 21 2013 10:57 |
|
|
|
Thank you Bruce, that is exactly the same problem that I have. Unfortunately, the directions used to solve that problem were not posted. |
|
|
| Author |
RE: CPU Pegging |
VolkerHalle
Member
Posts: 104
Location: Germany
Joined: 02.04.10 |
| Posted on August 21 2013 12:07 |
|
|
Galen,
the IDLE code loads an execlet called SYS$IDLE. You can easily check, whether this execlet is loaded in your running OpenVMS System and look at the code:
$ ANAL/SYS
SDA> SHOW EXEC SYS$IDLE
....
[UPDATE]: the following is only true for V8.3 or higher !
SDA> exam/ins SCH$IDLE_CPU_C;40 ! this is IDLE V1.1
SCH$IDLE_CPU_C: SUBQ SP,#X20,SP
SCH$IDLE_CPU_C+00004: STQ R27,(SP)
SCH$IDLE_CPU_C+00008: STQ R26,#X0010(SP)
SCH$IDLE_CPU_C+0000C: STQ FP,#X0018(SP)
SCH$IDLE_CPU_C+00010: BIS R31,SP,FP
SCH$IDLE_CPU_C+00014: BIS R31,#X01,R16
SCH$IDLE_CPU_C+00018: LDQ R26,#X0028(R27)
SCH$IDLE_CPU_C+0001C: LDL R24,(R26)
SCH$IDLE_CPU_C+00020: ADDL R24,#X01,R24
SCH$IDLE_CPU_C+00024: STL R24,(R26)
SCH$IDLE_CPU_C+00028: WTINT
SCH$IDLE_CPU_C+0002C: BIS R31,FP,SP
SCH$IDLE_CPU_C+00030: LDQ R28,#X0010(SP)
SCH$IDLE_CPU_C+00034: LDQ FP,#X0018(SP)
SCH$IDLE_CPU_C+00038: ADDQ SP,#X20,SP
SCH$IDLE_CPU_C+0003C: RET R31,(R28)
SCH$IDLE_CPU_C+00040: HALT
This code is being called via the SCH$IDLE_CPU System routine
SDA> exa sch$idle_cpu;10
FFFFFFFF 80694000 00200000 00103089 .0.... ..@i..... 81A14820
SDA> exa/ins 80694000
SCH$IDLE_CPU_C: SUBQ SP,#X20,SP
This code is loaded during OpenVMS boot, except if NOAUTOCONFIG=1 or bit 0 in LOAD_SYS_IMAGES is cleared.
The problem descriptions are a bit vague regarding 'reboot', they do not always correctly talk about an Emulator restart, an OpenVMS reboot or a complete Windows reboot.
If I understand your problem description correctly, your're saying that an OpenVMS reboot does not make the problem reappear, even an Emulator restart does not trigger the problem, only a Windows reboot causes the problem to reappear. And the problem is '1 core fully utilized by the emulator', although IDLE had been installed.
Volker.
Edited by VolkerHalle on August 22 2013 11:15 |
 |
| Author |
RE: CPU Pegging |
VolkerHalle
Member
Posts: 104
Location: Germany
Joined: 02.04.10 |
| Posted on August 21 2013 12:24 |
|
|
Galen,
I've powered on my Notebook, started FreeAXP v1.0.283 and booted OpenVMS including IDLE V1.2. The Windows CPU/core utilization is about 10-20% for each core.
So something must have changed between 'then' and 'now'.
I don't think OpenVMS changed, but you can now verify, whether IDLE is still loaded.
Volker. |
|
|
| Author |
RE: CPU Pegging |
Galen
Member
Posts: 16
Joined: 19.08.13 |
| Posted on August 21 2013 12:51 |
|
|
Volker, thank you for your help.
My testing yesterday indicated that shutting down the emulator and restarting it did NOT affect the setting of IDLE. Yesterday, rebooting my PC and restarting the emulator caused the CPU to max out on one core.
Today, I do the same test (shutting down the emulator and then restarting VMS), and IDLE is reset (CPU is max on one core) until I re-install the IDLE v1.2. I get the same results with a shutdown and automatic reboot.
Here are the settings you inquired about from my system:
$ mc sysgen
SYSGEN> SHOW NOAUTOCONFIG
Parameter Name Current Default Min. Max. Unit Dynamic
-------------- ------- ------- ------- ------- ---- -------
NOAUTOCONFIG 0 0 0 1 Boolean D
SYSGEN> SHOW LOAD_SYS_IMAGES
Parameter Name Current Default Min. Max. Unit Dynamic
-------------- ------- ------- ------- ------- ---- -------
LOAD_SYS_IMAGES 7 7 0 31 Bitmask
SYSGEN>
$ anal/sys
OpenVMS (TM) system analyzer
SDA> show exec sys$idle
VMS Executive layout
--------------------
Image Base End
Length SymVec
--------------------------------------- ----------------- ----------------- ----
------------- --------
SYS$IDLE FFFFFFFF.85FFC000 FFFFFFFF.86003FFF 0000
0000.00008000
Nonpaged read only FFFFFFFF.85FFC000 FFFFFFFF.85FFC1FF 0000
0000.00000200
Nonpaged read/write FFFFFFFF.86000000 FFFFFFFF.860001FF 0000
0000.00000200
Linked 21-AUG-2013 10:37 LDRIMG 81B91380 --< not sliced >--
SDA> exam/ins SCH$IDLE_CPU_C;40
IMG$RUNDOWN_C: LDQ R27,#X0010(R27)
XQP_STD$UNLOCK_CACHE_C+00004: LDQ R28,#X0008(R27)
XQP_STD$UNLOCK_CACHE_C+00008: JMP R31,(R28)
XQP_STD$UNLOCK_CACHE_C+0000C: LDQ R3,#X0010(R3)
XQP_STD$UNLOCK_CACHE_C+00010: LDQ R2,#X0008(R3)
XQP_STD$UNLOCK_CACHE_C+00014: JMP R31,(R2)
EXE$PROC_CORRECTED_ERROR_C: BIS R3,R31,R6
SCH$PAGEFAULT_C+00004: LDQ R3,#X0010(R3)
SCH$PAGEFAULT_C+00008: LDQ R2,#X0008(R3)
SCH$PAGEFAULT_C+0000C: JMP R31,(R2)
SCH$PAGEFAULT_C+00010: RET R31,(R26)
SCH$PAGEFAULT_C+00014: LDA R0,#X0001(R31)
SCH$PAGEFAULT_C+00018: RET R31,(R26)
SCH$PAGEFAULT_C+0001C: LDA R0,#X0E4A(R31)
SCH$PAGEFAULT_C+00020: RET R31,(R26)
SCH$PAGEFAULT_C+00024: HALT
OTS$BIT_AND_C: SRA R17,#X03,R1
SDA> |
|
|
| Author |
RE: CPU Pegging |
VolkerHalle
Member
Posts: 104
Location: Germany
Joined: 02.04.10 |
| Posted on August 21 2013 13:26 |
|
|
Galen,
while the SYS$IDLE execlet seems to be loaded, it's NOT being called from the SCH$IDLE_CPU Routine. Look at the instruction stream you're seeing when examining SCH$IDLE_CPU_C;40
I'll try to contact the author of the IDLE tool and ask him for a comment.
Volker. |
|
|
| Author |
RE: CPU Pegging |
Galen
Member
Posts: 16
Joined: 19.08.13 |
| Posted on August 21 2013 13:45 |
|
|
Thank you.
I look forward for his opinion on the problem. |
|
|
| Author |
RE: CPU Pegging |
VolkerHalle
Member
Posts: 104
Location: Germany
Joined: 02.04.10 |
| Posted on August 21 2013 23:45 |
|
|
Galen,
could you please provide the console output of the boot (up to the first OPCOM message) of the working and the failing case.
And please also provide the output of PRODUCT SHOW HISTORY.
There are different mechanisms for loading the execlet and connecting it to the idle Loop during boot and during installation. This may explain, why re-installing works, but booting doesn't.
Thanks,
Volker.
Edited by VolkerHalle on August 22 2013 00:32 |
|
|
| Author |
RE: CPU Pegging |
Bruce Claremont
Moderator
Posts: 623
Joined: 07.01.10 |
| Posted on August 22 2013 07:35 |
|
|
|
Doesn't IDLE require that a SYSGEN parameter be set? I don't know which one. |
|
|
| Author |
RE: CPU Pegging |
Galen
Member
Posts: 16
Joined: 19.08.13 |
| Posted on August 22 2013 10:55 |
|
|
$ product show history
----------------------------------- ----------- ----------- --------------------
PRODUCT KIT TYPE OPERATION DATE AND TIME
----------------------------------- ----------- ----------- --------------------
SRI AXPVMS IDLE V1.2 Full LP Install 21-AUG-2013 10:37:54
SRI AXPVMS IDLE V1.2 Full LP Install 21-AUG-2013 10:29:43
SRI AXPVMS IDLE V1.2 Full LP Install 20-AUG-2013 10:05:18
SRI AXPVMS IDLE V1.2 Full LP Install 19-AUG-2013 15:37:19
SRI AXPVMS IDLE V1.2 Full LP Install 19-AUG-2013 13:12:36
SRI AXPVMS IDLE V1.2 Full LP Install 14-AUG-2013 10:36:36
SRI AXPVMS IDLE V1.2 Full LP Install 05-AUG-2013 08:50:53
SRI AXPVMS IDLE V1.2 Full LP Install 31-JUL-2013 11:18:27
SRI AXPVMS IDLE V1.2 Full LP Install 31-JUL-2013 10:37:59
SRI AXPVMS IDLE V1.2 Full LP Install 31-JUL-2013 10:22:03
DEC AXPVMS JAVA150 V1.5-7 Full LP Install 24-MAR-2011 14:15:44
HP AXPVMS SSL V1.4-332 Full LP Install 09-AUG-2010 15:43:57
HP AXPVMS SSL V1.3-281 Full LP Remove 09-AUG-2010 15:43:57
DEC AXPVMS VMS732_UPDATE V14.0 Patch Install 13-MAR-2008 09:32:59
DEC AXPVMS VMS732_UPDATE V13.0 Patch Install 13-MAR-2008 09:08:33
CPQ AXPVMS PERL V5.8-6 Full LP Install 30-AUG-2007 15:09:46
HP AXPVMS SSL V1.3-281 Full LP Install 16-APR-2007 12:44:12
CPQ AXPVMS SSL V1.1-B Full LP Remove 16-APR-2007 12:43:37
DEC AXPVMS VMS732_UPDATE V9.0 Patch Install 05-MAR-2007 12:16:02
DEC AXPVMS VMS732_PCSI V3.0 Patch Install 05-MAR-2007 11:19:37
CPQ AXPVMS SSL V1.1-B Full LP Install 24-JAN-2006 17:38:16
HP AXPVMS SSL V1.2 Full LP Remove 24-JAN-2006 17:36:02
HP AXPVMS SSL V1.2 Full LP Install 24-JAN-2006 16:41:42
CPQ AXPVMS SSL V1.1-A Full LP Remove 24-JAN-2006 16:38:35
DEC AXPVMS VMS732_DRIVER V2.0 Patch Install 22-JUN-2005 14:01:25
DEC AXPVMS VMS732_UPDATE V4.0 Patch Install 22-JUN-2005 13:49:40
DEC AXPVMS TCPIP_ECO V5.4-155 Patch Install 20-JUN-2005 15:50:29
DEC AXPVMS VMS732_LMF V1.0 Patch Install 28-MAR-2005 12:11:31
DEC AXPVMS VMS732_LINKER V1.0 Patch Install 22-FEB-2005 17:04:19
DEC AXPVMS VMS732_DRIVER V1.0 Patch Install 22-FEB-2005 16:36:07
DEC AXPVMS VMS732_RMS V2.0 Patch Install 22-FEB-2005 16:27:10
DEC AXPVMS VMS732_SYS V6.0 Patch Install 22-FEB-2005 16:10:03
DEC AXPVMS VMS732_SYSINI V1.0 Patch Install 22-FEB-2005 15:56:45
DEC AXPVMS VMS732_UPDATE V3.0 Patch Install 22-FEB-2005 15:32:36
DEC AXPVMS VMS732_PCSI V1.0 Patch Install 22-FEB-2005 14:56:32
CPQ AXPVMS SSL V1.1-A Full LP Install 21-APR-2004 09:15:25
CPQ AXPVMS SSL V1.0-A Full LP Remove 21-APR-2004 09:15:25
DEC AXPVMS VMS732_FIBRE_SCSI V2.0 Patch Install 20-APR-2004 16:19:56
DEC AXPVMS VMS732_F11X V1.0 Patch Install 20-APR-2004 16:10:21
DEC AXPVMS VMS732_GRAPHICS V2.0 Patch Install 20-APR-2004 16:00:41
DEC AXPVMS VMS732_DCL V1.0 Patch Install 20-APR-2004 15:55:11
DEC AXPVMS VMS732_LAN V2.0 Patch Install 20-APR-2004 15:44:46
DEC AXPVMS VMS732_MANAGE V1.0 Patch Install 20-APR-2004 15:41:38
DEC AXPVMS VMS732_RPC V1.0 Patch Install 20-APR-2004 15:39:59
DEC AXPVMS VMS732_SYS V2.0 Patch Install 20-APR-2004 15:28:49
DEC AXPVMS VMS732_UPDATE V1.0 Patch Install 20-APR-2004 15:16:57
DEC AXPVMS TCPIP_ECO V5.4-151 Patch Install 20-APR-2004 14:27:42
DEC AXPVMS VMS732_PCSI V1.0 Patch Install 20-APR-2004 14:18:49
CPQ AXPVMS CDSA V2.0-109 Full LP Install 20-APR-2004 11:47:19
DEC AXPVMS DECNET_OSI V7.3-2 Full LP Install 20-APR-2004 11:47:19
DEC AXPVMS DWMOTIF V1.3-1 Full LP Install 20-APR-2004 11:47:19
DEC AXPVMS OPENVMS V7.3-2 Platform Install 20-APR-2004 11:47:19
DEC AXPVMS TCPIP V5.4-15 Full LP Install 20-APR-2004 11:47:19
DEC AXPVMS VMS V7.3-2 Oper System Install 20-APR-2004 11:47:19
HP AXPVMS KERBEROS V2.0-6 Full LP Install 20-APR-2004 11:47:19
CPQ AXPVMS CDSA V1.0-2 Full LP Remove 20-APR-2004 11:47:19
DEC AXPVMS DECNET_OSI V7.3-1 Full LP Remove 20-APR-2004 11:47:19
DEC AXPVMS DWMOTIF V1.2-6 Full LP Remove 20-APR-2004 11:47:19
DEC AXPVMS OPENVMS V7.3-1 Platform Remove 20-APR-2004 11:47:19
DEC AXPVMS TCPIP V5.3-18 Full LP Remove 20-APR-2004 11:47:19
DEC AXPVMS TCPIP_ECO V5.3-182 Patch Remove 20-APR-2004 11:47:19
DEC AXPVMS VMS V7.3-1 Oper System Remove 20-APR-2004 11:47:19
DEC AXPVMS VMS731_ACRTL V1.0 Patch Remove 20-APR-2004 11:47:19
DEC AXPVMS VMS731_BACKUP V1.0 Patch Remove 20-APR-2004 11:47:19
DEC AXPVMS VMS731_DCL V3.0 Patch Remove 20-APR-2004 11:47:19
DEC AXPVMS VMS731_LAN V6.0 Patch Remove 20-APR-2004 11:47:19
DEC AXPVMS VMS731_PCSI V1.0 Patch Remove 20-APR-2004 11:47:19
DEC AXPVMS VMS731_RMS V4.0 Patch Remove 20-APR-2004 11:47:19
DEC AXPVMS VMS731_SYS V3.0 Patch Remove 20-APR-2004 11:47:19
DEC AXPVMS VMS731_UPDATE V1.0 Patch Remove 20-APR-2004 11:47:19
DEC AXPVMS VMS731_XFC V1.0 Patch Remove 20-APR-2004 11:47:19
HP AXPVMS KERBEROS V1.0 Transition Remove 20-APR-2004 11:47:19
HP AXPVMS KERBEROS V1.0 Transition Reg Product 20-APR-2004 10:52:21
HP AXPVMS IA64_XTOOLS X10.27-654951 Full LP Install 14-NOV-2003 10:43:07
HP AXPVMS I64_XTOOLS V8.0 Full LP Remove 14-NOV-2003 10:34:32
DEC AXPVMS VMS731_UPDATE V1.0 Patch Install 31-JUL-2003 16:15:59
DEC AXPVMS VMS731_LAN V6.0 Patch Install 31-JUL-2003 15:36:37
DEC AXPVMS VMS731_XFC V1.0 Patch Install 31-JUL-2003 15:16:42
DEC AXPVMS VMS731_RMS V4.0 Patch Install 31-JUL-2003 15:06:44
DEC AXPVMS VMS731_PCSI V1.0 Patch Install 31-JUL-2003 14:47:19
DEC AXPVMS VMS731_XFC V1.0 Patch Install 10-JUL-2003 09:26:21
DEC AXPVMS VMS731_RMS V4.0 Patch Install 10-JUL-2003 09:25:36
DEC AXPVMS VMS731_DCL V3.0 Patch Install 10-JUL-2003 09:24:50
DEC AXPVMS VMS731_BACKUP V1.0 Patch Install 10-JUL-2003 09:24:11
HP AXPVMS I64_XTOOLS V8.0 Full LP Install 09-JUL-2003 10:56:07
DEC AXPVMS VMS731_ACRTL V1.0 Patch Install 09-JUN-2003 14:00:07
DEC AXPVMS VMS731_SYS V3.0 Patch Install 06-JUN-2003 14:56:40
DEC AXPVMS TCPIP_ECO V5.3-182 Patch Install 30-APR-2003 16:11:27
CPQ AXPVMS SSL V1.0-A Full LP Install 01-NOV-2002 10:05:29
CPQ AXPVMS SSL V1.0 Full LP Remove 01-NOV-2002 10:02:10
CPQ AXPVMS SSL V1.0 Full LP Install 25-OCT-2002 16:01:25
CPQ AXPVMS CDSA V1.0-2 Full LP Install 16-OCT-2002 15:48:38
DEC AXPVMS DECNET_OSI V7.3-1 Full LP Install 16-OCT-2002 15:48:38
DEC AXPVMS DWMOTIF V1.2-6 Full LP Install 16-OCT-2002 15:48:38
DEC AXPVMS OPENVMS V7.3-1 Platform Install 16-OCT-2002 15:48:38
DEC AXPVMS TCPIP V5.3-18 Full LP Install 16-OCT-2002 15:48:38
DEC AXPVMS VMS V7.3-1 Oper System Install 16-OCT-2002 15:48:38
DEC AXPVMS DECNET_OSI V7.2-1 Full LP Remove 16-OCT-2002 15:48:38
DEC AXPVMS DNVOSIECO01 V7.2 Patch Remove 16-OCT-2002 15:48:38
DEC AXPVMS DWMOTIF V1.2-5 Full LP Remove 16-OCT-2002 15:48:38
DEC AXPVMS OPENVMS V7.2-1H1 Platform Remove 16-OCT-2002 15:48:38
DEC AXPVMS TCPIP V5.0-10 Full LP Remove 16-OCT-2002 15:48:38
DEC AXPVMS TCPIP_ECO V5.0-112 Patch Remove 16-OCT-2002 15:48:38
DEC AXPVMS VMS V7.2-1H1 Oper System Remove 16-OCT-2002 15:48:38
DEC AXPVMS VMS721H1_ACRTL V3.0 Patch Remove 16-OCT-2002 15:48:38
DEC AXPVMS VMS721H1_AMACRO V1.0 Patch Remove 16-OCT-2002 15:48:38
DEC AXPVMS VMS721H1_BACKUP V1.0 Patch Remove 16-OCT-2002 15:48:38
DEC AXPVMS VMS721H1_CLIUTL V1.0 Patch Remove 16-OCT-2002 15:48:38
DEC AXPVMS VMS721H1_F11X V2.0 Patch Remove 16-OCT-2002 15:48:38
DEC AXPVMS VMS721H1_FIBRE_SCSI V5.0 Patch Remove 16-OCT-2002 15:48:38
DEC AXPVMS VMS721H1_RMS V8.0 Patch Remove 16-OCT-2002 15:48:38
DEC AXPVMS VMS721H1_RMS V3.0 Patch Remove 16-OCT-2002 15:48:38
DEC AXPVMS VMS721H1_UPDATE V5.0 Patch Remove 16-OCT-2002 15:48:38
DEC AXPVMS VMS721H1_UPDATE V3.0 Patch Remove 16-OCT-2002 15:48:38
DEC AXPVMS VMS721H1_FIBRE_SCSI V5.0 Patch Install 17-SEP-2002 11:53:12
DEC AXPVMS VMS721H1_F11X V2.0 Patch Install 17-SEP-2002 11:52:31
DEC AXPVMS VMS721H1_BACKUP V1.0 Patch Install 17-SEP-2002 11:51:56
DEC AXPVMS VMS721H1_AMACRO V1.0 Patch Install 17-SEP-2002 11:51:21
DEC AXPVMS VMS721H1_RMS V8.0 Patch Install 16-SEP-2002 19:59:37
DEC AXPVMS VMS721H1_ACRTL V3.0 Patch Install 16-SEP-2002 19:58:47
DEC AXPVMS VMS721H1_UPDATE V5.0 Patch Install 16-SEP-2002 19:51:33
DEC AXPVMS TCPIP_ECO V5.0-112 Patch Install 09-APR-2001 09:30:00
DEC AXPVMS VMS721H1_RMS V3.0 Patch Install 29-MAR-2001 10:58:27
DEC AXPVMS VMS721H1_CLIUTL V1.0 Patch Install 29-MAR-2001 10:57:55
DEC AXPVMS VMS721H1_UPDATE V3.0 Patch Install 29-MAR-2001 10:56:54
DEC AXPVMS OPENVMS V7.2-1H1 Platform Install 28-MAR-2001 19:13:46
DEC AXPVMS VMS V7.2-1H1 Oper System Install 28-MAR-2001 19:13:46
DEC AXPVMS OPENVMS V7.2-1 Platform Remove 28-MAR-2001 19:13:46
DEC AXPVMS VMS V7.2-1 Oper System Remove 28-MAR-2001 19:13:46
DEC AXPVMS VMS721_ACRTL V2.0 Patch Remove 28-MAR-2001 19:13:46
DEC AXPVMS VMS721_PCSI V1.0 Patch Remove 28-MAR-2001 19:13:46
DEC AXPVMS VMS721_SYS V5.0 Patch Remove 28-MAR-2001 19:13:46
DEC AXPVMS VMS721_UPDATE V1.0 Patch Remove 28-MAR-2001 19:13:46
DEC AXPVMS JAVA122 V1.2-21 Full LP Install 26-SEP-2000 14:35:39
DEC AXPVMS VMS721_ACRTL V2.0 Patch Install 26-SEP-2000 14:02:53
DEC AXPVMS DNVOSIECO01 V7.2 Patch Install 31-MAY-2000 13:18:43
DEC AXPVMS VMS721_SYS V5.0 Patch Install 25-MAY-2000 21:38:48
DEC AXPVMS VMS721_UPDATE V1.0 Patch Install 25-MAY-2000 21:33:51
DEC AXPVMS VMS721_PCSI V1.0 Patch Install 25-MAY-2000 21:23:45
DEC AXPVMS DECNET_OSI V7.2-1 Full LP Install 20-DEC-1999 18:37:54
DEC AXPVMS DWMOTIF V1.2-5 Full LP Install 20-DEC-1999 18:37:54
DEC AXPVMS OPENVMS V7.2-1 Platform Install 20-DEC-1999 18:37:54
DEC AXPVMS TCPIP V5.0-10 Full LP Install 20-DEC-1999 18:37:54
DEC AXPVMS VMS V7.2-1 Oper System Install 20-DEC-1999 18:37:54
DEC AXPVMS DWMOTIF V1.2-3 Full LP Remove 20-DEC-1999 18:37:54
DEC AXPVMS VMS V6.2 Oper System Remove 20-DEC-1999 18:37:54
DEC AXPVMS UCX V4.1-12 Full LP Remove 20-DEC-1999 16:38:23
DEC AXPVMS UCXECO_41_7 V7.0 Patch Remove 20-DEC-1999 16:38:23
DEC AXPVMS UCXECO_41_8 V8.0 Patch Remove 20-DEC-1999 16:38:23
DEC AXPVMS UCXECO_41_8 V8.0 Patch Install 30-MAR-1998 12:51:33
DEC AXPVMS UCXECO_41_7 V7.0 Patch Install 05-NOV-1997 08:13:03
DEC AXPVMS UCX V4.1-12 Full LP Install 04-NOV-1997 15:15:14
DEC AXPVMS DWMOTIF V1.2-3 Full LP Install 02-SEP-1996 12:14:38
DEC AXPVMS VMS V6.2 Oper System Install 02-SEP-1996 11:35:59
DEC AXPVMS VMS V6.1-1H2 Oper System Remove 02-SEP-1996 11:35:59
DEC AXPVMS NASAXP V5.2 Full LP Install 23-NOV-1994 14:16:05
DEC AXPVMS VMS V6.1-1H2 Oper System Install 23-NOV-1994 11:45:34
----------------------------------- ----------- ----------- --------------------
157 items found
$ |
|
|
| Author |
RE: CPU Pegging |
Galen
Member
Posts: 16
Joined: 19.08.13 |
| Posted on August 22 2013 11:09 |
|
|
This is a failing boot:
┌─┬─┬─┬─┬─┬─┬─┠V i r t u a l serial0
│F│r│e│e│A│X│P│ A l p h a on emulator TRITON (128 M
└─┴─┴─┴─┴─┴─┴─┘ x64 version 2.4.1.502
ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.
ef.df.ee.ed.ec.f4.eb.ea.e9.e8.e7.e6.....e5.
V7.0-9, built on Mar 18 1999 at 13:25:37
>>>b dka0
(boot dka0.0.0.6.0 -flags 0)
block 0 of dka0.0.0.6.0 is a valid boot block
reading 1143 blocks from dka0.0.0.6.0
bootstrap code read in
base = 1f2000, image_start = 0, image_bytes = 8ee00
initializing HWRPB at 2000
initializing page table at 1e4000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
OpenVMS (TM) Alpha Operating System, Version V7.3-2
© Copyright 1976-2003 Hewlett-Packard Development Company, L.P.
%DECnet-I-LOADED, network base image loaded, version = 05.10.00
%SYSINIT-I- waiting to form or join an OpenVMS Cluster
%VMScluster-I-LOADSECDB, loading the cluster security database
%EWA0, Twisted-Pair mode set by console
%EWA0, Link state: UP
%MSCPLOAD-I-CONFIGSCAN, enabled automatic disk serving
%CNXMAN, Sending VMScluster membership request to system VMSIT
%CNXMAN, Now a VMScluster member -- system TRITON
%STDRV-I-STARTUP, OpenVMS startup begun at 22-AUG-2013 09:03:27.48
%MSCPLOAD-I-CONFIGSCAN, enabled automatic disk serving
%RUN-S-PROC_ID, identification of created process is 22E00089
%RUN-S-PROC_ID, identification of created process is 22E0008A
%%%%%%%%%%% OPCOM 22-AUG-2013 09:03:36.79 %%%%%%%%%%%
Operator _TRITON$OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 22-AUG-2013 09:03:36.79 %%%%%%%%%%%
Operator status for operator _TRITON$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 22-AUG-2013 09:03:36.82 %%%%%%%%%%%
Logfile has been initialized by operator _TRITON$OPA0:
Logfile is TRITON::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;23 |
|
|
| Author |
RE: CPU Pegging |
VolkerHalle
Member
Posts: 104
Location: Germany
Joined: 02.04.10 |
| Posted on August 22 2013 11:10 |
|
|
|
Bruce Claremont wrote:
Doesn't IDLE require that a SYSGEN parameter be set? I don't know which one.
OpenVMS V8.3 (V8.2-1 for IA64) or higher use:
Controlled by SYSGEN parameter CPU_POWER_MGMT
and CPU_POWER_THRSH
Volker. |
|
|
| Author |
RE: CPU Pegging |
Galen
Member
Posts: 16
Joined: 19.08.13 |
| Posted on August 22 2013 11:51 |
|
|
Is it necessary to run sys$idle_load.exe everytime the system boots for the CPU to IDLE properly?
The reason I ask is that the last thing that the install does is to link sys$idle_load.exe into pcsi$scratch and then run it. If I run it after boot when the CPU is at max, it brings the CPU back down to normal levels. |
|
|
| Author |
RE: CPU Pegging |
VolkerHalle
Member
Posts: 104
Location: Germany
Joined: 02.04.10 |
| Posted on August 22 2013 12:23 |
|
|
Galen,
there seem to be 2 different methods for loading and activating SYS$IDLE and there are various 'tricks', which need to be used on the different versions of OpenVMS Alpha. Once installed, SYS$IDLE should load and get initialized automatically during boot.
As you've extracted and analyzed the files from the PCSI kit and have found a workaround for yourself, go ahead and use it.
There should still be a real solution. The author of the IDLE kit will try to diagnose and solve the problem. Just be patient ;-)
Volker.
Edited by VolkerHalle on August 22 2013 12:24 |
|
|
| Author |
RE: CPU Pegging |
Jur van der Burg
Member
Posts: 4
Joined: 22.08.13 |
| Posted on August 22 2013 12:51 |
|
|
Ok, let me jump in (as I wrote idle).
You probably have a file named vms$system_images.data in sys$specific:[sys$ldr] which does not belong there.
If that's not the case not then please do this and post the output:
$ dump/block=count=2 sys$common:[sys$ldr]vms$system_images.data
If you run sys$idle_load (which is there in the kit just to load the execelet and avoid a rboot after installation) and it works fine after that then it means that it's just not loaded at boot time, and the file above is critical for that.
Jur.
|
|
|
| Author |
RE: CPU Pegging |
Galen
Member
Posts: 16
Joined: 19.08.13 |
| Posted on August 22 2013 13:04 |
|
|
Hi Jur. Thank you for your help.
$ dir sys$specific:[sys$ldr]
%DIRECT-W-NOFILES, no files found
$ dump/block=count=2 sys$common:[sys$ldr]vms$system_images.data
Dump of file SYS$COMMON:[SYS$LDR]VMS$SYSTEM_IMAGES.DA on 22-AUG-2013 10:56:31.07
TA;18
File ID (48210,1,0) End of file block 69 / Allocated 69
Virtual block number 1 (00000001), 512 (0200) bytes
00000000 00000000 00000000 00000000 ................ 000000
00000000 00000000 00000000 00000000 ................ 000010
00000000 00000000 00000000 00000000 ................ 000020
00000000 00000000 00000000 00000000 ................ 000030
00000000 00000000 00000000 00000000 ................ 000040
00000000 00000000 00000000 00000000 ................ 000050
00000000 00000000 00000000 00000000 ................ 000060
00000000 00000000 00000000 00000000 ................ 000070
00000000 00000000 00000000 00000000 ................ 000080
00000000 00000000 00000000 00000000 ................ 000090
00000000 00000000 00000000 00000000 ................ 0000A0
00000000 00000000 00000000 00000000 ................ 0000B0
00000000 00000000 00000000 00000000 ................ 0000C0
00000000 00000000 00000000 00000000 ................ 0000D0
00000000 00000000 00000000 00000000 ................ 0000E0
00000000 00000000 00000000 00000000 ................ 0000F0
00000000 00000000 00000000 00000000 ................ 000100
00000000 00000000 00000000 00000000 ................ 000110
00000000 00000000 00000000 00000000 ................ 000120
00000000 00000000 00000000 00000000 ................ 000130
00000000 00000000 00000000 00000000 ................ 000140
00000000 00000000 00000000 00000000 ................ 000150
00000000 00000000 00000000 00000000 ................ 000160
00000000 00000000 00000000 00000000 ................ 000170
00000000 00000000 00000000 00000000 ................ 000180
00000000 00000000 00000000 00000000 ................ 000190
00000000 00000000 00000000 00000000 ................ 0001A0
00000000 00000000 00000000 00000000 ................ 0001B0
00000000 00000000 00000000 00000000 ................ 0001C0
00000000 00000000 00000000 00000000 ................ 0001D0
00000000 00000000 00000000 00000000 ................ 0001E0
00000000 00000000 00000000 00000000 ................ 0001F0
Dump of file SYS$COMMON:[SYS$LDR]VMS$SYSTEM_IMAGES.DA on 22-AUG-2013 10:56:31.07
TA;18
File ID (48210,1,0) End of file block 69 / Allocated 69
Virtual block number 2 (00000002), 512 (0200) bytes
00000000 00000000 00000000 00000000 ................ 000000
00000000 00000000 00000000 00000000 ................ 000010
00000000 00000000 00000000 00000000 ................ 000020
00000000 00000000 00000000 00000000 ................ 000030
00000000 00000000 00000000 00000000 ................ 000040
00000000 00000000 00000000 00000000 ................ 000050
00000000 00000000 00000000 00000000 ................ 000060
00000000 00000000 00000000 00000000 ................ 000070
00000000 00000000 00000000 00000000 ................ 000080
00000000 00000000 00000000 00000000 ................ 000090
00000000 00000000 00000000 00000000 ................ 0000A0
00000000 00000000 00000000 00000000 ................ 0000B0
00000000 00000000 00000000 00000000 ................ 0000C0
00000000 00000000 00000000 00000000 ................ 0000D0
00000000 00000000 00000000 00000000 ................ 0000E0
00000000 00000000 00000000 00000000 ................ 0000F0
00000000 00000000 00000000 00000000 ................ 000100
00000000 00000000 00000000 00000000 ................ 000110
00000000 00000000 00000000 00000000 ................ 000120
00000000 00000000 00000000 00000000 ................ 000130
00000000 00000000 00000000 00000000 ................ 000140
00000000 00000000 00000000 00000000 ................ 000150
00000000 00000000 00000000 00000000 ................ 000160
00000000 00000000 00000000 00000000 ................ 000170
00000000 00000000 00000000 00000000 ................ 000180
00000000 00000000 00000000 00000000 ................ 000190
00000000 00000000 00000000 00000000 ................ 0001A0
00000000 00000000 00000000 00000000 ................ 0001B0
00000000 00000000 00000000 00000000 ................ 0001C0
00000000 00000000 00000000 00000000 ................ 0001D0
00000000 00000000 00000000 00000000 ................ 0001E0
00000000 00000000 00000000 00000000 ................ 0001F0
$ |
|
|
| Author |
RE: CPU Pegging |
Jur van der Burg
Member
Posts: 4
Joined: 22.08.13 |
| Posted on August 22 2013 13:10 |
|
|
Ok so there's the problem, there's no info for the vms loader at boot time to load the execlet.
Do this:
$ mc sysman sys_loadable add idle sys$idle
$ @sys$update:vms$system_images
This sequence is normally done by the installation procedure.
That should fix the issue unless you get errors doing the above. If you get errors then post what you got.
Jur.
|
|
|
| Author |
RE: CPU Pegging |
Galen
Member
Posts: 16
Joined: 19.08.13 |
| Posted on August 22 2013 13:13 |
|
|
$ mc sysman sys_loadable add idle sys$idle
%SYSMAN-I-NODERR, error returned from node TRITON
-SMI-E-IMGDUPINV, Image SYS$IDLE for product IDLE already in images table
$ @sys$update:vms$system_images
-SYS-I-NULL, building null system loadable images data file
$ |
|
|
| Author |
RE: CPU Pegging |
Jur van der Burg
Member
Posts: 4
Joined: 22.08.13 |
| Posted on August 22 2013 13:27 |
|
|
sysman attempts to enter the data in this file:
$ analyze/rms sys$update:vms$system_images.idx
$ dump/record sys$update:vms$system_images.idx
The command procedure creates sys$common:[sys$ldr]vms$system_images.data from the .idx file, and since that file is empty there's an issue with the .idx file.
Jur.
|
|
|
