From owner-freebsd-tokenring Thu Jun 3 4:37:41 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (Postfix) with ESMTP id D921614C20 for ; Thu, 3 Jun 1999 04:37:36 -0700 (PDT) (envelope-from regnauld@ftf.net) Received: from ns.int.ftf.net (fw2.ftf.dk [192.168.1.2] (may be forged)) by mail.ftf.dk (8.9.3/8.9.3/gw-ftf-1.2) with ESMTP id NAA23482 for ; Thu, 3 Jun 1999 13:39:11 +0200 (CEST) X-Authentication-Warning: mail.ftf.dk: Host fw2.ftf.dk [192.168.1.2] (may be forged) claimed to be ns.int.ftf.net Received: (from regnauld@localhost) by ns.int.ftf.net (8.9.2/8.9.3) id NAA18565; Thu, 3 Jun 1999 13:45:35 +0200 (CEST) Message-ID: <19990603134535.55646@ns.int.ftf.net> Date: Thu, 3 Jun 1999 13:45:35 +0200 From: Phil Regnauld To: freebsd-tokenring@freebsd.org Subject: Re: Strange behavior with OC-3117, 4.0-C Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e X-Operating-System: FreeBSD 3.1-RELEASE i386 Organization: FTFnet Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wood, Richard writes: > > -----Original Message----- > > From: Phil Regnauld [mailto:regnauld@ftf.net] > > Sent: Friday, May 28, 1999 8:57 AM > > To: freebsd-tokering@freebsd.org > > Subject: Strange behavior with OC-3117, 4.0-C > > > > > Anybody seen this kind of problem ? > > I've had similar problems with a OC-3137 (PCI/II 16/4) card in a Digital > Venturis P75 machine, but I managed to break the machine completely before > looking into it any further. > > The symptoms were very similar to yours. The machine would be fine as long > as I didn't use it much, but doing anything which transferred data at a high > rate would cause the card to fall over. Even doing an `ls -al` on a large > directory would cause the link to fail, however downloading a 100MB file > over our 512K WAN link was fine, therefore it's almost definately speed of > delivery and not quantity of data which is the problem. > > IIRC though, I couldn't `ifconfig down` and then `ifconfig up` the interface > to restart it, a powerdown was the only option. I solved this problem by reinstalling 19990421-CURRENT -- something between 19990421 and 19990530 had broken the DMA or something else. Larry Lile said it might be the new bus code. My adapter works fine now, except for regular receive error(3) messages on the console (and corresponding errors in netstat -i) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message