From owner-freebsd-current  Fri Jan 19 14:28:16 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA19314
          for current-outgoing; Fri, 19 Jan 1996 14:28:16 -0800 (PST)
Received: from uni-sb.de (uni-sb.de [134.96.7.230])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA19308
          for <current@freebsd.org>; Fri, 19 Jan 1996 14:28:07 -0800 (PST)
Received: by uni-sb.de with ESMTP; Fri, 19 Jan 1996 23:27:52 +0100 (MET)
Received: by cs.uni-sb.de with ESMTP; Fri, 19 Jan 1996 23:27:49 +0100 (MET)
Received: (from rock@localhost)
          by wurzelausix.CS.Uni-SB.DE (8.7.3/wjp-SVR4/951126s)
          id XAA01553; Fri, 19 Jan 1996 23:27:52 +0100 (MET)
Date: Fri, 19 Jan 1996 23:27:52 +0100 (MET)
From: "D. Rock" <rock@wurzelausix.CS.Uni-SB.DE>
Message-Id: <199601192227.XAA01553@wurzelausix.CS.Uni-SB.DE>
To: current@freebsd.org
Subject: machdep.c, pmap.c and i386 CPUs
Sender: owner-current@freebsd.org
Precedence: bulk

Noone else running FreeBSD-current on a 386 processor.

The machine panics immediately. The problem is the in this stage
uninitialized variable cpu_class in /sys/i386/i386/machdep.c
In pmap.c the code jumps to the wrong place and the machine hangs with
an illegal instruction. After initializing the variable with a default
value of CPUCLASS_386 the machine just works fine now.

Daniel