From owner-cvs-src@FreeBSD.ORG Tue Oct 21 10:08:28 2003 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67D2716A4B3; Tue, 21 Oct 2003 10:08:28 -0700 (PDT) Received: from postal2.es.net (proxy.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6ADD43FB1; Tue, 21 Oct 2003 10:08:26 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id MUA74016; Tue, 21 Oct 2003 10:08:25 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id A69F25D07; Tue, 21 Oct 2003 10:08:23 -0700 (PDT) To: Sam Leffler In-Reply-To: Message from Sam Leffler of "Tue, 21 Oct 2003 08:50:03 PDT." <200310210850.03204.sam@errno.com> Date: Tue, 21 Oct 2003 10:08:23 -0700 From: "Kevin Oberman" Message-Id: <20031021170823.A69F25D07@ptavv.es.net> cc: cvs-src@FreeBSD.org cc: Andrea Campi cc: Warner Losh cc: cvs-all@FreeBSD.org cc: src-committers@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/ep if_ep.c if_ep_isa.c if_ep_pccard.c if_epreg.h if_epvar.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 17:08:28 -0000 > From: Sam Leffler > Date: Tue, 21 Oct 2003 08:50:03 -0700 > Sender: owner-cvs-all@freebsd.org > > On Tuesday 21 October 2003 12:42 am, Andrea Campi wrote: > > Incidentally, even when ep is sane, I still need to remove MPSAFE from > > pccbb.c, or it stops after a few dozens of packets are sent/received. > > Rerunning ifconfig on the interface brings it back for a few more packets. > > Could this be the same problem that people are reporting on current@ as "IP > stack is busted"? Some of those folks were, however, using USB Ethernet > devices... I doubt it. FWIW, the problem has disappeared from my system since I updated my CURRENT about a week ago. I ran over the weekend with absolutely no sign of the problems I had been seeing for the prior two weeks. I suspect that whatever was causing this problem (Prism 2.5 mini-PCI card) has been fixed, probably as a fix for a different problem. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634