Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!seismo!gatech!akgua!akguc!codas!peora!jer
From: jer@peora.UUCP (J. Eric Roskos)
Newsgroups: net.arch
Subject: Re: Suspected "popf" bug in Intel 80286 (long)
Message-ID: <2128@peora.UUCP>
Date: Fri, 2-May-86 08:21:30 EDT
Article-I.D.: peora.2128
Posted: Fri May  2 08:21:30 1986
Date-Received: Thu, 8-May-86 03:25:21 EDT
References: <180@vcvax1.UUCP>
Organization: Concurrent Computer Corporation, Orlando, Fl
Lines: 16

> While experimenting with an asynchronous communication driver for VENIX
> (in protected mode) on the IBM PC/AT, I encountered some rather strange
> behavior that I now attribute to a bug in the Intel 80286 processor.

There was also an article in the latest issue of this new newspaper that
replaced _On_Communications_ (I forget the name, I think it might be
_Network_World_) that claimed that a bug existed in the 286 which was
causing network processors using that MPU to "lock up".  Unfortunately,
the article was very unclear on what was going on; and according to the
article, Intel denied any problem existed, claiming manufacturers just
hadn't followed the documentation properly, whereas the manufacturers
interviewed claimed there was a bug in the processor.  Does anybody know
what is going on with that, and if it is the same problem referenced
above?
-- 
E. Roskos