From owner-freebsd-tokenring Tue Jul 6 11:59: 7 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from ausmail1.austin.ibm.com (ausmail1.austin.ibm.com [192.35.232.12]) by hub.freebsd.org (Postfix) with ESMTP id A632515003 for ; Tue, 6 Jul 1999 11:58:59 -0700 (PDT) (envelope-from pmara@cactus.org) Received: from netmail3.austin.ibm.com (netmail3.austin.ibm.com [9.53.250.99]) by ausmail1.austin.ibm.com (8.9.1/8.8.5) with ESMTP id NAA33658 for ; Tue, 6 Jul 1999 13:55:26 -0500 Received: from popmail.austin.ibm.com (popmail.austin.ibm.com [9.53.247.178]) by netmail3.austin.ibm.com (8.8.5/8.8.5) with ESMTP id NAA17234 for ; Tue, 6 Jul 1999 13:58:58 -0500 Received: from cactus.org (pmara.austin.ibm.com [9.53.113.178]) by popmail.austin.ibm.com (AIX4.2/UCB 8.7/8.7-client1.01) with ESMTP id NAA22064 for ; Tue, 6 Jul 1999 13:58:55 -0500 (CDT) Message-ID: <37825111.5BB70A60@cactus.org> Date: Tue, 06 Jul 1999 13:55:13 -0500 From: Shashi Mara Organization: CACTUS X-Mailer: Mozilla 4.51 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-tokenring@FreeBSD.org Subject: NetBSD -- TROPIC IBM T/R Adapter Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI: Has any one looked at NetBSD 1.4 TROPIC tokenring device driver ? src/sys/dev/ic/tropic.c src/sys/dev/isapnp/if_tr_isapnp.c src/sys/dev/isa/if_tr_isa.c Separating the device driver from bus architecture make it easier to add isa / PCI/ PCMCIA support.... Shashi Mara To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Tue Jul 6 12:11:42 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id C35F414E20 for ; Tue, 6 Jul 1999 12:11:38 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id PAA07159; Tue, 6 Jul 1999 15:11:32 -0400 (EDT) Date: Tue, 6 Jul 1999 15:11:32 -0400 (EDT) From: "Matthew N. Dodd" To: Shashi Mara Cc: freebsd-tokenring@FreeBSD.ORG Subject: Re: NetBSD -- TROPIC IBM T/R Adapter In-Reply-To: <37825111.5BB70A60@cactus.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 6 Jul 1999, Shashi Mara wrote: > Has any one looked at NetBSD 1.4 TROPIC tokenring device driver ? > > src/sys/dev/ic/tropic.c > src/sys/dev/isapnp/if_tr_isapnp.c > src/sys/dev/isa/if_tr_isa.c There are actually 2 other related files in src/sys/dev/isa IIRC but my box at home is powered down so I can't go digging for the names. I've got a Tropic card in the test box I just brought up and was pondering looking at the NetBSD driver a bit more but haven't had the time. Are you offering to port the driver? > Separating the device driver from bus architecture make it easier to add > isa / PCI/ PCMCIA support.... Are there PCI based Tropic adapters? I'm aware of the LANStreamer and the Olympic PCI IBM TR cards but not of any PCI based Tropic cards. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Tue Jul 6 12:56:43 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 48DA014C13 for ; Tue, 6 Jul 1999 12:56:38 -0700 (PDT) (envelope-from lile@stdio.com) Received: from heathers.stdio.com (lile@heathers.stdio.com [199.89.192.5]) by heathers.stdio.com (8.8.8/8.8.8) with ESMTP id PAA24238; Tue, 6 Jul 1999 15:56:21 -0400 (EDT) (envelope-from lile@stdio.com) Date: Tue, 6 Jul 1999 15:56:21 -0400 (EDT) From: Larry Lile To: "Matthew N. Dodd" Cc: Shashi Mara , freebsd-tokenring@FreeBSD.ORG Subject: Re: NetBSD -- TROPIC IBM T/R Adapter In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Almost all of the TROPIC's that I know of are either glued to an ISA or PCMCIA bus. The PCMCIA variety looks exactly like the ISA's except there are a few (8 I think) extra PCMCIA specific registers. The only other TROPIC's that I know of are glued to proprietary busses and I don't think they matter to us. Larry On Tue, 6 Jul 1999, Matthew N. Dodd wrote: > On Tue, 6 Jul 1999, Shashi Mara wrote: > > Has any one looked at NetBSD 1.4 TROPIC tokenring device driver ? > > > > src/sys/dev/ic/tropic.c > > src/sys/dev/isapnp/if_tr_isapnp.c > > src/sys/dev/isa/if_tr_isa.c > > There are actually 2 other related files in src/sys/dev/isa IIRC but my > box at home is powered down so I can't go digging for the names. > > I've got a Tropic card in the test box I just brought up and was pondering > looking at the NetBSD driver a bit more but haven't had the time. > > Are you offering to port the driver? > > > Separating the device driver from bus architecture make it easier to add > > isa / PCI/ PCMCIA support.... > > Are there PCI based Tropic adapters? > > I'm aware of the LANStreamer and the Olympic PCI IBM TR cards but not of > any PCI based Tropic cards. > > -- > | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | > | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | > | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-tokenring" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Wed Jul 7 3:15:51 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 DDCF014EB3 for ; Wed, 7 Jul 1999 03:15:49 -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 MAA01765 for ; Wed, 7 Jul 1999 12:15:47 +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 MAA03029; Wed, 7 Jul 1999 12:28:49 +0200 (CEST) Message-ID: <19990707122849.28764@ns.int.ftf.net> Date: Wed, 7 Jul 1999 12:28:49 +0200 From: Phil Regnauld To: freebsd-tokenring@freebsd.org Subject: Status on Olicom driver ? 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 Hi, I've been away for a while -- what's the status on the Olicom drivers -- are ther still problems or are they working now ? (I remind my problem: 4.0-SNAP-19990421 worked, but not 4.0-SNAP-19990527 for example). Thx. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Wed Jul 7 6:21:25 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 06EC114D79 for ; Wed, 7 Jul 1999 06:21:22 -0700 (PDT) (envelope-from lile@stdio.com) Received: from heathers.stdio.com (lile@heathers.stdio.com [199.89.192.5]) by heathers.stdio.com (8.8.8/8.8.8) with ESMTP id JAA28356; Wed, 7 Jul 1999 09:21:15 -0400 (EDT) (envelope-from lile@stdio.com) Date: Wed, 7 Jul 1999 09:21:14 -0400 (EDT) From: Larry Lile To: Phil Regnauld Cc: freebsd-tokenring@FreeBSD.ORG Subject: Re: Status on Olicom driver ? In-Reply-To: <19990707122849.28764@ns.int.ftf.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Jul 1999, Phil Regnauld wrote: > Hi, > > I've been away for a while -- what's the status on the Olicom drivers -- > are ther still problems or are they working now ? > > (I remind my problem: 4.0-SNAP-19990421 worked, but not 4.0-SNAP-19990527 for example). Unfortunately it is still busted and I can't seem to figure out why. There are actually three problems that have it broken. The first is that at roughly the same time frame the driver started getting packets ( < 1500 bytes) that were spread over a huge number of mbufs ( > 16 and sometimes > 32 !) I have a fix for that in the new driver code. The second and worst is that the PMW kit ceases to call TransmitFrameCompleted. This causes the driver/card to run out of transmit buffers and there is no way to recover except reboot. The third problem (one I just ran into myself) is that since newbus the PCI bus gets probed before the ISA bus and this appears to cause the PCI probe to fail. I can't help but think that since newbus went in on 4/16 that there is some correlation with the second problem. I know the third problem is directly related to newbus, but it is a problem with the probe code in my driver. The first problem was me being naive and most likely is either some new big inefficency or some new big performance improvement, I am not sure which :) Needless to say I am very frustrated that I haven't been able to fix these problems, but I am still working on them. I still have a lot of cleaning up to do in the driver but these 3 things have me tied up. Any help would be greatly appreciated. I am getting ready to look for help on -hackers shortly. Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Thu Jul 8 6:50: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 9706B152F9 for ; Thu, 8 Jul 1999 06:50:37 -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 PAA11042; Thu, 8 Jul 1999 15:50:34 +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 QAA06250; Thu, 8 Jul 1999 16:03:47 +0200 (CEST) Message-ID: <19990708160347.13356@ns.int.ftf.net> Date: Thu, 8 Jul 1999 16:03:47 +0200 From: Phil Regnauld To: Larry Lile Cc: freebsd-tokenring@FreeBSD.ORG Subject: Re: Status on Olicom driver ? References: <19990707122849.28764@ns.int.ftf.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Larry Lile on Wed, Jul 07, 1999 at 09:21:14AM -0400 X-Operating-System: FreeBSD 3.1-RELEASE i386 Organization: FTFnet Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Larry Lile writes: > > On Wed, 7 Jul 1999, Phil Regnauld wrote: > > > Hi, > > > > I've been away for a while -- what's the status on the Olicom drivers -- > > are ther still problems or are they working now ? > > > > (I remind my problem: 4.0-SNAP-19990421 worked, but not 4.0-SNAP-19990527 for example). > [...] > The second and worst is that the PMW kit ceases to call > TransmitFrameCompleted. This causes the driver/card to run out of > transmit buffers and there is no way to recover except reboot. In my case, ifconfig down flushes the packets, and ifconfig up gets the interface up and running again (until next burst) -- mild traffic doesn't kill it... > I can't help but think that since newbus went in on 4/16 that there is > some correlation with the second problem. But 4/21 works... (except for repeated "receive error. (ReceiveStatus=3)" on the console, and it also says "adapter not ready to come up", or similar, when I ifconfig the oltr0 for the first time -- but it works anyway). > Needless to say I am very frustrated that I haven't been able to fix > these problems, but I am still working on them. I still have a lot > of cleaning up to do in the driver but these 3 things have me tied > up. Is this purely FreeBSD related -- i.e.: wouldn't the Olicom people be able to help a little ? > Any help would be greatly appreciated. I am getting ready to look > for help on -hackers shortly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Thu Jul 8 7: 5: 2 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 07169152F9 for ; Thu, 8 Jul 1999 07:04:55 -0700 (PDT) (envelope-from lile@stdio.com) Received: from heathers.stdio.com (lile@heathers.stdio.com [199.89.192.5]) by heathers.stdio.com (8.8.8/8.8.8) with ESMTP id KAA22057; Thu, 8 Jul 1999 10:04:49 -0400 (EDT) (envelope-from lile@stdio.com) Date: Thu, 8 Jul 1999 10:04:49 -0400 (EDT) From: Larry Lile To: Phil Regnauld Cc: freebsd-tokenring@FreeBSD.ORG Subject: Re: Status on Olicom driver ? In-Reply-To: <19990708160347.13356@ns.int.ftf.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Jul 1999, Phil Regnauld wrote: > Larry Lile writes: > > > > On Wed, 7 Jul 1999, Phil Regnauld wrote: > > > > > Hi, > > > > > > I've been away for a while -- what's the status on the Olicom drivers -- > > > are ther still problems or are they working now ? > > > > > > (I remind my problem: 4.0-SNAP-19990421 worked, but not 4.0-SNAP-19990527 for example). > > > [...] > > > The second and worst is that the PMW kit ceases to call > > TransmitFrameCompleted. This causes the driver/card to run out of > > transmit buffers and there is no way to recover except reboot. > > In my case, ifconfig down flushes the packets, and ifconfig up gets > the interface up and running again (until next burst) -- mild > traffic doesn't kill it... You are suffering under the too many mbufs problem. All of the available transmit fragments get used up because you are trying to transmit a packet with more mbufs than there are total (not available) adapter fragments. > > > I can't help but think that since newbus went in on 4/16 that there is > > some correlation with the second problem. > > But 4/21 works... (except for repeated "receive error. (ReceiveStatus=3)" > on the console, and it also says "adapter not ready to come up", or similar, > when I ifconfig the oltr0 for the first time -- but it works anyway). The only way I can figure out your ReceiveStatus=3 problem is with a network trace. The adapter not ready problem is a race condition that I have to fix in the probe/attach code. If you go a little further forward in time you will find that the adapter will hang on outgoing packets, because the PMW ceases to call TransmitFrameCompleted. Although without my new code to get around the mbuf fragment problem "seeing" it would be sorta pot luck. :( > > > Needless to say I am very frustrated that I haven't been able to fix > > these problems, but I am still working on them. I still have a lot > > of cleaning up to do in the driver but these 3 things have me tied > > up. > > Is this purely FreeBSD related -- i.e.: wouldn't the Olicom people > be able to help a little ? The author of PMW is looking at some dumps for me already. It is likely an interrupted DMA transfer, caused by me failing to protect a PMW call properly. Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Thu Jul 8 14:36: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 D3D27150E6 for ; Thu, 8 Jul 1999 14:36:12 -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 XAA19872; Thu, 8 Jul 1999 23:36:04 +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 XAA07010; Thu, 8 Jul 1999 23:49:20 +0200 (CEST) Message-ID: <19990708234920.32311@ns.int.ftf.net> Date: Thu, 8 Jul 1999 23:49:20 +0200 From: Phil Regnauld To: Larry Lile Cc: freebsd-tokenring@FreeBSD.ORG Subject: Re: Status on Olicom driver ? References: <19990708160347.13356@ns.int.ftf.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Larry Lile on Thu, Jul 08, 1999 at 10:04:49AM -0400 X-Operating-System: FreeBSD 3.1-RELEASE i386 Organization: FTFnet Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Larry Lile writes: > > > > But 4/21 works... (except for repeated "receive error. (ReceiveStatus=3)" > > on the console, and it also says "adapter not ready to come up", or similar, > > when I ifconfig the oltr0 for the first time -- but it works anyway). > > The only way I can figure out your ReceiveStatus=3 problem is with a > network trace. I can supply you with the output of tcpdump : the machine is _idle_ and this happens with clockwork precision (will measure the interval tommorrow), when the machine is xmitting/receiving nothing. Any other info ? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Fri Jul 9 1:12:46 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 5F1E71552D for ; Fri, 9 Jul 1999 01:12:34 -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 KAA00729; Fri, 9 Jul 1999 10:12:31 +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 KAA07902; Fri, 9 Jul 1999 10:25:52 +0200 (CEST) Message-ID: <19990709102551.19936@ns.int.ftf.net> Date: Fri, 9 Jul 1999 10:25:51 +0200 From: Phil Regnauld To: Larry Lile Cc: freebsd-tokenring@FreeBSD.ORG Subject: Re: Status on Olicom driver ? References: <19990708160347.13356@ns.int.ftf.net> <19990708234920.32311@ns.int.ftf.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <19990708234920.32311@ns.int.ftf.net>; from Phil Regnauld on Thu, Jul 08, 1999 at 11:49:20PM +0200 X-Operating-System: FreeBSD 3.1-RELEASE i386 Organization: FTFnet Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Phil Regnauld writes: > > > > The only way I can figure out your ReceiveStatus=3 problem is with a > > network trace. > > I can supply you with the output of tcpdump : the machine > is _idle_ and this happens with clockwork precision (will measure > the interval tommorrow), when the machine is xmitting/receiving nothing. The receive error happens every 26~27 seconds, systematically. Will try to correlate it with the activity on the net. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message