From: "John W. Linville" <linville@tuxdriver.com>
To: Dennis Borgmann <dennis.borgmann@googlemail.com>
Cc: linux-wireless@vger.kernel.org, hostap@lists.shmoo.com
Subject: Re: "ressource temporarily unavailable" on 2.4 GHz, not on 5GHz
Date: Wed, 16 Jun 2010 10:21:58 -0400 [thread overview]
Message-ID: <20100616142158.GC2404@tuxdriver.com> (raw)
In-Reply-To: <4C18DA3D.1030303@googlemail.com>
On Wed, Jun 16, 2010 at 04:05:49PM +0200, Dennis Borgmann wrote:
> Hello wireless-list!
> Hello hostapd-list!
>
> I am using ath5k with hostapd-0.6.9 on a debian running kernel 2.6.34
> and I am observing a "ressource temporarily unavailable" - error code 11
> if I pump out multicast-packets quite fast. I wrote a small
> test-program, that handles this test and as soon as I go down to a
> 8ms-pause or below in betweens the packets, the error is thrown quite
> soon after starting the program. Funny thing is, that this error only
> occurs in g-band (2.4 GHz), not in a-band (5GHz).
>
> What could be the problem? Is this due to backoff-times in 2.4 GHz, that
> don't occur on 5 GHz? Or could this be a bug?
My only initial thought is that the 2.5GHz band is usually more
utilized. So there is more likely to be retransmissions, etc.
> Find attached my small piece of code to test and reproduce this effect.
Perhaps you could include actual dmesg output?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-06-16 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 14:05 "ressource temporarily unavailable" on 2.4 GHz, not on 5GHz Dennis Borgmann
2010-06-16 14:21 ` John W. Linville [this message]
2010-06-16 14:23 ` John W. Linville
2010-06-16 14:38 ` Bob Copeland
2010-06-17 12:13 ` Dennis Borgmann
2010-06-17 14:38 ` Dennis Borgmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100616142158.GC2404@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dennis.borgmann@googlemail.com \
--cc=hostap@lists.shmoo.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).