xy: cannot exec first read

[Mike Persichetty]

The problem described was caused by a timing condition in the CPU
firmware. This problem was corrected by Sun in mid March 1989 with the
release of the 2.8.4 Boot PROM.

 CPU boards with the following part numbers incorporate this change:

        501-1206-16 or greater   Sun-3/260/280
        501-1100-15 or greater   Sun-3/260/280
        501-1274-20 or greater   Sun-4/260/280
        501-1491-04 or greater   Sun-4/260/280
        501-1522-04 or greater   Sun-4/260/280
        501-1164-14 or greater   Sun-3/160/180
        501-1208-10 or greater   Sun-3/160/180


>Date:    Fri, 11 Aug 89 10:34:08 PDT
>From:    Brent Chapman <capmkt!brent at uunet.uu.net>
>Subject: Re: xy: cannot exec first read

>We ran into this in late December and early January.  This is indeed a bug
>in the 2.7 (and 2.8, from what I'm told by Sun) PROMs.  We had a 3/280
>that started exhibiting the same problems after a motherboard swap during
>maintenance, and we finally narrowed it down to the new PROMs.  Going back
>to an older boot PROM (2.6 or earlier) fixed the problem.  I don't know if
>it's been fixed in subsequent versions of the PROM (I've seen at least one
>machine with PROM rev 2.8.3, though).

>While we were tracking this down, we heard from several other people at
>other sites with the same problem, and folks from Sun were working on it.
>The person at Sun who we working with and who seemed to be the one
>tracking the problem was Mike Persichetty <mike at sun.com>.  Sorry, I don't
>have a bug number (do such things exist for hardware problems?) or service
>order number handy, but hopefully he'll remember it. 

>-Brent
>--
>Brent Chapman					Capital Market Technology, Inc.
>Computer Operations Manager			1995 University Ave., Suite 390
>brent at capmkt.com				Berkeley, CA  94704
>{apple,lll-tis,uunet}!capmkt!brent		Phone:  415/540-6400


 Mike Persichetty
 Sun Microsystems, Inc.
 CSD Product Support Engineering