From owner-freebsd-hackers Thu Jul 9 07:57:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24420 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 07:57:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24415 for ; Thu, 9 Jul 1998 07:57:34 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id QAA26281 ; Thu, 9 Jul 1998 16:56:09 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id QAA13910; Thu, 9 Jul 1998 16:56:08 +0200 To: sbabkin@dcn.att.com Cc: mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: NIC drivers References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 09 Jul 1998 16:56:07 +0200 In-Reply-To: sbabkin@dcn.att.com's message of Thu, 9 Jul 1998 10:47:40 -0400 Message-ID: Lines: 37 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sbabkin@dcn.att.com writes: > > sbabkin@dcn.att.com writes: > > > Although I don't know about the current state of the driver. There > > > was a period (early '95) when packet loss led to the hang of the > > > card and that's the reason why it was marked as "buggy" in LINT at > > > that time. This was fixed but this comment just was not cleaned up. > > Believe me, it still sucks. Search the archives (both the mailing list > > archives and the PR database) for "no buffer space", and/or "ep0". > > Basically, the driver is fine for telnet and mail, but wedges under > > sustained load. I can get it to hang without ever going above 20 kBps > Do you have heavy disk load ? This card has small buffer size No. I experience these problems mostly while playing MP3 audio files which reside on an NFS file system. It is invariably the server that gets wedged. The disk load is practically identical to the network load in that case (~130 kbps) > so it's sensitive to interrupt delays. Another problem is that in > case of buffer overflow it has to be reset. But when the watchdog > routine discovers this, it restores just fine and the problem > generally occurs not that often. Of course, if it was Nope. Once it's wedged it stays wedged until I do ifconfig ep0 up. > not broken again (I've fixed it twice but I don't have these cards > any more so I have no interest in doing that once more :-). > > (160 kbps). Gimme an Intel EtherExpress. > Sure, _now_, when you can get 100Mbps EtherExpress for > the same money, nobody would buy 3c509. But a few years ago -------------- Half the money, if the reports I've heard of EtherExpress cards retailing at $50 are reliable. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message