From owner-freebsd-current  Tue Jan 28 02:53:14 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA05557
          for current-outgoing; Tue, 28 Jan 1997 02:53:14 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA05552
          for <freebsd-current@freebsd.org>; Tue, 28 Jan 1997 02:53:11 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id VAA21068; Tue, 28 Jan 1997 21:40:49 +1100
Date: Tue, 28 Jan 1997 21:40:49 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199701281040.VAA21068@godzilla.zeta.org.au>
To: freebsd-current@freebsd.org, regnauld@deepo.prosa.dk
Subject: Re: DX 2/50 as i286...
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>More on this -- defining I386_CPU as well as I486_CPU doesn't help.
>The kernel still panics on boot with a i286 probe !
>
>Strangely, the I486_CPU only kernel of the machine I'm using now
>works fine on the 2/50 (??).  The only differences I see in the kernels are:

The i286 message means that `cpu_class' is 0.  This can't happen :-).
cpu_class is always set to != 0 if `cpu_id' is 0x435.  The other
messages are consistent with a cpu_id of 0x435.  Perhaps something
is overwriting cpu_class.

Bruce