Date: Fri, 28 May 1999 09:57:20 +0200 From: Phil Regnauld <regnauld@ftf.net> To: freebsd-tokering@freebsd.org Subject: Strange behavior with OC-3117, 4.0-C Message-ID: <19990528095720.38159@ns.int.ftf.net>
next in thread | raw e-mail | index | archive | help
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: <Olicom ISA 16/4 Adapter (OC-3117)> [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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 1.2.3.4 netmask 0xff000000 broadcast 1.255.255.255
lladdr 00:00:83:79:d5:c4
media: autoselect (<unknown type>)
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990528095720.38159>