From owner-freebsd-current Tue Apr 6 8: 9:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from sirius.ctr.columbia.edu (sirius.ctr.columbia.edu [128.59.64.60]) by hub.freebsd.org (Postfix) with ESMTP id D598014C28 for ; Tue, 6 Apr 1999 08:09:47 -0700 (PDT) (envelope-from wpaul@ctr.columbia.edu) Received: from startide.ctr.columbia.edu (wpaul@startide.ctr.columbia.edu [128.59.64.52]) by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) with ESMTP id LAA16000; Tue, 6 Apr 1999 11:07:48 -0400 (EDT) From: wpaul@ctr.columbia.edu (Bill Paul) Received: (wpaul@localhost) by startide.ctr.columbia.edu (8.9.1/8.6.4.788743) id LAA23216; Tue, 6 Apr 1999 11:07:46 -0400 (EDT) Message-Id: <199904061507.LAA23216@startide.ctr.columbia.edu> Subject: Re: Patched RealTek driver -- please test To: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) Date: Tue, 6 Apr 1999 11:07:46 -0400 (EDT) Cc: shocking@bandicoot.prth.tensor.pgs.com, current@freebsd.org In-Reply-To: <199904061135.TAA29847@ariadne.tensor.pgs.com> from "Stephen Hocking-Senior Programmer PGS Tensor Perth" at Apr 6, 99 07:35:58 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Stephen Hocking-Senior Programmer PGS Tensor Perth had to walk into mine and say: > OK - I've banged on the new version with extra debug messages and it still > locks up, but without any messages! Grr. > I can only conclude that the 486MB BIOS is > iffy. I haven't tried any other slots in the MB, but have tried various PCI > settings, all to no avail. I have swapped the de0 and the rl0 between > machines, and the rl0 is happy in it's new home - hasn't fallen over, although > it's netpipe performance sucks with very small packets. I think we can write > this one off as a faulty PCI implementation on the 486 motherboard. Thanks for > your patience & time. I have one more thing you can try for me (I hope it's not too much trouble to put the NIC back where it was). This latest test version has a small change to rl_start() which modifies the transmit behavior: instead of trying to fill up as many transmit 'descriptors' as possible, it should never be possible now to have more than one transmission in progress at any one time. That is, instead of trying to fill up all four TX 'descriptors' and issue four transmissions in rapid succession and then waiting to clean up the buffers later, it issues a single transmission, waits for completion, then issues another transmission, waits for completion, and so on. This will probably worsen performance at 100Mbps, but it would be interesting to see if it fixes your problem. Please try it and let me know what happens. (I left the loop detection code in place just for giggles.) -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "Mulder, toads just fell from the sky!" "I guess their parachutes didn't open." ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message