(Subsystem 98)(Continued) [ MPE/iX Error Messages Manual Volume II ] MPE/iX 5.5 Documentation
MPE/iX Error Messages Manual Volume II
(Subsystem 98)(Continued)
------------------------------------------------------------
1115 MESSAGE The MEMORY MANAGER detected an error while trying
to set up an I/O request entry.
-------------------------------------------------------------
1116 MESSAGE The MEMORY MANAGER detected an error while trying
to identify a block of contiguous physical pages.
-------------------------------------------------------------
1117 MESSAGE The MEMORY MANAGER was not able to GET a MIB for
this request.
-------------------------------------------------------------
1118 MESSAGE The MEMORY MANAGER detected an error while trying
to kick out a block of contiguous physical pages.
-------------------------------------------------------------
1119 MESSAGE The MEMORY MANAGER was unable to add an entry to
the I/O notification queue.
-------------------------------------------------------------
1120 MESSAGE A block of contiguous physical memory was
requested for virtual pages which were not virgin.
-------------------------------------------------------------
1121 MESSAGE The MEMORY MANAGER was unable to allocate an I/O
notification queue entry.
-------------------------------------------------------------
1122 MESSAGE The MEMORY MANAGER was unable to set up an I/O
INFO entry.
-------------------------------------------------------------
1123 MESSAGE The MEMORY MANAGER received an error when writing
a page to secondary storage.
-------------------------------------------------------------
1124 MESSAGE The MEMORY MANAGER received an error when it
attempted to RECEIVE from its I/O notification
port.
-------------------------------------------------------------
1125 MESSAGE A block of physical pages which the MEMORY
MANAGER tried to make memory-resident contained a
page which was not present.
-------------------------------------------------------------
1126 MESSAGE The critical PAGE POOL is empty.
-------------------------------------------------------------
1127 MESSAGE The MEMORY MANAGER was unable to REPLENISH the
critical PAGE POOL.
-------------------------------------------------------------
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.
-------------------------------------------------------------
MPE/iX 5.5 Documentation