HP 3000 Manuals HP 3000 Manuals
(Subsystem 98) (contd.)
1128 MESSAGE The MEMORY MANAGER received an error when it
attempted to RECEIVE from its I/O notification
port.
---------------------------------------------------------------
1129 MESSAGE The MEMORY MANAGER could not find a
memory-resident PAGE entry in the PDIRX.
---------------------------------------------------------------
1130 MESSAGE The MEMORY MANAGER could not find a
memory-resident PAGE entry in the PDIRX.
---------------------------------------------------------------
1131 MESSAGE The MEMORY MANAGER was unable to get a PDIR entry
from TABLE MANAGEMENT.
---------------------------------------------------------------
1132 MESSAGE Inserting an entry at the head of a chain in the
KO HASH TABLE is the only supported method.
---------------------------------------------------------------
1133 MESSAGE Inserting an entry at the head of a chain in the
PSEUDO PRESENT HASH TABLE is the only supported
method.
---------------------------------------------------------------
1134 MESSAGE The MEMORY MANAGER was unable to lock the PDIRX
when attempting to CHANGE a page to a recoverable
overlay candidate.
---------------------------------------------------------------
1135 MESSAGE A user-requested WRITE is in progress on a stack
page above SP.
---------------------------------------------------------------
1136 MESSAGE An error was detected while trying to send a
message to the MEMORY MANAGER PAGE filler port.
---------------------------------------------------------------
1137 MESSAGE The MEMORY MANAGER detected an error while trying
to get a clean page to add to the filled page pool.
---------------------------------------------------------------
1138 MESSAGE An error was detected whie trying to RECEIVE a
message from the MEMORY MANAGER PAGE filler port.
---------------------------------------------------------------
1139 MESSAGE The MEMORY MANAGER was unable to LOCK to PDIRX.
---------------------------------------------------------------
1140 MESSAGE The MEMORY MANAGER detected an error while
attempting to WRITE pages to secondary storage.
---------------------------------------------------------------
1141 MESSAGE The MEMORY MANAGER can not find a page which has
not been referenced since the last traverse of
physical memory.
---------------------------------------------------------------
1142 MESSAGE The MEMORY MANAGER was unable to LOCK the PDIRX.
---------------------------------------------------------------
1143 MESSAGE The MEMORY MANAGER was unable to LOCK the PDIRX.
---------------------------------------------------------------
1144 MESSAGE The MEMORY MANAGER encountered a STACK OVERFLOW
while trying to handle a STACK OVERFLOW condition.
---------------------------------------------------------------
1145 MESSAGE The MEMORY MANAGER was unable to ADD a page to a
process's minimum locality.
---------------------------------------------------------------
1146 MESSAGE The MEMORY MANAGER detected an error while trying
to get PLABEL information about a system entry
point.
---------------------------------------------------------------
1147 MESSAGE The MEMORY MANAGER was unable to CREATE an object
in the safe stack.
---------------------------------------------------------------
1148 MESSAGE The MEMORY MANAGER was unable to lock an object
in the safe stack.
---------------------------------------------------------------
1149 MESSAGE The MEMORY MANAGER attempted to MAP in a VIRGIN
page which was already in the process of being
mapped in from secondary storage.
---------------------------------------------------------------
1150 MESSAGE The TOS of STACK POINTER (SP) is not
word-aligned.
---------------------------------------------------------------
1151 MESSAGE The MEMORY MANAGER was unable to FREEZE pages in
the SAFE stack.
---------------------------------------------------------------
1152 MESSAGE The MEMORY MANAGER was unable to release an
object from the SAFE stack.
---------------------------------------------------------------
1153 MESSAGE A PAGE fault which was no a TOS trap occurred
while interrupts were disabled.
---------------------------------------------------------------
1154 MESSAGE A PAGE fault occurred while the DISABLED TOS trap
count was nonzero.
---------------------------------------------------------------
1156 MESSAGE The MEMORY MANAGER was unable to get an entry
from the GREY PAGE TABLE.
---------------------------------------------------------------
1157 MESSAGE The physical PAGE POOL used for mapping in TOS
pages was empty.
---------------------------------------------------------------
1158 MESSAGE The MEMORY MANAGER was unable to get an entry
from the GREY PAGE TABLE.
---------------------------------------------------------------
1159 MESSAGE A virtual page which should have been frozen in
memory was found to be absent.
---------------------------------------------------------------
1160 MESSAGE The MEMORY MANAGER was unable to LOCK a portion
of the process stack in the VPN cache.
---------------------------------------------------------------
1161 MESSAGE The MEMORY MANAGER was unable to get a valid
PLABEL from the loader.
---------------------------------------------------------------
1163 MESSAGE FETCH pages could not obtain the resources that
it needs.
---------------------------------------------------------------
1164 MESSAGE FETCH PAGES out of service clean up has detected
an inconsistency.
---------------------------------------------------------------
1165 MESSAGE An attempt was made to FREEZE a virtual page
which was not mapped into physical memory.
---------------------------------------------------------------
1166 MESSAGE An attempt was made to UNFREEZE a virtual page
which was not mapped into physical memory.
---------------------------------------------------------------
1167 MESSAGE The MEMORY MANAGER either was given a bad
locality list entry number, or found a bad entry in
the locality list.
---------------------------------------------------------------
1168 MESSAGE The MEMORY MANAGER's semaphore for this page is
already locked. This should not occur in a
uni-processor environment.
---------------------------------------------------------------
1169 MESSAGE A frozen page is absent.
---------------------------------------------------------------
1170 MESSAGE A frozen page is absent.
---------------------------------------------------------------
1171 MESSAGE An uninitialized semaphore is used in a lock
request.
---------------------------------------------------------------
1172 MESSAGE An attempt was made to lock the stack below the
currently locked area.
---------------------------------------------------------------
1174 MESSAGE We were asked to map in a page for a page that
was present.
---------------------------------------------------------------
1175 MESSAGE If we force a KO page absent, it should have a
present version.
---------------------------------------------------------------
1176 MESSAGE An error was detected in changing from VPS to KO.
---------------------------------------------------------------
1177 MESSAGE The PDIRX entry could not be locked.
---------------------------------------------------------------
1178 MESSAGE SEND MESSAGE failed in background posts.
---------------------------------------------------------------
1179 MESSAGE A bug occurred in stale page bug catcher.
---------------------------------------------------------------
1180 MESSAGE Page VP state detected in CHANGE VPS STATE.
---------------------------------------------------------------
1181 MESSAGE MM_TT_ZERO_VALUED_FIRST_INTERRUPT_MKR for MEMORY
MANAGER.
CAUSE First CM interrupt marker in TCB is set to zero.
---------------------------------------------------------------
1300 MESSAGE The procedure CREATE_PROCESS_SWITCH_OBJ is unable
to create process SWITCH OBJECT.
CAUSE Unable to create an object for the CM procedure
name to the plabel table.
---------------------------------------------------------------
1301 MESSAGE The procedure CREATE_PROCESS_SWITCH_OBJ is unable
to create HASH TABLE.
CAUSE Unable to create the CM procedure name to the
plabel table.
---------------------------------------------------------------
1302 MESSAGE The procedure ALLOCATE_CM_PROCEDURE received bad
status from SWITCH_TO_CM.
CAUSE SWITCH_TO_CM could not call LOADPROC.
---------------------------------------------------------------
1303 MESSAGE The procedure DEALLOCATE_CM_PROCEDURE received
bad status from SWITCH_TO_CM.
CAUSE SWITCH_TO_CM could not call UNLAODPROC.
---------------------------------------------------------------
1304 MESSAGE The procedure DELETE_SCM_HASH_ENTRY failed to
find entry.
CAUSE Could not find a name in the CM procedure name to
plabel table.
---------------------------------------------------------------
1305 MESSAGE The procedure DELETE_SCM_HASH_ENTRY received bad
status from RELEASE_TABLE_ENTRY.
CAUSE A table management error occured while releasing a
table entry in the CM procedure to the plabel
table.
---------------------------------------------------------------
1306 MESSAGE The procedure GET_PROCESS_SCM_PLABEL received bad
status from RELEASE_TABLE_ENTRY.
CAUSE A table management error occured while releasing a
table entry in the CM procedure name to the plabel
table.
---------------------------------------------------------------
1307 MESSAGE The procedure SWITCH_TO_CM received bad status
from RELDATSEG.
CAUSE Unable to release a data segment previously created
in SWITCH_TO_CM.
---------------------------------------------------------------
1320 MESSAGE TIMER entry had an illegal state.
---------------------------------------------------------------