Date: Wed, 10 Nov 1999 09:25:23 -0800 (PST) From: Doug Ambrisko <ambrisko@whistle.com> To: billm@danger.ms (Bill Marquette) Cc: freebsd-current@FreeBSD.ORG Subject: Re: No buffer space available errors Message-ID: <199911101725.JAA68371@whistle.com> In-Reply-To: <Pine.BSF.4.10.9911072157590.10718-100000@nuke.danger.ms> from Bill Marquette at "Nov 7, 99 10:26:06 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Bill Marquette writes: | For the last week and a half or so I've been trying to track this down | assuming it was a configuration error on my part or a problem with my | ISP's DHCP configuration. After switching from a DEC 20141 chipset card | to a 3com 3c905, I found I was still having problems although the error | message had changed. I'm now back to the DEC card cause I found more | results in the mailing lists on the errors I was seeing. | | At first it appeared to be dhclient having issues, but I've finally found | occurances of other programs showing symptoms prior to dhclient log | entries. Also, until today I couldn't replicate the problem while sitting | at the console, it would only show itself after I'd been away for a few | minutes (I swear it has a mind of it's own) usually, when I was going to | be away for more than 10-15 minutes. Today I managed to force the machine | to have problems by doing multiple simultaneous downloads and uploads, I | was running about 100K/sec through the NIC. On one out of 8 machines, I ran into this problem. My network is running at 100BaseTX. I noticed that ifconfig showed OACTIVE flag set and I was running in autosense mode. So I setup the media to 100BaseTX and now it works okay. My guess is the autosense gets confused sometimes. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911101725.JAA68371>