Date: Wed, 10 Nov 1999 08:09:26 -1000 (HST) From: Bill Marquette <billm@danger.ms> To: Doug Ambrisko <ambrisko@whistle.com> Cc: freebsd-current@freebsd.org Subject: Re: No buffer space available errors Message-ID: <Pine.BSF.4.10.9911100801110.3899-100000@nuke.danger.ms> In-Reply-To: <199911101725.JAA68371@whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 10 Nov 1999, Doug Ambrisko wrote: > 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, thanks for the tip, I'll give that a try as I haven't been forcing either card to 10Mbit or TP connections. I have added to the mystery however and this is aggravatingly puzzling. In my previous message I had mentioned that walking away fromt he console for any length of time would cause the machine to generate the "No buffer space" errors. Since then I've turned off my screensaver (Matrix from KDE) and the system has stabilized completely; well almost completely. I can still duplicate the buffer situation and I've still seen it occur when doing fairly high bandwidth (for cable, not for ethernet) file transfers. If I can manage to bring the xfer rate up to around 100K/sec total between inbound and outbound I experience the "Out of buffer" messages within a couple minutes. netstat -m doesn't show anything unusual. I am going to try removing both NMBCLUSTERS and NBUF from my config and just use a maxusers of 128 and see how that goes. --Bill 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?Pine.BSF.4.10.9911100801110.3899-100000>