Search Linux Wireless

Re: [BISECTED] [PATCH v2 8/8] rt2x00: Properly request tx headroom for alignment operations.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/21/09 07:33, Pavel Roskin wrote:
> Quoting Gertjan van Wingerde <gwingerde@xxxxxxxxx>:
> 
>> On 12/20/09 16:42, Markus Baier wrote:
>>> After my latest git pull to the kernel version 2.6.33-rc1-wl
>>> no client was able to connect to my hostapd (v0.6.9) AP.
>>> I found a lot of the following entries in the syslog:
>>>
>>> wlan0: STA xx:xx:xx:xx:xx:xx
>>> IEEE 802.11: did not acknowledge authentication response
> 
> I'm also having problems with rt2x00 support the current
> wireless-testing, but in the station mode.  The device is using rt61pci
> driver.  Association to an AP with WEP fails.
> 
> [  147.930019] wlan2: direct probe to AP 00:11:6b:28:0b:92 (try 1)
> [  148.130010] wlan2: direct probe to AP 00:11:6b:28:0b:92 (try 2)
> [  148.330009] wlan2: direct probe to AP 00:11:6b:28:0b:92 (try 3)
> [  148.530008] wlan2: direct probe to AP 00:11:6b:28:0b:92 timed out
> [  152.942516] wlan2: direct probe to AP 00:11:6b:28:0b:92 (try 1)
> [  153.142512] wlan2: direct probe to AP 00:11:6b:28:0b:92 (try 2)
> [  153.340011] wlan2: direct probe to AP 00:11:6b:28:0b:92 (try 3)
> [  153.540008] wlan2: direct probe to AP 00:11:6b:28:0b:92 timed out
> 
> It worked fine with wireless-testing when it was 2.6.32 based.
> 
>>> After I removed the lines below in rt2x00dev.c:
> 
> That "patch" is helping me too!  The association is working now.
> 
>> That is very strange as this patch was meant to send TX statuses of
>> frames
>> towards monitor interfaces (which is what hostapd is using).
> 
> I'm not using monitor mode.  I only have one vif in the station mode.
> 
> My debugging shows that the headroom is 0 with the "patch".  Without it,
> the headroom is 17 (13 from IEEE80211_TX_STATUS_HEADROOM plus 4 from
> RT2X00_ALIGN_SIZE).
> 
> Perhaps non-zero headroom is not handled correctly?
> 

Hmmm, perhaps the problem is that the headroom is not a multiple of 4.
Can you check what happens when you set the extra_tx_headroom fixed to e.g. 20?

The driver should be able to handle this, but maybe there is something wrong
with the alignment.

---
Gertjan.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux