Dear Bob,
I have found a solution for my problem.
Patch from "Johannes Berg <johannes.berg@xxxxxxxxx>" fixes a problem.
#Processing an association response could take a bit
#of time while we set up the hardware etc. During that
#time, the AP might already send a blockack request.
#If this happens very quickly on a fairly slow machine,
#we can end up processing the blockack request before
#the association processing has finished. Since the
#blockack processing cannot sleep right now, we also
#cannot make it wait in the driver.
> > I have found that ATH5k has severe problems during association to AP.
> > Sometimes it needs more than 100 attempts to association, before it connects
> > to AP.
> Did it work in previous kernels?
The association has beed bad - 2 to 5 attempts needed,
but not 150. So previous kernels did not behave so wrong.
> You said you reverted 6b5d117eddc09cd976ad8030d715f4 and still have the
> problem, right? Are you sure you booted the kernel with the revert?
Yes, because I have ATH5k inside modules. And when I type:
make KLIB=/usr/src/linux-2.6.32.11 KLIB_BUILD=/usr/src/linux-2.6.32.11
make KLIB=/usr/src/linux-2.6.32.11 KLIB_BUILD=/usr/src/linux-2.6.32.11 KMODPATH_ARG='INSTALL_MOD_PATH=' install
Modules in /lib/modules are updated.
> > [ 149.926717] wlan1: direct probe to 00:15:6d:d6:2a:9d (try 1)
> > [ 150.013353] eth3: no IPv6 routers present
> > [ 150.126699] wlan1: direct probe to 00:15:6d:d6:2a:9d (try 2)
> > [ 150.326707] wlan1: direct probe to 00:15:6d:d6:2a:9d (try 3)
> > [ 150.526696] wlan1: direct probe to 00:15:6d:d6:2a:9d timed out
>
> Probably traffic is not being sent or received from one side.
But when association is done (after 150 attempts), the client runs without any packetloss
without any problems.
regards
Jara
> --
> Bob Copeland %% www.bobcopeland.com
Attachment:
patch_wireless.txt
Description: Binary data
