From owner-freebsd-stable  Sat Aug  3 14:38:41 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA16679
          for stable-outgoing; Sat, 3 Aug 1996 14:38:41 -0700 (PDT)
Received: from sierra.zyzzyva.com (ppp0.zyzzyva.com [198.183.2.50])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA16674
          for <freebsd-stable@freebsd.org>; Sat, 3 Aug 1996 14:38:35 -0700 (PDT)
Received: from sierra.zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.7.3) with ESMTP id QAA11489 for <freebsd-stable@freebsd.org>; Sat, 3 Aug 1996 16:38:33 -0500 (CDT)
Message-Id: <199608032138.QAA11489@sierra.zyzzyva.com>
To: freebsd-stable@freebsd.org
Subject: ep0 problems and the stable tree
X-uri: http://www.zyzzyva.com/
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 03 Aug 1996 16:38:33 -0500
From: Randy Terbush <randy@zyzzyva.com>
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I've seen a lot of discussion about the ep driver getting broken late
in the 2.1.5 release. Should I still be seeing this from sources dated

sierra:/sys/i386/isa
#> ll if_ep*
-rw-r--r--  1 root  wheel  36464 Jul 15 23:10 if_ep.c
-rw-r--r--  1 root  wheel  36457 May 26 14:54 if_ep.c.orig
-rw-r--r--  1 root  wheel  13946 Mar 31 23:08 if_epreg.h

Aug  3 16:11:25 sierra /kernel: ep0: Status: 2002 (input buffer overflow)
Aug  3 16:13:49 sierra /kernel: ep0: Status: 2002 (input buffer overflow)
Aug  3 16:13:52 sierra /kernel: ep0: Status: 2002 (input buffer overflow)


The net result is that a new NFS client on the net is suddenly freezing
quite frequently. Killing and restarting the 'nfsd' processes on the
server fix the problem.

Secondly, do I dare sup the -stable tree at this point? What was decided?