From owner-freebsd-smp  Tue Sep  2 17:31:22 1997
Return-Path: <owner-freebsd-smp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id RAA06420
          for smp-outgoing; Tue, 2 Sep 1997 17:31:22 -0700 (PDT)
Received: from ic.net (qmailr@srv1b.ic.net [152.160.72.20])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA06415
          for <smp@freebsd.org>; Tue, 2 Sep 1997 17:31:19 -0700 (PDT)
Received: (qmail 8743 invoked from network); 3 Sep 1997 00:30:59 -0000
Received: from unknown (HELO lurch.rickl.org) (152.160.108.5)
  by unknown with SMTP; 3 Sep 1997 00:30:59 -0000
Received: from lurch.rickl.org (rickl@lurch.rickl.org [192.168.255.1]) by lurch.rickl.org (8.8.7/8.7.3) with ESMTP id SAA11789 for <smp@freebsd.org>; Tue, 2 Sep 1997 18:36:37 -0400 (EDT)
Date: Tue, 2 Sep 1997 18:36:37 -0400 (EDT)
From: Rick Lotoczky <rickl@ic.net>
Reply-To: Rick Lotoczky <rickl@ic.net>
Subject: Re: serious instability with -current kernel
To: smp@freebsd.org
Message-ID: <ML-3.0.873239797.7590.rickl@lurch.rickl.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-freebsd-smp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I've been using the -current kernel with updates thru today (9/2) without a
problem.  I'm using X, and the ep network driver. The only issue I've seen
is a large amount of interrupt-level overflows on the serial driver.  The
MB is a SuperMicro P6DOF, 64MB RAM, 2940UW scsi, and NCR '815 scsi.

Rick