Date: Mon, 15 Mar 1999 21:51:19 -0500 From: "Edward Ing" <inge@home.com> To: "Greg Lehey" <grog@lemis.com> Subject: Re: TCP/IP on LAN drops after a few minutes. Message-ID: <001901be6f57$de835760$4f4b7018@mimico.firstmaple.ca>
next in thread | raw e-mail | index | archive | help
Now I tried the PR search myself by using a query. But I did not get an answer. How did you search it? Anyways, I have three of these DE203 lying around. Would it be worthwhile for me to send FreeBSD one of these for testing debug purposes. Or is it almost obsolete and not worth the time to fix it. Edward Ing -> >The next thing would be to query the PR database. There I see: > >> Number: 4292 >> Category: kern >> Synopsis: le0 (DE203) goes OACTIVE after some time >> Confidential: no >> Severity: serious >> Priority: medium >> Responsible: freebsd-bugs >> State: closed >> Class: sw-bug >> Quarter: >> Keywords: >> Date-Required: >> Submitter-Id: current-users >> Arrival-Date: Wed Aug 13 03:10:01 PDT 1997 >> Closed-Date: >> Last-Modified: Sun Oct 12 06:57:35 PDT 1997 >> Originator: Olaf Erb >> Release: FreeBSD 2.2-STABLE i386 > >Looking in more detail, > >>> Description: >> >> le0 goes OACTIVE after some time, errors like "no buffer space >> available" occur. Only downing/deleting and re-configuring the interface >> brings it back, for some packets though, then it hangs again. The problem >> mainly appears while acting as bootp/tftp server, after some < 100kB of data >> transfered. >> Have a look at >> f [1995/07/04] kern/587 if_le hangs on OACTIVE with 2k buffer >> too. >> >> >>> How-To-Repeat: >> >> use a DE203 with msize 2048 and serve bootp/tftp/nfs over it, or just >> large transfers over some time. >> >>> Fix: >> >> switched the card with nicsetup.exe to 32768 bytes msize. This isn't >> recognised by the driver, because msize is hardcoded there to 2048. >> >> A quick change in if_le.c to 32768 (lemac_probe()) solved this problem, >> but this is no real fix. >> Hardcoded value should be replaced by using the probed msize, if it's >> possible (this info should be in eeprom, though I don't know how to figure >> it out). >> >> This doesn't solve the problem. It just avoids it. I wish I know >> enough about FreeBSD to poke around an figure out what is going on. > >Yup, it looks as if this problem hasn't really been solved. I'd >suggest you put in a new PR, referring to this one, and maybe somebody >will fix it this time. > >Greg >-- >See complete headers for address, home page and phone numbers >finger grog@lemis.com for PGP public key > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001901be6f57$de835760$4f4b7018>