From owner-freebsd-tokenring Fri May 28 1:18:31 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 8DDCC14F3E for ; Fri, 28 May 1999 01:18:27 -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 KAA27871 for ; Fri, 28 May 1999 10:20:07 +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 KAA01525 for freebsd-tokenring@freebsd.org; Fri, 28 May 1999 10:25:32 +0200 (CEST) Message-ID: <19990528095720.38159@ns.int.ftf.net> Date: Fri, 28 May 1999 09:57:20 +0200 From: Phil Regnauld To: freebsd-tokering@freebsd.org Subject: 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 Here's the context: uname: FreeBSD aylee 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Wed May 19 14:31:48 CEST 1999 root@:/usr/src/sys/compile/AYLEE i386 dmesg: oltr0: oltr_probe oltr0: auto assigning card. oltr0: [00:00:83:79:d5:c4] oltr0 at port 0xa20 irq 10 drq 7 on isa0 oltr0: Adapter modes - TRLLD_MODE_16M TRLLD_MODE_PHYSICAL oltr0 XXX: driver didn't set ifq_maxlen oltr0: adapter status good. (close completed/self-test) oltr0: Ring status change: [Soft error] oltr0: receive error. (ReceiveStatus=3) oltr0: receive error. (ReceiveStatus=3) oltr0: receive error. (ReceiveStatus=3) ^--- repeat every ~10 seconds ---^ ifconfig: oltr0: flags=8843 mtu 1500 inet 1.2.3.4 netmask 0xff000000 broadcast 1.255.255.255 lladdr 00:00:83:79:d5:c4 media: autoselect () supported media: UTP/16Mbit UTP/4Mbit autoselect - the card seems to work fine, but when I do some heavy traffic (i.e.: ftp from machine to machine), the connection hangs, between 100 and 200 KB into the transfer. When I do ifconfig down, I see: oltr0: Promiscuous mode stopped: Poll failure May 28 09:39:49 aylee /kernel: oltr0: promiscuous mode enabled May 28 09:40:36 aylee calife+[523]: pr to root on ttyp6 - BEGIN oltr0: otlr_stop oltr0: DriverTransmitFrameCompleted (frame 2 status 1) oltr0: DriverTransmitFrameCompleted (frame 3 status 1) oltr0: DriverTransmitFrameCompleted (frame 4 status 1) oltr0: DriverTransmitFrameCompleted (frame 5 status 1) oltr0: DriverTransmitFrameCompleted (frame 0 status 1) oltr0: DriverTransmitFrameCompleted (frame 6 status 1) oltr0: DriverTransmitFrameCompleted (frame 7 status 1) oltr0: DriverTransmitFrameCompleted (frame 8 status 1) oltr0: DriverTransmitFrameCompleted (frame 9 status 1) oltr0: DriverTransmitFrameCompleted (frame 10 status 1) oltr0: DriverTransmitFrameCompleted (frame 11 status 1) oltr0: DriverTransmitFrameCompleted (frame 12 status 1) oltr0: DriverTransmitFrameCompleted (frame 13 status 1) oltr0: DriverCloseCompleted ... and then if I ifconfig the oltr0 back up within a short delay, the connection is "restored" (until the next heavy trnsfer). note: on an earlier test, I suddenly saw a large frame burst with tcpdump that looked like: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 ... over a few hundred lines I couldn't see the offending packet header, as the scrollback buffer wasn't long enough, and then my machine suddenly rebooted :-| The hardware is an IBM 300PL with on board fxp0, Pii-350 and 128-MB of RAM -- the bios settings for DMA and such look ok, but I will need to check. Anybody seen this kind of problem ? I'v heard the Olicom drivers were supposed to be stable, and we already use them here in Linux, but I'm dying to get our internal DNS+DHCP boxes up and running on FreeBSD... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message