Google
 

Trailing-Edge - PDP-10 Archives - AP-4178E-RM - swskit-binaries/11bugstrings.txt
There are no other files named 11bugstrings.txt in the archive.


CRASH   MODULE  MEANING
CODE


BF1     QPRDTE  BUFFER FAILURE 1
                ATTEMPT TO OBTAIN BUFFER SPACE FOR  THE  TO-11  PROTOCOL
                HEADER FAILED.
                POSSIBLE CAUSE:  BUFFER POOL SPACE HAS BECOME  EXHAUSTED
                OR HIGHLY FRAGMENTED.  R1 CONTAINS THE NODE(BUFFER) SIZE
                REQUESTED.  .FREPL POINTS TO THE  LIST  OF  FREE  NODES.
                NODES  ARE  LINKED  TOGETHER  IN  THE  FORWARD DIRECTION
                THROUGH THE FIRST WORD OF THE NODE.  THE SECOND WORD  OF
                EACH NODE CONTAINS THE NODE SIZE.


B02     QPRDTE  BUFFER OVERFLOW 2
                THE -11 WAS NOT ABLE TO OBTAIN THE BUFFER SPACE REQUIRED
                TO RECEIVE AN INDIRECT DATA TRANSFER FROM THE -10.
                POSSIBLE CAUSE:  SAME AS BF1 ABOVE.


B03     QPRDTE  BUFFER OVERFLOW 3
                THE -11 WAS NOT ABLE TO OBTAIN THE BUFFER SPACE
                NECESSARY FOR DATA IT WANTS TO SEND TO THE -10.  AN
                ATTEMPT TO GET 30(8) BYTES FAILED.
                POSSIBLE CAUSE:  SAME AS BF1 ABOVE.


CBR     PF      CROBAR ERROR.
                DTE-20 POWER HAS NOT RETURNED AFTER A POWER- FAIL
                RESTART.  RSX-20F ALLOWS IT 30 SECONDS TO RE-APPEAR.
                POSSIBLE CAUSE:  MALFUNCTIONING HARDWARE IN THE KL10.


DTB     QPRDTE  TO-11 DTE TRANSFER FAILURE
                A TO-11 DONE INTERRUPT HAS OCCURRED BUT THE TO-11
                ADDRESS IN THE DTE TO11AD REGISTER (REGISTER 22) DID NOT
                HAVE THE EXPECTED VALUE.  SINCE TO11AD GETS INCREMENTED
                FOR EACH BYTE TRANSFERRED, IT SHOULD POINT TO THE FIRST
                WORD FOLLOWING THE BUFFER INTO WHICH THE TO-11 DATA WAS
                WRITTEN.
                POSSIBLE CAUSE:  THE -11 RECEIVED THE WRONG BYTE COUNT
                OR ,MORE LIKELY, THE DTE HAS A HARDWARE MALFUNCTION.
                TO11BC CONTAINS THE NEGATIVE COUNT OF DATA TRANSFERRED.
                TO11AS CONTAINS ADDRESS OF DATA NODE.  R1 CONTAINS
                EXPECTED TERMINATION ADDRESS AND CR$DTB-2 CONTAINS THE
                ACTUAL TERMINATION ADDRESS FOR TRANSFER.


DTF     QPRDTE  TO-10 DTE TRANSFER FAILURE
                A TO-10 DONE INTERRUPT HAS OCCURRED BUT THE TO-10
                ADDRESS IN THE DTE TO10AD REGISTER (REGISTER 20) DID NOT
                HAVE THE EXPECTED VALUE.  SINCE TO10AD GETS INCREMENTED
                FOR EACH BYTE TRANSFERRED, IT SHOULD POINT TO THE FIRST
                WORD FOLLOWING THE PACKET WHICH WAS SENT TO THE 10.
                                                                  Page 2


                POSSIBLE CAUSE:  THE -11 GAVE THE -10 THE WRONG BYTE
                COUNT OR, MORE LIKELY, THE DTE HAS A HARDWARE
                MALFUNCTION.  TO10SZ CONTAINS THE SIZE OF TRANSFER AND
                TO10AS THE START ADDRESS.  THE EXPECTED TERMINATION
                ADDRESS IS IN R4.


ETE     QPRDTE  TO -11 TRANSFER ERROR
                A DTE INTERRUPT OCCURRED WITH THE TO11ER BIT SET IN THE
                DTE STATUS REGISTER( REGISTER 34).
                POSSIBLE CAUSE:  HARDWARE MALFUNCTION ALONG THE DATA
                PATH BETWEEN THE -10 AND -11(M-BOX, E-BOX, E-BUS,
                DTE-20, THROUGH TO 11-MEMORY).


FTA     LC      FILES-11 TASK ABORTED
                A TASK OCCUPYING F11TPD PARTITION HAS ABORTED AND THE
                TASK TERMINATION NOTIFICATION TASK (TKTN) CANNOT BE
                STARTED SINCE IT TOO RUNS IN THE F11TPD PARTITION.
                POSSIBLE CAUSE:  .TKTN ITSELF ABORTED.  R5 AND .CRTSK
                POINT TO THE ACTIVE TASK LIST (ATL) NODE OF THE ABORTED
                TASK.


IAS     SCH     UNKNOWN SIGNIFICANT EVENT
                AN UNUSED BIT IN .SERFG HAS BEEN SET
                POSSIBLE CAUSE:  PDP11 HARDWARE MALFUNCTION OR CORRUPTED
                SOFTWARE IN PDP11.  .SERFG HAS THE BIT SET.


ILF     QPRDTE  ILLEGAL PROTOCOL FUNCTION 
                THE FUNCTION CODE IN A TO-11 PROTOCOL HEADER SPECIFIED A
                FUNCTION WHICH IS OUTSIDE THE LEGAL RANGE OR WHICH IS
                CURRENTLY UNIMPLEMENTED.
                POSSIBLE CAUSE:  -10 SOFTWARE IS CORRUPTED OR HARDWARE
                MALFUNCTION ALONG DATA PATH BETWEEN -10 AND -11.  R1
                CONTAINS THE FUNCTION CODE *2 AND R0,R4 CONTAIN THE
                ADDRESS OF THE PROTOCOL HEADER.


ILQ     QPRDTE  ILLEGAL QUEUE COUNT
                THE -10 AND THE -11 DISAGREE ON THE NUMBER OF DIRECT
                TRANSFERS THAT HAVE THUS FAR TAKEN PLACE FROM THE -10 TO
                THE -11.
                POSSIBLE CAUSE:  THE -11 IS MISSING TO-11 DOORBELL
                INTERRUPTS OR EITHER THE -10 OR -11 SOFTWARE IS
                CORRUPTED.  STATI+0 TO STATI+2 CONTAIN THE -10'S TO-11
                STATUS WORD AS READ BY RSX20F AT THE LAST EXAMINE.
                STATI+4 IS THE COUNT AS THE -10 EXPECTS IT AND TO10QC IS
                THE COUNT AS THE -11 EXPECTS IT.


LRF     SCH     LOAD REQUEST FAILURE.
                AN ATTEMPT TO LOAD A NON-RESIDENT MONITOR ROUTINE INTO
                THE F11TPD PARTITION FAILED.
                                                                  Page 3


                POSSIBLE CAUSE:  THE FILES-11 SYSTEM IS INCOMPLETE OR
                DAMAGED.


MPE     LC      MEMORY PARITY ERROR
                A MEMORY PARITY ERROR HAS OCCURRED IN THE PDP11 (TRAP TO
                LOCATION 114).  THE MEMORY STATUS REGISTERS ARE STORED
                STARTING AT LOCATION PARSAV.  SEE PROCESSOR HANDBOOK FOR
                DETAILS.


PT1     QPRDTE  PROTOCOL BROKEN
                AN ILLEGAL PROTOCOL DEVICE NUMBER WAS SPECIFIED IN A TO
                -11 REQUEST.  IT WAS FOUND TO BE GREATER THAN THE
                MAXIMUM ALLOWED DEVICE NUMBER .DQPSZ (CURRENTLY 10)
                POSSIBLE CAUSE:  -10 SOFTWARE IS CORRUPTED OR HARDWARE
                MALFUNCTION ALONG THE DATA PATH BETWEEN THE -10 AND -11.
                THE DEVICE NUMBER FROM THE PROTOCOL HEADER IS IN TO11DV.


PT2     QPRDTE  PROTOCOL ERROR 2
                AN ILLEGAL PROTOCOL FUNCTION WAS SPECIFIED IN A TO -11
                REQUEST.  THE FUNCTION WAS FOUND TO BE GREATER THAN THE
                ALLOWED MAXIMUM BC.FNM (CURRENTLY 34).
                POSSIBLE CAUSE:  SAME AS PT1 ABOVE.  THE FUNCTION CODE
                FROM THE PROTOCOL HEADER IS IN TO11FN.


PT3     QPRDTE  PROTOCOL ERROR 3
                THE -11 HAS RECEIVED A DOORBELL INTERRUPT FROM THE -10.
                THE INDIRECT BIT IN THE -10'S TO-11 STATUS WORD
                INDICATES THAT AN INDIRECT TRANSFER IS TO BE INITIATED.
                THE FUNCTION CODE HOWEVER SENT IN THE LAST PROTOCOL
                HEADER DOES NOT INDICATE THAT AN INDIRECT REQUEST IS IN
                PROGRESS (THE MOST SIGNIFICANT BIT OF THE FUNCTION CODE
                WAS NOT SET).
                POSSIBLE CAUSE:  SAME AS PT1 ABOVE.  TO11FN CONTAINS THE
                FUNCTION CODE AND STATI CONTAINS THE -10'S TO-11
                PROTOCOL STATUS WORD.


PT4     QPRDTE  PROTOCOL ERROR 4
                THE -10 WANTS TO SEND A PACKET TO THE -11 WHOSE SIZE IS
                GREATER THAN THE MAXIMUM ALLOWED SIZE OF 100(10).
                POSSIBLE CAUSE:  SAME AS PT1 ABOVE THE SIZE IS IN EQSZ.


RES     LC      RESERVED INSTRUCTION TRAP
                THIS IS THE PDP11 TRAP TO LOCATION 10.  AN ATTEMPT WAS
                MADE TO EXECUTE AN ILLEGAL OR RESERVED INSTRUCTION.  SEE
                THE PDP11 PROCESSOR HANDBOOK FOR FURTHER DETAILS.
                POSSIBLE CAUSE:  -11 SOFTWARE IS CORRUPTED OR THERE IS A
                PDP11 HARDWARE MALFUNCTION.
                                                                  Page 4


T04     LC      TRAP AT LOCATION 4
                THE PDP-11 TRAPS TO LOCATION 4 WHEN MAKING A WORD
                REFERENCE TO AN ODD ADDRESS OR AT THE OCCURRENCE OF A
                BUS TIMEOUT.  SEE THE PDP11 PROCESSOR HANDBOOK FOR
                FURTHER DETAILS.
                POSSIBLE CAUSE:  -11 SOFTWARE IS CORRUPTED, OR A PDP11
                PERIPHERAL DEVICE IS MALFUNCTIONING OR HAS GONE AWAY.


TBT     LC      T-BIT TRAP
                THIS IS THE PDP11 TRAP TO LOCATION 14.  IT OCCURS WHEN
                THE BPT INSTRUCTION (NOT USED BY RSX-20F) IS EXECUTED OR
                WHEN THE T-BIT IS SET.  SEE THE PDP11 PROCESSOR HANDBOOK
                FOR FURTHER DETAILS.
                POSSIBLE CAUSE:  CORRUPTED -11 SOFTWARE OR PDP11
                HARDWARE MALFUNCTION.


TET     QPRDTE  T0-10-TRANSFER ERROR,
                A DTE INTERRUPT HAS OCCURRED WITH EITHER TO10ER (TO-10
                ERROR) OR MPE11 (-11 PARITY ERROR)BIT SET IN THE DTE-20
                STATUS REGISTER( REGISTER 34)
                POSSIBLE CAUSE:  DTE HARDWARE ERROR, PDP11 MEMORY PARITY
                ERROR, OR HARDWARE MALFUNCTION ALONG THE DATA PATH
                BETWEEN THE -11 AND -10.


UIE     QPRDTE  UNIMPLEMENTED PROTOCOL FUNCTION
                THE -10 USES BITS 0-2 OF ITS TO-11 STATUS WORD IN THE
                COMM-REGION TO INFORM THE FRONT END OF ANY DISASTER
                OCCURRING IN THE KL.  THESE BITS ARE READ BY THE FRONT
                END ON RECEIPT OF A TO-11 DOORBELL.  THE CURRENTLY
                IMPLEMENTED FUNCTIONS ARE KL-RELOAD REQUEST AND KL POWER
                FAIL.  ANY OTHER SET BITS CAUSE THIS HALT.
                POSSIBLE CAUSE:  CORRUPTED -10 SOFTWARE, -10 HARDWARE
                MALFUNCTION OR ANY HARDWARE MALFUNCTION ALONG DATA PATH
                BETWEEN -10 AND -11.