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