XEROX1108 Users Guide51SECTION 8MP CODE SUMMARYThere are two types of Maintenance Panel codes: progress codes and error codes. Progresscodes are placed in the Maintenance Panel at various stages of initialization. Error codes aretraps which freeze or blink the error number in the maintenance panel. All errors except the9000-range errors are fatal.All MP codes less than 9000 are generated by non-Lisp programs implemented directly inmicrocode or in Mesa, a high-level programming language in use at Xerox. MP codes from 9000to 9999 are generated by an error in the Lisp system code.Summary of MP code rangesBlank MP to 0099: Preboot diagnostics03000399Boot diagnostics06000699Memory diagnostics04000499Utility (Real time clock, etc.) diagnostics07000799Disk diagnostics (written in microcode)09000999Pilot OS 10001199Disk Fault Analysis (10MB)13001499Disk Fault Analysis (42MB)16001799Disk Fault Analysis (29MB)88888888MP lamp test90009999LispBoot-time errors0096Insufficient real memory (<1MByte) for Lisp0149Usually right after power-on. Disk not ready. Safe and effective to 0-boot fromthis state.0200-0299 Booting phase 2 (Initial microcode)0200Normal booting phase 20201CP error in reading from boot device0202Null Mesa germ installed in physical volume0203Broken rigid disk boot chain (possibly intermittent)0204Illegal IOP port command0205CP Trap (CS parity or double-bit memory error) gdpXq@p gd*?dF*j)p(;]s$[ gV(pL gS L gQ'1 gO  gK@ gI|S gGH8 gClsC?p&C=\/C;(/C8/+C6/'C4/C2X/C0$/C-/C+/ C)/ g%sC#1pS+C S;SV gzs-CpSCS$CS+CcS4C/SC S.TVk( XEROX1108 Users Guide520206Null diagnostic microcode in physical volume0207Null Pilot/Mesa emulator microcode in physical volume0208Null Mesa germ installed in physical volume0217Inconsistent Virtual Memory. Requires reinstallation or try another partition.0500-0502 Domino progress codes0500StartDominoDomino has started0501InitReadTODDomino starting to read the TOD clock0502InitReadTODdoneReading of TOD clock completed (next MP number fromLisp)0505-0599 Domino error codes0505CSParityCS parity error detected0506BurdockCPDisabledBurdock attempted to use EtherKludge0507CPBurdockDisabledCP attempted to use EtherKludge0508IOPBreakAn IOP break with no IOP kernel0509IllegalIOPIntrIllegal IOP interrupt0510BadMapEntryIncorrect vm Map entry in IOP access.0511NoCPDmaCompleteCP Dma operation failed to complete0512NoCPDmaChannelCP Dma channel not specified0513ReadCPPortDeadCP not responding to Read CPPort0514WriteCPPortDeadCP not responding to Write CPPort0520StackOverflowA task's stack has overflowed0565InvToneCmdInvalid keyboard tone generator command0570InvProcCmdInvalid command value in Processor CSB0571UnImplCmdUnimplemented command in Processor CSB0572SetTODErrorThe Time-Of-Day could not be set 0576LSEPCtlOVRLSEP Control CSB overrun0580NoValidCommandInvalid floppy IOCB command0581UnImplFloppyCmdUnimplemented floppy IOCB command0582InvalidEscapeCmdInvalid Escape floppy command0583CommandTrackFloppy track register is not correct0584TrackToBigFloppy track number is too large0585BadDmaChannelCouldn't program Floppy Dma0586NoDmaEndCount1External Dma End Count not set0587NoDmaEndCount2Internal Dma End Count not set gdpXq@p gd*?dF*j)pC]S(C[S5CYwS+CWCSO gSgsCPp9 $CN9 $%CL9$$J gGsCDp9$CBR9$$C@9$C=9$C;9 $C99 $%C7N9$#C59 $C29 $C09$!C.~9 $C,J9 $'C*9 $&C'9$&C%9 $!C#z9 $C!F9 $C9$!C9$C9 $$Cv9 $CB9 $C9 $C9 $bTVk( XEROX1108 Users Guide530900-0999 Pilot codes0915Pilot breakpoint.If 0915 occurs during the installation of the software, theproblem could be a bad page on the rigid disk, the systemcannot read the floppy disk, or a hardware failure. Tryrunning ALAG. If ALAG passes and Media Scan shows nonew bad pages, the floppy disk (software installation) issuspect.0937Trying to find outthe time and date.Will hang in this state if no time server is responding, andthe time has not been set on the machine since power-up.Time can be set from within Interlisp (with SETTIME), by 2-booting the Installation Utility floppy, or by 5-booting the EIFixed Disk Diagnostics floppy.)0981Trying to discoverEthernet Pup hostnumber.Will hang in this state if non-Lisp code tries to perform Pupoperations and no Pup ID Server responds.9000-9299 Interlisp-D microcode error detectedMost of these errors are indicative of some serious problem, probably hardware, and usuallyfatal (but try ^D if you can't TeleRaid). The main exception is 9004 see description of code9304.9001CSParErrControl store parity error9002StackErrHardware stack overflow9003IBEmptyErrInstruction fetch unit empty error9004VirtAddrErrAttempt to reference virtual address >22 bits9005EmuMemErrDouble bit memory error or non-existent memory9013NegPcErrorInconsistent PC at FnCall9014applyUfnArg to apply not integer9016notFreeTrapStack allocation error9024Page fault in the page fault handler.9048ReFOvr page fault under page fault9049Ghost context switch9051BadUfnTable 9120MiscErrOpcode no such register9121MiscErrOpcode bad 2nd byte9127PcNegErrorInconsistent PC at Punt9136CycleMaskBad caller9129M1LocMicrocode error9130M2LocMicrocode error9131M3LocMicrocode error gdpXq@p gd*?dF*j)p g]s C[dp9$ -$Y#$X)$Vo $T3$S!CP9 9N$P3$N5$MX'$K$J CG99E9DA$G ,$E  g@es. g9 "C/ 9 -C,9 .C*9 C(n9 C&:9 C$9%C!9"C9Cj9 C69 C9 C9 C9 Cf9 C29 C 9 TVk(? XEROX1108 Users Guide549300-9399 Lisp system code error (call to \MP.ERROR)These codes generally indicate an error state in Lisp system code that cannot be handled in thebreak package. Most are "should never happen" cases that indicate a serious error; but some(in particular, 9305 and 9318) may be much less serious. If possible, use TeleRaid to find outmore information (press the Undo key to enter the TeleRaid server (cursor changes into"TeleRaid"), and run the TeleRaid user from another machine). Even if you can't TeleRaid fromanother machine, several of these codes you can convert into a Lisp break if the state of thesystem is reasonably consistent and the error occurred under user code (rather than, say, thegarbage collector): type ^B to the TeleRaid server.Summary of TeleRaid server commands:^BAttempt to enter Break. If error is in a special system context, will change cursorto "CANT", indicating refusal to enter break. ^DPerform Hard Resetclear stack, flush all non-restartable processes.^NContinue from error. This is usually not possible, except for code 9318, or whenyou got a 9915 error by typing ^C while the Raid interrupt was enabled.^PDisplay Pup host number (in decimal) in maintenance panel.The 9300 Series Codes are:9302Invalid Vmem: attempt to boot an image that is not a valid Lisp sysout, or which isinconsistent from having some, but not all, of its dirty pages written. Can happen ifyou boot instead of calling LOGOUT. Usually caught sooner as code 0217.9303No place for IOCB page at startup; should never happen.9304Map out of bounds: attempt to use a pointer larger than the virtual address spaceof the machine. Usually means garbage was fetched from somewhere that shouldhave contained a pointer. This usually appears as code 9004 instead. 9305Invalid address: attempt to use a pointer that does not refer to an existing(allocated) part of virtual memory. Usually means garbage was fetched fromsomewhere that should have contained a pointer. This error can often beconverted to a break with the ^B TeleRaid command.9306Invalid virtual page. Usually caught sooner, as a 9004. 9307Unavailable page on real page chain: inconsistent state in page fault handler.9308Loop in \SELECTREALPAGE: inconsistent state in page fault handler.9309Attempt to allocate already existing page (from call to \NEWPAGE).9310\DONEWPAGE failed to allocate new map page.9311Locked page occupies a file page needed to lock another: bad state in virtualmemory system.9312Arg to CLOCK0 not an integer box. gdpXq@p gd*?dF*j)p g]s+ g[p"8 gYw4# gWC'5 gU6 gR 3 gP$2 gNs!6 gL?sp gHc$oEs9p*#9Cm,d@s9pDo>ws9pD9<Dz:Us9p: g6y3*p9;91 G9/E-ap97*p949)?09'B%p99 9#v /9!<9 ()p992p9Np9B