The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] pdp11 UNIX memory allocation.
Date: Wed, 7 Jan 2015 11:14:48 -0500	[thread overview]
Message-ID: <CAC20D2PRdyZCb6edmHbX1cTeuEcGZdjTo_TMzFzYVAv9UMegXQ@mail.gmail.com> (raw)
In-Reply-To: <54AC70EE.4060301@update.uu.se>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2190 bytes --]

On Tue, Jan 6, 2015 at 6:34 PM, Johnny Billquist <bqt at update.uu.se> wrote:

> The basic microcode for the machine was in ROM, just like on all the other
> PDP-11s. And DEC sold a compiler and other programs required to develop
> microcode for the 11/60. Not that I know of anyone who had them. I've
> "owned" four PDP-11/60 systems in my life. I still have a set of boards for
> the 11/60 CPU, but nothing else left around.


I did not realized it was an option.  ​IIRC we had it on the Teklabs 11/60,
but we could not run the tools easily so we ended up never messing with it.
  We had talked about adding the CMU csav/cret instructs from the 11/40e
but we got the 11/70 and that sucked up my time and I never got back to try
it.

It was not a redux of the 11/34 BTW.  Jeff Mitchell did the 11/34 and was
off working on the 750 when the 60 was done.  I believe Al Pat was somehow
involved with 60, but I've forgotten.

As for the "halt and confuse uCode" stuff.  The 60 was notorious for
getting "stuck" when running UNIX.    I've now forgotten many of the
details, IIRC it had to with context switch, register save and I think I
remember it was something to do with multiple interrupts.   Since Glaser
and I did the original 11/60 port, I think we knew most of the USENIX UNIX
sites that run it on them since we swapped notes if not code.  All of us
used to complain about random hangs where the uCode take a jump and the
system would halt.    The only solution when that happened was the pull the
circuit breaker power on the back of the machine because the front panel
switched were lost.   I personally spend many hours with the DEC guys
trying to figure what is was, we could never repeat it.   Years later, when
I got to know some of the uCode engineers that had worked on the 11s and
the Vaxen, I found out it was agreed at DEC engineer there was a uCode bug,
but so few UNIX customer were out there (and the system had gone to
"traditional products") management dropped as not being worth finding and
fixing.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150107/eb826931/attachment.html>


  parent reply	other threads:[~2015-01-07 16:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.151.1420584979.3354.tuhs@minnie.tuhs.org>
2015-01-06 23:34 ` Johnny Billquist
2015-01-06 23:52   ` scj
2015-01-07 16:14   ` Clem Cole [this message]
2015-01-07 17:27     ` Dave Horsfall
2015-01-07  2:18 Noel Chiappa
2015-01-07 16:17 ` Clem Cole
  -- strict thread matches above, loose matches on Subject: below --
2015-01-06 22:45 Noel Chiappa
2015-01-06 22:55 ` Clem Cole
     [not found] <mailman.149.1420581544.3354.tuhs@minnie.tuhs.org>
2015-01-06 22:20 ` Johnny Billquist
2015-01-06 22:36   ` Ronald Natalie
2015-01-06 23:14     ` Johnny Billquist
2015-01-07  2:39   ` John Cowan
2015-01-07  2:59     ` Johnny Billquist
     [not found] <mailman.147.1420574271.3354.tuhs@minnie.tuhs.org>
2015-01-06 20:20 ` Johnny Billquist
2015-01-06 20:33   ` random832
2015-01-06 21:57     ` Ronald Natalie
2015-01-06 22:00       ` Clem Cole
2015-01-06 22:04         ` Ronald Natalie
2015-01-07  1:46       ` Dave Horsfall
2015-01-07  2:00         ` Ronald Natalie
2015-01-07  6:29           ` Dave Horsfall
2015-01-07  6:39             ` Warren Toomey
2015-01-07 10:06               ` Brantley Coile
2015-01-07 13:29             ` Jacob Ritorto
     [not found]     ` <CAC20D2PP1hGyYsep1yNtj9KO55a-V02+QHS+S7bX-4joJy222g@mail.gmail.com>
     [not found]       ` <1420583703.863814.210431037.61D6C6EC@webmail.messagingengine.com>
2015-01-06 22:36         ` random832

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAC20D2PRdyZCb6edmHbX1cTeuEcGZdjTo_TMzFzYVAv9UMegXQ@mail.gmail.com \
    --to=clemc@ccc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).