linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Baier <Markus_Baier@web.de>
To: linux-wireless@vger.kernel.org
Subject: Re: [BISECTED] [PATCH v2 8/8] rt2x00: Properly request tx headroom for alignment operations.
Date: Mon, 21 Dec 2009 00:45:02 +0000 (UTC)	[thread overview]
Message-ID: <loom.20091221T011150-33@post.gmane.org> (raw)
In-Reply-To: 4B2E8729.7050501@gmail.com

Gertjan van Wingerde <gwingerde@...> writes:

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

The device is a PCMICA card with the RT2561 chipset.
The driver is the rt61pci driver.

>>lsmod
Module                  Size  Used by
rt61pci                18193  0
crc_itu_t               1017  1 rt61pci
rt2x00pci               4189  1 rt61pci
rt2x00lib              22940  2 rt61pci,rt2x00pci
eeprom_93cx6             960  1 rt61pci


> Are there any messages in dmesg when this happens?

No, there are no messages in dmesg


There are no differences in the dmesg output between
the working and the broken kernel
Here is the dmesg output:

rt61pci 0000:02:00.0: enabling device (0000 -> 0002)
rt61pci 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
rt61pci 0000:02:00.0: setting latency timer to 64
phy0 -> rt61pci_validate_eeprom: EEPROM recovery - NIC: 0xff80
phy0 -> rt61pci_validate_eeprom: EEPROM recovery - Led: 0xe0ff
phy0 -> rt2x00_print_chip: Info - Chipset detected - rt: 0302, rf: 0003, rev:
0002561c.
phy0: Selected rate control algorithm 'minstrel'
Registered led device: rt61pci-phy0::radio
Registered led device: rt61pci-phy0::assoc
phy0 -> rt2x00lib_request_firmware: Info - Loading firmware file 'rt2561.bin'.
rt61pci 0000:02:00.0: firmware: requesting rt2561.bin
phy0 -> rt2x00lib_request_firmware: Info - Firmware detected - version: 0.8.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 3, CWmax: 4,
Aifs: 2, TXop: 102.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 5,
Aifs: 2, TXop: 188.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10,
Aifs: 3, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10,
Aifs: 7, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 3, CWmax: 4,
Aifs: 2, TXop: 102.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 5,
Aifs: 2, TXop: 188.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10,
Aifs: 3, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10,
Aifs: 7, TXop: 0.
cfg80211: Calling CRDA for country: DE
cfg80211: Regulatory domain changed to country: DE
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
    (5150000 KHz - 5350000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    (5470000 KHz - 5725000 KHz @ 40000 KHz), (N/A, 2698 mBm)
device wlan0 entered promiscuous mode
br0: port 2(wlan0) entering learning state
br0: port 1(eth0) entering forwarding state
br0: port 2(wlan0) entering forwarding state


------------------------------------------------------------------------
But there are differences in the hostapd log.
Here is the log output from the broken system:

>>hostapd -tddd /etc/hostapd/wpa2_ap.conf
....
1261351288.111499: MGMT (TX callback) fail
1261351288.111513: mgmt::proberesp cb
1261351290.256576: STA xx:xx:xx:xx:xx:xx sent probe request for our SSID
1261351290.257122: STA xx:xx:xx:xx:xx:xx sent probe request for our SSID
1261351290.257735: STA xx:xx:xx:xx:xx:xx sent probe request for our SSID
1261351290.258351: STA xx:xx:xx:xx:xx:xx sent probe request for our SSID
1261351290.258971: STA xx:xx:xx:xx:xx:xx sent probe request for our SSID
1261351290.268092: MGMT (TX callback) fail
1261351290.268116: mgmt::proberesp cb
1261351290.277054: MGMT (TX callback) fail
1261351290.277074: mgmt::proberesp cb
1261351290.285832: MGMT (TX callback) fail
1261351290.285848: mgmt::proberesp cb
1261351290.294522: MGMT (TX callback) fail
1261351290.294538: mgmt::proberesp cb
1261351290.303364: MGMT (TX callback) fail
1261351290.303379: mgmt::proberesp cb
1261351291.334698: MGMT
1261351291.334719: mgmt::auth
1261351291.334727: authentication: STA=xx:xx:xx:xx:xx:xx auth_alg=0
auth_transaction=1 status_code=0 wep=0
1261351291.334769: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authentication OK
(open system)
1261351291.334795: wlan0: STA xx:xx:xx:xx:xx:xx MLME:
MLME-AUTHENTICATE.indication(xx:xx:xx:xx:xx:xx, OPEN_SYSTEM)
1261351291.334817: wlan0: STA xx:xx:xx:xx:xx:xx MLME:
MLME-DELETEKEYS.request(xx:xx:xx:xx:xx:xx)
1261351291.334830: authentication reply: STA=xx:xx:xx:xx:xx:xx auth_alg=0
auth_transaction=2 resp=0 (IE len=0)
1261351291.339781: MGMT (TX callback) fail
1261351291.339794: mgmt::auth cb
1261351291.339813: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: did not
acknowledge authentication response
....

------------------------------------------------------------------------
Here the log output from the working system:

>>hostapd -tddd /etc/hostapd/wpa2_ap.conf
....
1261353953.151469: MGMT (TX callback) ACK
1261353956.790339: STA xx:xx:xx:xx:xx:xx sent probe request for our SSID
1261353956.790871: STA xx:xx:xx:xx:xx:xx sent probe request for our SSID
1261353956.791481: STA xx:xx:xx:xx:xx:xx sent probe request for our SSID
1261353956.792098: STA xx:xx:xx:xx:xx:xx sent probe request for our SSID
1261353956.792717: STA xx:xx:xx:xx:xx:xx sent probe request for our SSID
1261353956.794326: MGMT (TX callback) ACK
1261353956.794339: mgmt::proberesp cb
1261353956.795806: MGMT (TX callback) ACK
1261353956.795827: mgmt::proberesp cb
1261353956.797184: MGMT (TX callback) ACK
1261353956.797195: mgmt::proberesp cb
1261353956.798558: MGMT (TX callback) ACK
1261353956.798569: mgmt::proberesp cb
1261353956.799907: MGMT (TX callback) ACK
1261353956.799918: mgmt::proberesp cb
1261353957.868214: MGMT
1261353957.868236: mgmt::auth
1261353957.868245: authentication: STA=xx:xx:xx:xx:xx:xx auth_alg=0
auth_transaction=1 status_code=0 wep=0
1261353957.868266:   New STA
1261353957.868313: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authentication OK
(open system)
1261353957.868344: wlan0: STA xx:xx:xx:xx:xx:xx MLME:
MLME-AUTHENTICATE.indication(xx:xx:xx:xx:xx:xx, OPEN_SYSTEM)
1261353957.868366: wlan0: STA xx:xx:xx:xx:xx:xx MLME:
MLME-DELETEKEYS.request(xx:xx:xx:xx:xx:xx)
1261353957.868385: authentication reply: STA=xx:xx:xx:xx:xx:xx auth_alg=0
auth_transaction=2 resp=0 (IE len=0)
1261353957.869332: MGMT (TX callback) ACK
1261353957.869347: mgmt::auth cb
1261353957.869368: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
....

Please tell me if some information are missing.


Regards,
Markus


  reply	other threads:[~2009-12-21  0:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-23 21:44 [PATCH v2 0/8] Assorted fixes and cleanups for rt2x00 and mac80211 Gertjan van Wingerde
2009-11-23 21:44 ` [PATCH v2 1/8] rt2x00: Only initialize HT on rt2800 devices that support it Gertjan van Wingerde
2009-11-23 21:44   ` [PATCH v2 2/8] rt2x00: Remove unused variable frame_control from rt2x00mac_tx Gertjan van Wingerde
2009-11-23 21:44     ` [PATCH v2 3/8] rt2x00: Clean up use of rt2x00_intf_is_pci Gertjan van Wingerde
2009-11-23 21:44       ` [PATCH v2 4/8] rt2x00: Fix typo (lengt --> length) in rt2x00queue.c Gertjan van Wingerde
2009-11-23 21:44         ` [PATCH v2 5/8] rt2x00: Whitespace cleanup Gertjan van Wingerde
2009-11-23 21:44           ` [PATCH v2 6/8] rt2x00: Centralize setting of extra TX headroom requested by rt2x00 Gertjan van Wingerde
2009-11-23 21:44             ` [PATCH v2 7/8] mac80211: Add define for TX headroom reserved by mac80211 itself Gertjan van Wingerde
2009-11-23 21:44               ` [PATCH v2 8/8] rt2x00: Properly request tx headroom for alignment operations Gertjan van Wingerde
2009-11-24 17:19                 ` Ivo van Doorn
2009-11-24 19:12                   ` Gertjan van Wingerde
2009-11-24 20:04                     ` Ivo van Doorn
2009-11-25 19:47                 ` John W. Linville
2009-11-25 21:29                   ` Gertjan van Wingerde
2009-11-25 21:48                     ` John W. Linville
2009-12-20 15:42                 ` [BISECTED] " Markus Baier
2009-12-20 20:20                   ` Gertjan van Wingerde
2009-12-21  0:45                     ` Markus Baier [this message]
2009-12-21  6:33                     ` Pavel Roskin
2009-12-21 16:26                       ` Gertjan van Wingerde
2009-12-21 19:17                         ` John W. Linville
2009-12-22  0:22                           ` Gertjan van Wingerde
2009-12-22  5:25                         ` Pavel Roskin
2009-12-22  8:13                           ` Gertjan van Wingerde
2009-12-22 10:55                             ` Markus Baier
2009-12-22 14:18                               ` Gertjan van Wingerde
2009-12-22 15:03                             ` Pavel Roskin
2009-11-23 23:22               ` [PATCH v2 7/8] mac80211: Add define for TX headroom reserved by mac80211 itself Johannes Berg
2009-11-24 17:13             ` [PATCH v2 6/8] rt2x00: Centralize setting of extra TX headroom requested by rt2x00 Ivo van Doorn
2009-11-24 17:13           ` [PATCH v2 5/8] rt2x00: Whitespace cleanup Ivo van Doorn
2009-11-23 22:18   ` [rt2x00-users] [PATCH v2 1/8] rt2x00: Only initialize HT on rt2800 devices that support it David Ellingsworth
2009-11-24 17:12     ` Ivo van Doorn

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=loom.20091221T011150-33@post.gmane.org \
    --to=markus_baier@web.de \
    --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).