From owner-freebsd-current  Sat Apr 19 23:53:08 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA08408
          for current-outgoing; Sat, 19 Apr 1997 23:53:08 -0700 (PDT)
Received: from mercury.uniserve.com (mercury.uniserve.com [204.191.197.248])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA08401
          for <freebsd-current@freebsd.org>; Sat, 19 Apr 1997 23:53:04 -0700 (PDT)
Received: from haven.uniserve.com (shell.uniserve.com [198.53.215.121]) by mercury.uniserve.com (8.8.2/8.8.2) with SMTP id XAA04673; Sat, 19 Apr 1997 23:46:49 -0700 (PDT)
Date: Sat, 19 Apr 1997 23:58:33 -0700 (PDT)
From: Tom Samplonius <tom@uniserve.com>
To: Brian Tao <taob@nbc.netcom.ca>
cc: freebsd-current@freebsd.org
Subject: Re: "Data overrun" with 3.0-SNAP, 2940UW controllers
In-Reply-To: <Pine.GSO.3.95.970419233210.11036M-100000@tor-adm1.nbc.netcom.ca>
Message-ID: <Pine.NEB.3.95.970419235345.9508A-100000@haven.uniserve.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Sun, 20 Apr 1997, Brian Tao wrote:

>     I'm stress testing a new NFS server with 2.0-970209-SNAP to see
> how it deals with having a couple of Adaptec 2940UW controllers.
> About half an hour into the tests, the machine appears to have crashed
> (no response to pings), and I don't have physical access to the
> machine right now.  :(

  3.0-970209?  The ahc driver has had major bugs fixed since then.  This
has been reported on this list many times.  In fact, see the archives in
regards to the similar problems that I had with the dual-channal 3940UW
controllor.

Tom