Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 May 2006 13:44:39 -0700
From:      Ross Finlayson <finlayson@live555.com>
To:        freebsd-mobile@freebsd.org
Subject:   Re: More 'resource' problems with "ath0"
Message-ID:  <7.0.1.0.1.20060519133359.02083d70@live555.com>
In-Reply-To: <446C23C0.8030501@errno.com>
References:  <7.0.1.0.1.20060517080119.01e00df8@live555.com> <446B44B0.5030908@errno.com> <7.0.1.0.1.20060517125415.01e0f568@live555.com> <446B8F14.80502@errno.com> <7.0.1.0.1.20060517153640.01e0f568@live555.com> <446C0C22.4090700@errno.com> <7.0.1.0.1.20060517230855.01ddd570@live555.com> <446C23C0.8030501@errno.com>

next in thread | previous in thread | raw e-mail | index | archive | help

>>So far I have not seen the problem recur after I switched to using 11g.

Unfortunately the problem arose again today, even when running 11g:

May 19 13:24:40 ns named[398]: client 66.80.0.7#1025: error sending 
response: not enough free resources
May 19 13:24:40 ns named[398]: client 66.80.0.7#1025: error sending 
response: not enough free resources

>So your clients are operating in ps mode

Yes, some of the clients of one of the access points (the one that's 
running at the coffee shop, which is where the problem arose again 
today) will be operating in power-save mode.  (Because these clients 
are random 'walk in off the street' types, it's not possible in 
general to prevent them from using power-save mode.)

>  and this may be the same issue seen by one other person.  I'm 
> working on it but am traveling right now so nothing will happen for 
> a while (and it's also hard to reproduce).

Is there any diagnostic tool that I could run - when I notice the 
problem occurring - that might help you in tracking down and solving 
this problem?

Also, do you think that Joao's suggestion - copied below - is worth trying?

 From "AT Matik <asstec@matik.com.br>":
>I saw this often on machines with network connection quality problems,
>especially on wireless connections. Seems the bufferspace get full and then
>the error comes up which may cause service problems. The problem is more
>frequent with udp traffic.
>
>normally you can workaround this by setting sysctls
>
>net.inet.udp.recvspace=65536
>net.inet.udp.maxdgram=131072
>
>or other values fitting to your needs





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7.0.1.0.1.20060519133359.02083d70>