To: BUG-LISPM@lurch
--Text Follows This Line--
In LMI Experimental System 123.235, Experimental Local-File 73.4,
Experimental FILE-Server 22.2, Experimental Unix-Interface 11.0,
Experimental KERMIT 34.3, Experimental ZMail 71.0,
Experimental Lambda-Diag 15.0, Experimental Tiger 27.0,
Experimental Site Data Editor 9.0, Experimental Tape 22.1,
microcode 1755, SDU Boot Tape 3.14, SDU ROM 8, Beta II/site/patch,
on Opus (LAMBDA):


Insert your description of the circumstances here:

I got this again, accessing a remote Lambda-Plus (System 5).  The login
sequence worked, but this happened in the background...?

>>ERROR: QFILE protocol violated, unknown transaction id in "T1269  ERROR UNK C Login incorrect."
Backtrace from the debugger:

(:INTERNAL FS::HOST-CHAOS-INTERRUPT-FUNCTION 0) (P.C. = 31)

 Arg 0 (PKT): #<CHAOS packet :STRING "T1269  ERROR UNK C Login incorrect." :STATUS CHAOS::RELEASED 33266775>


SI::PROCESS-RUN-FUNCTION-INTERNAL (P.C. = 64)

 Arg 0 (RESTART-ON-RESET): NIL
 Arg 1 (FUNCTION): #<DTP-FEF-POINTER (:INTERNAL FS::HOST-CHAOS-INTERRUPT-FUNCTION 0) 50432021>
 Rest arg (ARGS): (#<CHAOS packet :STRING "T1269  ERROR UNK C Login incorrect." :STATUS CHAOS::RELEASED 33266775>)
 Local 1: ("Terminate and free process ~A." "QFILE Protocol Error")
 Local 2: ((SYSTEM:ABORT ERROR) ("Terminate and free process ~A." "QFILE Protocol Error") T ("Terminate and free process ~A." "QFILE Protocol Error") ...)


SI::PROCESS-TOP-LEVEL (P.C. = 113)

 Arg 0 (IGNORE): NIL
 Local 0: ("Reset and arrest process ~A." "QFILE Protocol Error")
 Local 1: (CONDITION ("Reset and arrest process ~A." "QFILE Protocol Error") T ("Reset and arrest process ~A." "QFILE Protocol Error") ...)
 Local 2: ("Restart process ~A." "QFILE Protocol Error")
 Local 3: ((SYSTEM:ABORT CONDITION) ("Restart process ~A." "QFILE Protocol Error") T ("Restart process ~A." "QFILE Protocol Error") ...)