🚀 go-pugleaf

In article <1992Nov12.151415.21751@thijssen.nl>, geveld@thijssen.nl (Ge v.d. Veldt) writes:
> Problem 1:
> The RSX11M-plus operating system crashes at random time intervals with the 
> following console message:
> 
> 		XXXXXXXXX Exec. parity error stop XXXXXXXXX
> 
> After that the CPU halts, no time to generate an errorlog entrie. The same
> system has no problems when the CPU is a PDP11/84.

  You should make sure all of your Unibus boards are up to current revision
levels, as well as the bus converter (KT84, I think) that converts the Q-
bus to Unibus.

  Was your system upgraded by DEC (they are supposed to check all of this)
or did you just acquire and install the 11/93 CPU board? Also, make sure
that you have no Unibus or PMI memory installed.

  You could compare the displayed address against the map you got when you
built your executive. It's either in executive code or data. Finding out
_what_ code or data might help pin down what device is corrupting memory.

  Have you tried another '93 CPU to make sure that you don't have a real
memory problem? Also, I assume that you have a production-level '93 - the
prototypes had some rather odd memory timing quirks.

> Problem 2
> The PDP11/94 processor seem to have another power-up sequence compared with 
> the PDP11/84. When the DT07 has selected  the PDP11/94 CPU for unibus exten-
> sion the frontpanel halt/reset tockle switch will bring the CPU in a not 
> accessable  state when manipulated. The only way to get out of that state 
> (without powering down the system) is to deselect the unibusextension via the
> DT07 frontpanel switches and restart the 11/94 again. This time the normal
> powerup sequence will take place.

  I didn't think the DT07 was supported? I think what you're saying is that
you have to reset the '93 in order for it to come up after the Unibus has
been switched? This one you'll probably have to talk to the DEC folks about,
and maybe ROI as well.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381

In article <1992Nov12.151415.21751@thijssen.nl>, geveld@thijssen.nl (Ge v.d. Veldt) writes:
> 
> Hello,
> 
> We experienced 2 problems while upgrading a PDP11/84 to a PDP11/94.
> The PDP 11/84 contains very old hardware such as:
> 
> 		Emulex SC21 diskcontroller with M2322 Fujitsu disk
> 		RL11 diskcontroller
> 		Delua ethernet controller
> 		Emulex TC12 tapecontroller with M890 Cipher drive
> 		DL11-W asynchronous controller
> 		DZ11 asynchronous Multiplexer
> 		DT07 unibusswitch
> 		ICR11 I/O subsystem
                ^^^^^^^^^^^^^^^^^^^ or is it a ICS?
> 		Fisher and Porter CCM communication controller
> 
> Problem 1:
> The RSX11M-plus operating system crashes at random time intervals with the 
> following console message:
> 
> 		XXXXXXXXX Exec. parity error stop XXXXXXXXX
> 

This isn't the North sea gas terminal control system by any chance?? I'll put
money on it being the ICS/ICR as the problem. Are you running M or M-PLUS BTW?
Have all ICS/ICR and DT07 backplanes had the DD-11 ECO for the UDA-50 done?
This killed the Gronigen system when it went in. Bet the deuna/cpu cause signal
corruption and cross talk in the unibuss. If it IS an ICR, not an ICS, how long
is the link cable between the unibus and the ICS unit?

~Paul

In article <1992Nov12.151415.21751@thijssen.nl>, geveld@thijssen.nl (Ge v.d. Veldt) writes:
> 
> Hello,
> 
> We experienced 2 problems while upgrading a PDP11/84 to a PDP11/94.
> The PDP 11/84 contains very old hardware such as:
> 
> 		Emulex SC21 diskcontroller with M2322 Fujitsu disk
> 		RL11 diskcontroller
> 		Delua ethernet controller
> 		Emulex TC12 tapecontroller with M890 Cipher drive
> 		DL11-W asynchronous controller
> 		DZ11 asynchronous Multiplexer
> 		DT07 unibusswitch
> 		ICR11 I/O subsystem
> 		Fisher and Porter CCM communication controller
> 
> Problem 1:
> The RSX11M-plus operating system crashes at random time intervals with the 
> following console message:
> 
> 		XXXXXXXXX Exec. parity error stop XXXXXXXXX
> 
> After that the CPU halts, no time to generate an errorlog entrie. The same
> system has no problems when the CPU is a PDP11/84.
> 

Have read the mail you sent, 4 ICRs!! The question that occurs first is Where
did you get the M-Plus ICS/ICR driver? I assume you are using the DT07 as a
manual switch between 2 CPUs.

> Problem 2
> The PDP11/94 processor seem to have another power-up sequence compared with 
> the PDP11/84. When the DT07 has selected  the PDP11/94 CPU for unibus exten-
> sion the frontpanel halt/reset tockle switch will bring the CPU in a not 
> accessable  state when manipulated. The only way to get out of that state 
> (without powering down the system) is to deselect the unibusextension via the
> DT07 frontpanel switches and restart the 11/94 again. This time the normal
> powerup sequence will take place.
> 
> 		WHO HAS  ANY  SUGGESTIONS FOR THESE PROBLEMS????
> 

There was a simular problem with the 84 as I remember. This was fixed by an ECO
to the CPU to increase the reset time or some such. Best refer this one to some-
one in Utrecht I think. Good luck finding a Digit who knows what an 11 is!!

As to the UDA related problem I mentioned before, I think the NPG line was the
main culprit. The fix was to replace a couple of the wire runs in the DKs with
twisted pair. If you have access to the 11 fische library, its in there in the
ECO listings. You will need to do the same fix to the DT07, ICS/ICR bachplanes
and all the DD-11s if its not been done. Can you run the system without the
ICS/ICR? The other errors hint that exec I-space is being corrupted, poss by
erratic DMA.

~Paul