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

[Gertjan van Wingerde <gwingerde@gmail.com>]

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 bisected the problem to the commit e77f5ff92f5ef43c842e97136edcb68c61afe588
> above.
> 
> After I removed the lines below in rt2x00dev.c:
> rt2x00dev->hw->extra_tx_headroom =
>         max_t(unsigned int, IEEE80211_TX_STATUS_HEADROOM,
>               rt2x00dev->ops->extra_tx_headroom);
> 
> /*
> * Take TX headroom required for alignment into account.
> */
> if (test_bit(DRIVER_REQUIRE_L2PAD, &rt2x00dev->flags))
>         rt2x00dev->hw->extra_tx_headroom += RT2X00_L2PAD_SIZE;
> else if (test_bit(DRIVER_REQUIRE_DMA, &rt2x00dev->flags))
>         rt2x00dev->hw->extra_tx_headroom += RT2X00_ALIGN_SIZE;
> 
> added the line:
> rt2x00dev->hw->extra_tx_headroom = rt2x00dev->ops->extra_tx_headroom;
> 
> and compiled the kernel 2.6.33-rc2 again, all worked fine.
> 

That is very strange as this patch was meant to send TX statuses of frames
towards monitor interfaces (which is what hostapd is using).

What kind of rt2x00 device are you using (and which of the rt2x00 drivers)?

Are there any messages in dmesg when this happens?
Can you check whether there are any messages in dmesg in the working situation?

---
Gertjan.