All of lore.kernel.org
 help / color / mirror / Atom feed
* [ath9k-devel] Fwd: Kernel warning in ath9k related to wpa_supplicant scanning
       [not found] <195AAF39-2B75-4D7B-A1E8-CACFD47717D1@comcast.net>
@ 2011-10-20 20:27 ` Bryan Phillippe
  2011-10-24 23:29   ` Mohammed Shafi
  0 siblings, 1 reply; 4+ messages in thread
From: Bryan Phillippe @ 2011-10-20 20:27 UTC (permalink / raw)
  To: ath9k-devel


Thoughts on who's to blame and how to resolve?

Thanks,
--
-bp


Begin forwarded message:

> From: "B. J."
> Date: October 20, 2011 1:26:21 PM PDT
> To: hostap at lists.shmoo.com
> Subject: Kernel warning in ath9k related to wpa_supplicant scanning
> 
> 
> This is with wpa_supplicant-0.7.3 and compat-wireless-2011-10-10:
> 
> ...
> nl80211: Event message available
> nl80211: New scan results available
> Received scan results (0 BSSes)
> BSS: Start scan result update 6
> New scan results available
> Selecting BSS from priority group 0
> Try to find WPA-enabled AP
> Try to find non-WPA AP
> No suitable network found
> Setting scan request: 5 sec 0 usec
> RTM_NEWLINK: operstate=0 ifi_flags=0x3 ([UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> Starting AP scan for wildcard SSID
> nl80211: Scan SSID - hexdump_ascii(len=0): [NULL]
> Scan requested (ret=0) - scan timeout 30 seconds
> nl80211: Event message available
> nl80211: Scan trigger
> ------------[ cut here ]------------
> WARNING: at /home/bp/P4/UTM-mainline/components/kernel/build/richland/ath9k/net/mac80211/rx.c:3002 ieee80211_rx+0xf4/0x9dc [mac80211]()
> Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 93 (0x5d)
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20111020/f1a7750c/attachment.htm 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [ath9k-devel] Fwd: Kernel warning in ath9k related to wpa_supplicant scanning
  2011-10-20 20:27 ` [ath9k-devel] Fwd: Kernel warning in ath9k related to wpa_supplicant scanning Bryan Phillippe
@ 2011-10-24 23:29   ` Mohammed Shafi
  2011-10-25 23:19     ` [ath9k-devel] iwpriv and ath9k driver just login
  0 siblings, 1 reply; 4+ messages in thread
From: Mohammed Shafi @ 2011-10-24 23:29 UTC (permalink / raw)
  To: ath9k-devel

On Fri, Oct 21, 2011 at 1:57 AM, Bryan Phillippe <bp@terran.org> wrote:
>
> Thoughts on who's to blame and how to resolve?

its the driver,  the rate is is taken as a HT rate,

 if (rx_stats->rs_rate & 0x80) {
                /* HT rate */
                rxs->flag |= RX_FLAG_HT;
                if (rx_stats->rs_flags & ATH9K_RX_2040)
                        rxs->flag |= RX_FLAG_40MHZ;
                if (rx_stats->rs_flags & ATH9K_RX_GI)
                        rxs->flag |= RX_FLAG_SHORT_GI;
                rxs->rate_idx = rx_stats->rs_rate & 0x7f;
                return 0;
        }

please provide lspci so that we can get the descriptor dump for rx-status.
also please whether your consistently getting elaborating how to
recreate the issue.
thanks.

> Thanks,
> --
> -bp
>
> Begin forwarded message:
>
> From: "B. J."
> Date: October 20, 2011 1:26:21 PM PDT
> To: hostap at lists.shmoo.com
> Subject: Kernel warning in ath9k related to wpa_supplicant scanning
>
>
> This is with wpa_supplicant-0.7.3 and compat-wireless-2011-10-10:
>
> ...
> nl80211: Event message available
> nl80211: New scan results available
> Received scan results (0 BSSes)
> BSS: Start scan result update 6
> New scan results available
> Selecting BSS from priority group 0
> Try to find WPA-enabled AP
> Try to find non-WPA AP
> No suitable network found
> Setting scan request: 5 sec 0 usec
> RTM_NEWLINK: operstate=0 ifi_flags=0x3 ([UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> Starting AP scan for wildcard SSID
> nl80211: Scan SSID - hexdump_ascii(len=0): [NULL]
> Scan requested (ret=0) - scan timeout 30 seconds
> nl80211: Event message available
> nl80211: Scan trigger
> ------------[ cut here ]------------
> WARNING: at
> /home/bp/P4/UTM-mainline/components/kernel/build/richland/ath9k/net/mac80211/rx.c:3002
> ieee80211_rx+0xf4/0x9dc [mac80211]()
> Rate marked as an HT rate but passed status->rate_idx is not an MCS index
> [0-76]: 93 (0x5d)
>
>
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>



-- 
shafi

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [ath9k-devel] iwpriv and ath9k driver
  2011-10-24 23:29   ` Mohammed Shafi
@ 2011-10-25 23:19     ` just login
  2011-10-30 17:23       ` C. McPherson
  0 siblings, 1 reply; 4+ messages in thread
From: just login @ 2011-10-25 23:19 UTC (permalink / raw)
  To: ath9k-devel

Hi,

I have a recent (daily) from compat-wireless and have the (ath9k AR9160) driver working fine.

I wanted to play with private extensions, if any - with iwpriv and see "No private ioctls" for the wlan0 interface. 

Is this expected or should I be using some compile time flags to enable visibility of private extensions to iwpriv for the ath9k driver.

Thanks
-J
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20111025/8b789293/attachment.htm 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [ath9k-devel] iwpriv and ath9k driver
  2011-10-25 23:19     ` [ath9k-devel] iwpriv and ath9k driver just login
@ 2011-10-30 17:23       ` C. McPherson
  0 siblings, 0 replies; 4+ messages in thread
From: C. McPherson @ 2011-10-30 17:23 UTC (permalink / raw)
  To: ath9k-devel

I am using iwpriv  (Private IOCTL's). You have to modify cfg80211 
(should be under net/wireless). I put my iwpriv's in the wext-compat.c 
file. You have to do this because ath9k uses mac80211 API and cfg80211 API.

-Tex

On 10/25/2011 07:19 PM, just login wrote:
> Hi,
>
> I have a recent (daily) from compat-wireless and have the (ath9k 
> AR9160) driver working fine.
>
> I wanted to play with private extensions, if any - with iwpriv and see 
> "No private ioctls" for the wlan0 interface.
>
> Is this expected or should I be using some compile time flags to 
> enable visibility of private extensions to iwpriv for the ath9k driver.
>
> Thanks
> -J
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20111030/e9f2b7ca/attachment.htm 

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-10-30 17:23 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <195AAF39-2B75-4D7B-A1E8-CACFD47717D1@comcast.net>
2011-10-20 20:27 ` [ath9k-devel] Fwd: Kernel warning in ath9k related to wpa_supplicant scanning Bryan Phillippe
2011-10-24 23:29   ` Mohammed Shafi
2011-10-25 23:19     ` [ath9k-devel] iwpriv and ath9k driver just login
2011-10-30 17:23       ` C. McPherson

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.