* Re: [PATCH] mac80211: Allow single vif mac address change with addr_mask
From: Jakub Kiciński @ 2013-05-21 15:10 UTC (permalink / raw)
To: Helmut Schaa
Cc: linux-wireless, johannes, IvDoorn, gwingerde, stf_xl,
Alessandro Lannocca, Bruno Randolf
In-Reply-To: <1369140893-22622-1-git-send-email-helmut.schaa@googlemail.com>
On Tue, 21 May 2013 14:54:53 +0200, Helmut Schaa wrote:
> When changing the MAC address of a single vif mac80211 will check if the new
> address fits into the address mask specified by the driver. This only needs
> to be done when using multiple BSSIDs. Hence, check the new address only
> against all other vifs.
Oh, I see that you already posted this patch for review!
I think we should also take care of the way addresses for new
interfaces are chosen otherwise they'll just pick up
perm_addr and we will end up with incompatible MACs.
I created a patch for a user who reported this problem to
rt2x00 ML independently from Helmut.
--->8------------------
>From 63b32f4509d2c2bcf0ad791faa624b56a1947748 Mon Sep 17 00:00:00 2001
From: Jakub Kicinski <kubakici@wp.pl>
Date: Tue, 21 May 2013 13:05:43 +0200
Subject: [PATCH] mac80211: allow changing mac address on mac-masking devices
Some devices support multiple MAC addresses by
masking last few bits of the address. Address
compatibility has to be checked only when there
is more than one interface - otherwise we can
just overwrite current address.
While at it fix inverted flow at the end of
ieee80211_change_mac.
Signed-off-by: Jakub Kicinski <kubakici@wp.pl>
---
net/mac80211/iface.c | 22 ++++++++++++++++++----
1 file changed, 18 insertions(+), 4 deletions(-)
diff --git a/net/mac80211/iface.c b/net/mac80211/iface.c
index 60f1ce5..367aa3b 100644
--- a/net/mac80211/iface.c
+++ b/net/mac80211/iface.c
@@ -159,8 +159,9 @@ static int ieee80211_change_mtu(struct net_device *dev, int new_mtu)
return 0;
}
-static int ieee80211_verify_mac(struct ieee80211_local *local, u8 *addr)
+static int ieee80211_verify_mac(struct ieee80211_sub_if_data *target, u8 *addr)
{
+ struct ieee80211_local *local = target->local;
struct ieee80211_sub_if_data *sdata;
u64 new, mask, tmp;
u8 *m;
@@ -184,6 +185,8 @@ static int ieee80211_verify_mac(struct ieee80211_local *local, u8 *addr)
list_for_each_entry(sdata, &local->interfaces, list) {
if (sdata->vif.type == NL80211_IFTYPE_MONITOR)
continue;
+ if (sdata == target)
+ continue;
m = sdata->vif.addr;
tmp = ((u64)m[0] << 5*8) | ((u64)m[1] << 4*8) |
@@ -209,14 +212,15 @@ static int ieee80211_change_mac(struct net_device *dev, void *addr)
if (ieee80211_sdata_running(sdata))
return -EBUSY;
- ret = ieee80211_verify_mac(sdata->local, sa->sa_data);
+ ret = ieee80211_verify_mac(sdata, sa->sa_data);
if (ret)
return ret;
ret = eth_mac_addr(dev, sa);
+ if (ret)
+ return ret;
- if (ret == 0)
- memcpy(sdata->vif.addr, sa->sa_data, ETH_ALEN);
+ memcpy(sdata->vif.addr, sa->sa_data, ETH_ALEN);
return ret;
}
@@ -1479,7 +1483,17 @@ static void ieee80211_assign_perm_addr(struct ieee80211_local *local,
break;
}
+ /*
+ * Pick address of existing interface in case user changed
+ * MAC address manually, default to perm_addr.
+ */
m = local->hw.wiphy->perm_addr;
+ list_for_each_entry(sdata, &local->interfaces, list) {
+ if (sdata->vif.type == NL80211_IFTYPE_MONITOR)
+ continue;
+ m = sdata->vif.addr;
+ break;
+ }
start = ((u64)m[0] << 5*8) | ((u64)m[1] << 4*8) |
((u64)m[2] << 3*8) | ((u64)m[3] << 2*8) |
((u64)m[4] << 1*8) | ((u64)m[5] << 0*8);
--
1.8.1.4
^ permalink raw reply related
* R: [PATCH] mac80211: Allow single vif mac address change with addr_mask
From: Alessandro Lannocca @ 2013-05-21 15:51 UTC (permalink / raw)
To: 'Helmut Schaa'; +Cc: linux-wireless
In-Reply-To: <1369140893-22622-1-git-send-email-helmut.schaa@googlemail.com>
Tested right now against compat-drivers-2013-03-28-5-u and I can confirm it
works.
Thank you for your effort!
Alessandro Lannocca
-----Messaggio originale-----
Da: Helmut Schaa [mailto:helmut.schaa@googlemail.com]
Inviato: martedì 21 maggio 2013 14.55
A: linux-wireless@vger.kernel.org
Cc: johannes@sipsolutions.net; IvDoorn@gmail.com; gwingerde@gmail.com;
stf_xl@wp.pl; Helmut Schaa; Alessandro Lannocca; Bruno Randolf
Oggetto: [PATCH] mac80211: Allow single vif mac address change with
addr_mask
When changing the MAC address of a single vif mac80211 will check if the new
address fits into the address mask specified by the driver. This only needs
to be done when using multiple BSSIDs. Hence, check the new address only
against all other vifs.
Resolves:
https://bugzilla.kernel.org/show_bug.cgi?id=57371
Reported-by: Alessandro Lannocca <alessandro.lannocca@gmail.com>
Cc: Alessandro Lannocca <alessandro.lannocca@gmail.com>
Cc: Bruno Randolf <br1@thinktube.com>
Signed-off-by: Helmut Schaa <helmut.schaa@googlemail.com>
---
net/mac80211/iface.c | 16 ++++++++++------
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/net/mac80211/iface.c b/net/mac80211/iface.c index
60f1ce5..c1a8c79 100644
--- a/net/mac80211/iface.c
+++ b/net/mac80211/iface.c
@@ -159,9 +159,10 @@ static int ieee80211_change_mtu(struct net_device *dev,
int new_mtu)
return 0;
}
-static int ieee80211_verify_mac(struct ieee80211_local *local, u8 *addr)
+static int ieee80211_verify_mac(struct ieee80211_sub_if_data *sdata, u8
+*addr)
{
- struct ieee80211_sub_if_data *sdata;
+ struct ieee80211_local *local = sdata->local;
+ struct ieee80211_sub_if_data *iter;
u64 new, mask, tmp;
u8 *m;
int ret = 0;
@@ -181,11 +182,14 @@ static int ieee80211_verify_mac(struct ieee80211_local
*local, u8 *addr)
mutex_lock(&local->iflist_mtx);
- list_for_each_entry(sdata, &local->interfaces, list) {
- if (sdata->vif.type == NL80211_IFTYPE_MONITOR)
+ list_for_each_entry(iter, &local->interfaces, list) {
+ if (iter == sdata)
+ continue;
+
+ if (iter->vif.type == NL80211_IFTYPE_MONITOR)
continue;
- m = sdata->vif.addr;
+ m = iter->vif.addr;
tmp = ((u64)m[0] << 5*8) | ((u64)m[1] << 4*8) |
((u64)m[2] << 3*8) | ((u64)m[3] << 2*8) |
((u64)m[4] << 1*8) | ((u64)m[5] << 0*8); @@ -209,7
+213,7 @@ static int ieee80211_change_mac(struct net_device *dev, void
*addr)
if (ieee80211_sdata_running(sdata))
return -EBUSY;
- ret = ieee80211_verify_mac(sdata->local, sa->sa_data);
+ ret = ieee80211_verify_mac(sdata, sa->sa_data);
if (ret)
return ret;
--
1.7.10.4
^ permalink raw reply
* RE: [RFC PATCH] net/wireless/mwifiex/pcie: Convert to dev_pm_ops from legacy pm ops
From: Bing Zhao @ 2013-05-21 18:49 UTC (permalink / raw)
To: Shuah Khan, linville@tuxdriver.com, rafael.j.wysocki@intel.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, shuahkhan@gmail.com
In-Reply-To: <1369103589.12093.4.camel@lorien>
SGkgU2h1YWgsDQoNCj4gQ29udmVydCB0aGUgZHJpdmVyIHRvIHVzZSBkZXZfcG1fb3BzIGZvciBw
b3dlciBtYW5hZ2VtZW50IGFuZCByZW1vdmUgTGVnYWN5IFBNDQo+IGhhbmRsaW5nLiBUaGlzIGNo
YW5nZSByZS11c2VzIGV4aXN0aW5nIHN1c3BlbmQgYW5kIHJlc3VtZSBpbnRlcmZhY2VzIGZvcg0K
PiBkZXZfcG1fb3BzLg0KPiANCj4gU2lnbmVkLW9mZi1ieTogU2h1YWggS2hhbiA8c2h1YWgua2hA
c2Ftc3VuZy5jb20+DQo+IENjOiBTaHVhaCBLaGFuIDxzaHVhaGtoYW5AZ21haWwuY29tPg0KPiBT
dWdnZXN0ZWQtYnk6IHJhZmFlbC5qLnd5c29ja2lAaW50ZWwuY29tDQoNCkFja2VkLWJ5OiBCaW5n
IFpoYW8gPGJ6aGFvQG1hcnZlbGwuY29tPg0KDQpUaGFua3MsDQpCaW5nDQoNCj4gLS0tDQo+IA0K
PiBSYWZhZWwsDQo+IA0KPiBUaGlzIGlzIHRoZSBmaXJzdCBkcml2ZXIgcGF0Y2ggdG8gY29udmVy
dCBkcml2ZXJzIHRvIHVzZSBkZXZfcG1fb3BzIGZvcg0KPiBwb3dlciBtYW5hZ2VtZW50LiBQbGVh
c2UgcmV2aWV3IGZvciB0aGUgYXBwcm9hY2ggYW5kIG1ha2Ugc3VnZ2VzdGlvbnMgZm9yDQo+IGlt
cHJvdmVtZW50Lg0KPiANCj4gdGhhbmtzLA0KPiAtLSBTaHVhaA0K
^ permalink raw reply
* [GIT] [3.10] NFC fixes
From: Samuel Ortiz @ 2013-05-21 23:07 UTC (permalink / raw)
To: John W. Linville; +Cc: Linux Wireless, Linux NFC
Hi John,
This is the first batch of NFC fixes for 3.10, and it contains:
- 3 fixes for the NFC MEI support:
* We now depend on the correct Kconfig symbol.
* We register an MEI event callback whenever we enable an NFC device,
otherwise we fail to read anything after an enable/disable cycle.
* We only disable an MEI device from its disable mey_phy_ops,
preventing useless consecutive disable calls.
- An NFC Makefile cleanup, as I forgot to remove a commented out line when
moving the LLCP code to the NFC top level directory.
The following changes since commit 6bb4880d9ef30375da4507aeabd6dc261a2c6c2b:
ath9k: fix draining aggregation tid buffers (2013-05-17 14:31:09 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-fixes.git tags/nfc-fixes-3.10-1
for you to fetch changes up to e3a6b14ceda0207c3405c6266e5177a85c0db044:
NFC: mei: Do not disable MEI devices from their remove routine (2013-05-21 10:48:41 +0200)
----------------------------------------------------------------
Paul Bolle (1):
NFC: Remove commented out LLCP related Makefile line
Samuel Ortiz (3):
NFC: mei_phy depends on INTEL_MEI
NFC: mei_phy: Register event callback when enabling the device
NFC: mei: Do not disable MEI devices from their remove routine
drivers/nfc/Kconfig | 2 +-
drivers/nfc/mei_phy.c | 9 +++++++++
drivers/nfc/microread/mei.c | 20 +++++---------------
drivers/nfc/pn544/mei.c | 20 +++++---------------
net/nfc/Makefile | 1 -
5 files changed, 20 insertions(+), 32 deletions(-)
--
Intel Open Source Technology Centre
http://oss.intel.com/
^ permalink raw reply
* Re: [PATCH 2/2] cfg80211/nl80211: Add coalesce support
From: Luis R. Rodriguez @ 2013-05-21 23:23 UTC (permalink / raw)
To: Bing Zhao
Cc: linux-wireless, Johannes Berg, Luis R. Rodriguez, Jouni Malinen,
Vasanthakumar Thiagarajan, Senthil Balasubramanian,
Luciano Coelho, Amitkumar Karwar
In-Reply-To: <1369099918-4921-2-git-send-email-bzhao@marvell.com>
On Mon, May 20, 2013 at 06:31:58PM -0700, Bing Zhao wrote:
> From: Amitkumar Karwar <akarwar@marvell.com>
>
> Add set/get configuration support for packet coalesce.
>
> This feature needs to be advertised during driver initialization.
> Drivers can do required hardware settings based on user configuration.
>
> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
> Signed-off-by: Bing Zhao <bzhao@marvell.com>
I see nothing documenting clearly what this "coalesce" does.
Can you elaborate quite a bit both on the commit log and also
the documentation on nl80211.h what this is exactly? It would
also be good for you to express on your previous patch why
you want the rename.
If you add this also can you please be sure to update the wiki
for iw to document support for this?
Luis
^ permalink raw reply
* RE: [PATCH 2/2] cfg80211/nl80211: Add coalesce support
From: Bing Zhao @ 2013-05-21 23:59 UTC (permalink / raw)
To: Luis R. Rodriguez
Cc: linux-wireless@vger.kernel.org, Johannes Berg, Jouni Malinen,
Vasanthakumar Thiagarajan, Senthil Balasubramanian,
Luciano Coelho, Amitkumar Karwar
In-Reply-To: <20130521232303.GX6529@pogo>
Hi Luis,
Thanks for your comments.
> > From: Amitkumar Karwar <akarwar@marvell.com>
> >
> > Add set/get configuration support for packet coalesce.
> >
> > This feature needs to be advertised during driver initialization.
> > Drivers can do required hardware settings based on user configuration.
> >
> > Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
> > Signed-off-by: Bing Zhao <bzhao@marvell.com>
>
> I see nothing documenting clearly what this "coalesce" does.
> Can you elaborate quite a bit both on the commit log and also
> the documentation on nl80211.h what this is exactly?
will add the documentations in v2.
> It would also be good for you to express on your previous patch why
> you want the rename.
"packet coalesce" will reuse the pattern structure (and its enum definitions) defined for
WoWLAN. It's renamed so that both WoWLAN and Coalesce can make use of it.
More elaborations will be added in v2 series.
>
> If you add this also can you please be sure to update the wiki
> for iw to document support for this?
Sure. It will be done as soon as the iw patches are merged.
Thanks,
Bing
>
> Luis
^ permalink raw reply
* Re: [RFC 06/12] mac80211: notify bridge when leaving mesh
From: Thomas Pedersen @ 2013-05-22 1:09 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wirelss, Bob Copeland, open80211s
In-Reply-To: <1367934155.8328.21.camel@jlt4.sipsolutions.net>
Hey, Sorry for the late response.
On Tue, May 7, 2013 at 6:42 AM, Johannes Berg <johannes@sipsolutions.net> wrote:
> On Thu, 2013-05-02 at 19:33 -0700, Thomas Pedersen wrote:
>> After turning carrier off, any parent bridge interface
>> needs to be notified. Otherwise we would see a panic when
>> attempting to transmit frames on a mesh interface which
>> hadn't yet been put down.
>>
>> Signed-off-by: Thomas Pedersen <thomas@cozybit.com>
>> ---
>> net/mac80211/mesh.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/net/mac80211/mesh.c b/net/mac80211/mesh.c
>> index eac9988..271ddc9 100644
>> --- a/net/mac80211/mesh.c
>> +++ b/net/mac80211/mesh.c
>> @@ -993,6 +993,9 @@ void ieee80211_stop_mesh(struct ieee80211_sub_if_data *sdata)
>> struct beacon_data *bcn;
>>
>> netif_carrier_off(sdata->dev);
>> + if (sdata->dev->priv_flags & IFF_BRIDGE_PORT)
>> + /* stop bridge transmissions */
>> + call_netdevice_notifiers(NETDEV_CHANGE, sdata->dev);
>
> Err, this seems like a really bad hack? I don't really think drivers
> should call that?
Why not? We're just notifying the bridge interface that this port has
gone down, to avoid dereferencing a null pointer (on bridge flood
traffic) after the mesh_bss has been removed.
Is cfg80211_leave_mesh() an acceptable location for this fix?
--
Thomas
^ permalink raw reply
* Is anyone working on voice enterprise?
From: Mark Fitzjohn @ 2013-05-22 6:24 UTC (permalink / raw)
To: linux-wireless
Hi
I couldn't see much in terms of t-spec handling in the code that we're
working with:
compat-wireless 3.6.2.1
wpa_supplicant_8
Other than on the AP side and then with a few TODOs.
So is anyone already looking at this?
Thanks
Mark
^ permalink raw reply
* Re: [PATCH] mac80211: Allow single vif mac address change with addr_mask
From: Helmut Schaa @ 2013-05-22 8:06 UTC (permalink / raw)
To: Jakub Kiciński
Cc: linux-wireless, Johannes Berg, Ivo Van Doorn,
Gertjan van Wingerde, stf_xl@wp.pl, Alessandro Lannocca,
Bruno Randolf
In-Reply-To: <20130521171018.238056b2@north>
On Tue, May 21, 2013 at 5:10 PM, Jakub Kiciński <moorray3@wp.pl> wrote:
> On Tue, 21 May 2013 14:54:53 +0200, Helmut Schaa wrote:
>> When changing the MAC address of a single vif mac80211 will check if the new
>> address fits into the address mask specified by the driver. This only needs
>> to be done when using multiple BSSIDs. Hence, check the new address only
>> against all other vifs.
>
> Oh, I see that you already posted this patch for review!
>
> I think we should also take care of the way addresses for new
> interfaces are chosen otherwise they'll just pick up
> perm_addr and we will end up with incompatible MACs.
Maybe you could send the assign_pem_addr changes as a follow up patch?
[...]
> @@ -1479,7 +1483,17 @@ static void ieee80211_assign_perm_addr(struct ieee80211_local *local,
> break;
> }
>
> + /*
> + * Pick address of existing interface in case user changed
> + * MAC address manually, default to perm_addr.
> + */
> m = local->hw.wiphy->perm_addr;
> + list_for_each_entry(sdata, &local->interfaces, list) {
> + if (sdata->vif.type == NL80211_IFTYPE_MONITOR)
> + continue;
> + m = sdata->vif.addr;
> + break;
> + }
> start = ((u64)m[0] << 5*8) | ((u64)m[1] << 4*8) |
> ((u64)m[2] << 3*8) | ((u64)m[3] << 2*8) |
> ((u64)m[4] << 1*8) | ((u64)m[5] << 0*8);
This is only relevant if the driver registered a addr_mask with mac80211.
So, maybe you could only select a new address (!=perm_addr) if the
perm_addr is not covered by the addr_mask?
Helmut
^ permalink raw reply
* Re: [PATCH 2/2] cfg80211/nl80211: Add coalesce support
From: Johannes Berg @ 2013-05-22 8:12 UTC (permalink / raw)
To: Bing Zhao
Cc: Luis R. Rodriguez, linux-wireless@vger.kernel.org, Jouni Malinen,
Vasanthakumar Thiagarajan, Senthil Balasubramanian,
Luciano Coelho, Amitkumar Karwar
In-Reply-To: <477F20668A386D41ADCC57781B1F70430E0ADCE97D@SC-VEXCH1.marvell.com>
On Tue, 2013-05-21 at 16:59 -0700, Bing Zhao wrote:
> "packet coalesce" will reuse the pattern structure (and its enum definitions) defined for
> WoWLAN. It's renamed so that both WoWLAN and Coalesce can make use of it.
Before you make any changes (I didn't get around to commenting on your
patches yesterday), I think you have to be more careful with the renames
to not break the API. Please provide defines or so to not break
compilation in the rename.
johannes
^ permalink raw reply
* Re: Problem with iwlwifi kernel 3.9.0 and 3.9.2
From: Emmanuel Grumbach @ 2013-05-22 8:17 UTC (permalink / raw)
To: Flavio; +Cc: linux-wireless
In-Reply-To: <CAP8Jb=oTE_tL+57_wtMo_QTNG01_oP2jgjicrDneFwTuOocs8g@mail.gmail.com>
On Tue, May 21, 2013 at 12:26 AM, Flavio <fbcyborg@gmail.com> wrote:
> Hello,
>
> I've recently changed my wifi router and I'm experiencing something
> really strange with my wifi connection.
> If I try to connect to my access point using windows, I don't have any
> problem, but if I try with Linux (Gentoo Linux
> x86_64) I cannot connect to my Access Point unless I do the following steps:
>
> ifconfig wlan0 down
> rmmod iwldvm
> rmmod iwlwifi
> modprobe iwlwifi
> ifconfig wlan0 up
>
> otherwise if I try to connect to my access point / wifi router, Wicd
> tells me that I inserted a wrong password.
> I've even tried with another live linux distribution, and I don't have
> this issue.
>
Please try the patch attached in
https://bugzilla.kernel.org/show_bug.cgi?id=58341
^ permalink raw reply
* Re: [v3.9.x stable regression, bisected] iwlwifi/iwldvm has a 30s delay in EAP authentication
From: Emmanuel Grumbach @ 2013-05-22 8:17 UTC (permalink / raw)
To: kkhere.geo+suse; +Cc: linux-kernel@vger.kernel.org, linux-wireless, gregkh
In-Reply-To: <519B8021.6030002@gmail.com>
On Tue, May 21, 2013 at 5:09 PM, Kshitij Kulshreshtha
<kkhere.geo@gmail.com> wrote:
> Hello,
>
> I am currently running the openSUSE Tumbleweed distribution and have a
> problem starting with the kernel v3.9.1 and also with kernel v3.9.2.
>
> The iwldvm driver has an artificial delay of 30s when authenticating
> with a radius server using EAP-TLS. This was not the case using kernel
> v3.9.
>
> I bisected the problem using local builds of the tumbleweed desktop
> configuration. This is the result:
>
> c30f37f8f1f8d06c142d67ba74955fd48b5cf5a4 is the first bad commit
> commit c30f37f8f1f8d06c142d67ba74955fd48b5cf5a4
> Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
> Date: Wed Apr 17 09:47:00 2013 +0300
>
> iwlwifi: dvm: don't send zeroed LQ cmd
>
> commit 63b77bf489881747c5118476918cc8c29378ee63 upstream.
>
> When the stations are being restored because of unassoc
> RXON, the LQ cmd may not have been initialized because it
> is initialized only after association.
> Sending zeroed LQ_CMD makes the fw unhappy: it raises
> SYSASSERT_2078.
>
> Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
> Reviewed-by: Johannes Berg <johannes.berg@intel.com>
> [move zero_lq and make static const]
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
Thanks for the bisection.
Can you please try the patch in
https://bugzilla.kernel.org/show_bug.cgi?id=58341 and report?
Thanks
^ permalink raw reply
* iwlwifi: "fail to flush all tx fifo queues" and dies
From: Jiri Slaby @ 2013-05-22 8:26 UTC (permalink / raw)
To: Johannes Berg
Cc: Wey-Yi Guy, Intel Linux Wireless, linux-wireless@vger.kernel.org,
Linux kernel mailing list
Hi,
I'm seeing $SUBJ from iwlwifi and then it stops working (ping has high
RTT etc.) with this device:
03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N
6205 [Taylor Peak] [8086:0085] (rev 34)
Subsystem: Intel Corporation Centrino Advanced-N 6205 AGN
[8086:1311]
Flags: bus master, fast devsel, latency 0, IRQ 47
Memory at f1c00000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 60-67-20-ff-ff-81-4a-dc
Kernel driver in use: iwlwifi
When I disable 802.11n, it's gone:
modprobe iwlwifi 11n_disable=1
This is all with 3.9.3 kernel.
Dmesg output:
[90008.127440] cfg80211: Calling CRDA to update world regulatory domain
[90008.139827] cfg80211: World regulatory domain updated:
[90008.139832] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[90008.139836] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90008.139839] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[90008.139841] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[90008.139844] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90008.139846] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90011.557669] wlan0: authenticate with 14:d6:4d:cd:4b:2e
[90011.560161] wlan0: send auth to 14:d6:4d:cd:4b:2e (try 1/3)
[90011.575100] wlan0: authenticated
[90011.575543] wlan0: associate with 14:d6:4d:cd:4b:2e (try 1/3)
[90011.592192] wlan0: RX AssocResp from 14:d6:4d:cd:4b:2e (capab=0xc11
status=0 aid=1)
[90011.600809] wlan0: associated
[90011.600968] cfg80211: Calling CRDA for country: GB
[90011.605228] cfg80211: Regulatory domain changed to country: GB
[90011.605233] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[90011.605237] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90011.605239] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90011.605242] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90011.605244] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz),
(N/A, 2700 mBm)
[90392.229463] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues Q 11
[90392.229472] iwlwifi 0000:03:00.0: Current SW read_ptr 110 write_ptr 247
[90392.229524] iwl data: 00000000: ff ff 3f 00 7f 00 00 00 00 80 ff ff
00 00 ff ff ..?.............
[90392.229561] iwlwifi 0000:03:00.0: FH TRBs(0) = 0x00000000
[90392.229597] iwlwifi 0000:03:00.0: FH TRBs(1) = 0xc010b095
[90392.229633] iwlwifi 0000:03:00.0: FH TRBs(2) = 0x00000000
[90392.229670] iwlwifi 0000:03:00.0: FH TRBs(3) = 0x80300045
[90392.229691] iwlwifi 0000:03:00.0: FH TRBs(4) = 0x00000000
[90392.229712] iwlwifi 0000:03:00.0: FH TRBs(5) = 0x00000000
[90392.229732] iwlwifi 0000:03:00.0: FH TRBs(6) = 0x00000000
[90392.229753] iwlwifi 0000:03:00.0: FH TRBs(7) = 0x00709048
[90392.229832] iwlwifi 0000:03:00.0: Q 0 is active and mapped to fifo 3
ra_tid 0x0000 [70,70]
[90392.229909] iwlwifi 0000:03:00.0: Q 1 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[90392.229987] iwlwifi 0000:03:00.0: Q 2 is active and mapped to fifo 1
ra_tid 0x0000 [249,249]
[90392.230065] iwlwifi 0000:03:00.0: Q 3 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[90392.230149] iwlwifi 0000:03:00.0: Q 4 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[90392.230227] iwlwifi 0000:03:00.0: Q 5 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[90392.230305] iwlwifi 0000:03:00.0: Q 6 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[90392.230388] iwlwifi 0000:03:00.0: Q 7 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[90392.230521] iwlwifi 0000:03:00.0: Q 8 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[90392.230671] iwlwifi 0000:03:00.0: Q 9 is active and mapped to fifo 7
ra_tid 0x0000 [73,73]
[90392.230750] iwlwifi 0000:03:00.0: Q 10 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[90392.230827] iwlwifi 0000:03:00.0: Q 11 is active and mapped to fifo 1
ra_tid 0x0000 [111,247]
[90392.230977] iwlwifi 0000:03:00.0: Q 12 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90392.231063] iwlwifi 0000:03:00.0: Q 13 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90392.231144] iwlwifi 0000:03:00.0: Q 14 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90392.231274] iwlwifi 0000:03:00.0: Q 15 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90392.231360] iwlwifi 0000:03:00.0: Q 16 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90392.231473] iwlwifi 0000:03:00.0: Q 17 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90392.231558] iwlwifi 0000:03:00.0: Q 18 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90392.231644] iwlwifi 0000:03:00.0: Q 19 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90453.413842] cfg80211: Calling CRDA to update world regulatory domain
[90453.437671] cfg80211: World regulatory domain updated:
[90453.437677] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[90453.437681] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90453.437684] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[90453.437686] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[90453.437689] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90453.437691] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90456.774117] wlan0: authenticate with 14:d6:4d:cd:4b:2e
[90456.776360] wlan0: send auth to 14:d6:4d:cd:4b:2e (try 1/3)
[90456.806109] wlan0: authenticated
[90456.807005] wlan0: associate with 14:d6:4d:cd:4b:2e (try 1/3)
[90456.811076] wlan0: RX AssocResp from 14:d6:4d:cd:4b:2e (capab=0xc11
status=0 aid=1)
[90456.822785] wlan0: associated
[90456.822926] cfg80211: Calling CRDA for country: GB
[90456.827857] cfg80211: Regulatory domain changed to country: GB
[90456.827863] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[90456.827866] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90456.827869] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90456.827871] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90456.827873] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz),
(N/A, 2700 mBm)
[90512.524765] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues Q 11
[90512.524773] iwlwifi 0000:03:00.0: Current SW read_ptr 152 write_ptr 197
[90512.524832] iwl data: 00000000: 00 00 00 ff 00 00 00 06 ff 1f 00 00
70 00 00 00 ............p...
[90512.524869] iwlwifi 0000:03:00.0: FH TRBs(0) = 0x00000000
[90512.524905] iwlwifi 0000:03:00.0: FH TRBs(1) = 0xc010b0ac
[90512.524926] iwlwifi 0000:03:00.0: FH TRBs(2) = 0x00000000
[90512.524962] iwlwifi 0000:03:00.0: FH TRBs(3) = 0x8030004f
[90512.524983] iwlwifi 0000:03:00.0: FH TRBs(4) = 0x00000000
[90512.525019] iwlwifi 0000:03:00.0: FH TRBs(5) = 0x00000000
[90512.525039] iwlwifi 0000:03:00.0: FH TRBs(6) = 0x00000000
[90512.525077] iwlwifi 0000:03:00.0: FH TRBs(7) = 0x007090ee
[90512.525155] iwlwifi 0000:03:00.0: Q 0 is active and mapped to fifo 3
ra_tid 0x0000 [80,80]
[90512.525238] iwlwifi 0000:03:00.0: Q 1 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[90512.525316] iwlwifi 0000:03:00.0: Q 2 is active and mapped to fifo 1
ra_tid 0x0000 [111,111]
[90512.525394] iwlwifi 0000:03:00.0: Q 3 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[90512.525477] iwlwifi 0000:03:00.0: Q 4 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[90512.525554] iwlwifi 0000:03:00.0: Q 5 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[90512.525632] iwlwifi 0000:03:00.0: Q 6 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[90512.525758] iwlwifi 0000:03:00.0: Q 7 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[90512.525858] iwlwifi 0000:03:00.0: Q 8 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[90512.525940] iwlwifi 0000:03:00.0: Q 9 is active and mapped to fifo 7
ra_tid 0x0000 [239,239]
[90512.526026] iwlwifi 0000:03:00.0: Q 10 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[90512.526159] iwlwifi 0000:03:00.0: Q 11 is active and mapped to fifo 1
ra_tid 0x0000 [152,197]
[90512.526244] iwlwifi 0000:03:00.0: Q 12 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90512.526333] iwlwifi 0000:03:00.0: Q 13 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90512.526479] iwlwifi 0000:03:00.0: Q 14 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90512.526613] iwlwifi 0000:03:00.0: Q 15 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90512.526705] iwlwifi 0000:03:00.0: Q 16 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90512.526788] iwlwifi 0000:03:00.0: Q 17 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90512.526874] iwlwifi 0000:03:00.0: Q 18 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90512.526960] iwlwifi 0000:03:00.0: Q 19 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[90594.515989] cfg80211: Calling CRDA to update world regulatory domain
[90594.519436] cfg80211: World regulatory domain updated:
[90594.519441] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[90594.519445] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90594.519448] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[90594.519450] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[90594.519453] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90594.519455] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90597.872693] wlan0: authenticate with 14:d6:4d:cd:4b:2e
[90597.875212] wlan0: send auth to 14:d6:4d:cd:4b:2e (try 1/3)
[90597.904896] wlan0: authenticated
[90597.905995] wlan0: associate with 14:d6:4d:cd:4b:2e (try 1/3)
[90597.910076] wlan0: RX AssocResp from 14:d6:4d:cd:4b:2e (capab=0xc11
status=0 aid=1)
[90597.921771] wlan0: associated
[90597.921927] cfg80211: Calling CRDA for country: GB
[90597.926595] cfg80211: Regulatory domain changed to country: GB
[90597.926601] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[90597.926604] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90597.926607] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90597.926609] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90597.926612] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz),
(N/A, 2700 mBm)
[90609.517742] cfg80211: Calling CRDA to update world regulatory domain
[90609.521309] cfg80211: World regulatory domain updated:
[90609.521315] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[90609.521318] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90609.521321] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[90609.521324] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[90609.521326] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90609.521329] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90612.899852] wlan0: authenticate with 14:d6:4d:cd:4b:2e
[90612.901797] wlan0: send auth to 14:d6:4d:cd:4b:2e (try 1/3)
[90612.920586] wlan0: send auth to 14:d6:4d:cd:4b:2e (try 2/3)
[90613.049972] wlan0: send auth to 14:d6:4d:cd:4b:2e (try 3/3)
[90613.076487] wlan0: authentication with 14:d6:4d:cd:4b:2e timed out
[90624.697553] wlan0: authenticate with 14:d6:4d:cd:4b:2e
[90624.700463] wlan0: send auth to 14:d6:4d:cd:4b:2e (try 1/3)
[90624.702980] wlan0: authenticated
[90624.703661] wlan0: associate with 14:d6:4d:cd:4b:2e (try 1/3)
[90624.707630] wlan0: RX AssocResp from 14:d6:4d:cd:4b:2e (capab=0xc11
status=0 aid=1)
[90624.717199] wlan0: associated
[90624.717348] cfg80211: Calling CRDA for country: GB
[90624.721716] cfg80211: Regulatory domain changed to country: GB
[90624.721722] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[90624.721725] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90624.721728] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90624.721730] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90624.721732] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz),
(N/A, 2700 mBm)
[90850.680850] cfg80211: Calling CRDA to update world regulatory domain
[90850.684666] cfg80211: World regulatory domain updated:
[90850.684673] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[90850.684678] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90850.684682] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[90850.684685] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[90850.684689] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90850.684693] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[90862.212040] wlan0: authenticate with 14:d6:4d:cd:4b:2e
[90862.214551] wlan0: send auth to 14:d6:4d:cd:4b:2e (try 1/3)
[90862.229579] wlan0: authenticated
[90862.230261] wlan0: associate with 14:d6:4d:cd:4b:2e (try 1/3)
[90862.235878] wlan0: RX AssocResp from 14:d6:4d:cd:4b:2e (capab=0xc11
status=0 aid=1)
[90862.246734] wlan0: associated
[90862.246840] cfg80211: Calling CRDA for country: GB
[90862.250583] cfg80211: Regulatory domain changed to country: GB
[90862.250588] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[90862.250591] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90862.250594] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90862.250596] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[90862.250598] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz),
(N/A, 2700 mBm)
[91591.588372] cfg80211: Calling CRDA to update world regulatory domain
[91591.593238] cfg80211: World regulatory domain updated:
[91591.593244] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[91591.593248] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[91591.593251] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[91591.593253] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[91591.593256] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[91591.593258] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[91594.981072] wlan0: authenticate with 14:d6:4d:cd:4b:2e
[91594.982153] wlan0: send auth to 14:d6:4d:cd:4b:2e (try 1/3)
[91595.012490] wlan0: authenticated
[91595.013275] wlan0: associate with 14:d6:4d:cd:4b:2e (try 1/3)
[91595.017262] wlan0: RX AssocResp from 14:d6:4d:cd:4b:2e (capab=0xc11
status=0 aid=1)
[91595.022920] wlan0: associated
[91595.023009] cfg80211: Calling CRDA for country: GB
[91595.026693] cfg80211: Regulatory domain changed to country: GB
[91595.026699] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[91595.026702] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[91595.026705] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[91595.026707] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[91595.026709] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz),
(N/A, 2700 mBm)
[92038.663037] cfg80211: Calling CRDA to update world regulatory domain
[92038.667064] cfg80211: World regulatory domain updated:
[92038.667069] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[92038.667072] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[92038.667075] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[92038.667078] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[92038.667080] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[92038.667083] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[92042.045356] wlan0: authenticate with 14:d6:4d:cd:4b:2e
[92042.047968] wlan0: send auth to 14:d6:4d:cd:4b:2e (try 1/3)
[92042.063278] wlan0: authenticated
[92042.064013] wlan0: associate with 14:d6:4d:cd:4b:2e (try 1/3)
[92042.068090] wlan0: RX AssocResp from 14:d6:4d:cd:4b:2e (capab=0xc11
status=0 aid=1)
[92042.080991] wlan0: associated
[92042.081147] cfg80211: Calling CRDA for country: GB
[92042.085524] cfg80211: Regulatory domain changed to country: GB
[92042.085529] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[92042.085532] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[92042.085535] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[92042.085537] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[92042.085539] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz),
(N/A, 2700 mBm)
[92146.538148] cfg80211: Calling CRDA to update world regulatory domain
[92146.542591] cfg80211: World regulatory domain updated:
[92146.542597] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[92146.542600] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[92146.542603] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[92146.542606] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[92146.542608] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[92146.542610] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[92149.923675] wlan0: authenticate with 14:d6:4d:cd:4b:2e
[92149.925907] wlan0: send auth to 14:d6:4d:cd:4b:2e (try 1/3)
[92149.943355] wlan0: authenticated
[92149.944073] wlan0: associate with 14:d6:4d:cd:4b:2e (try 1/3)
[92149.948101] wlan0: RX AssocResp from 14:d6:4d:cd:4b:2e (capab=0xc11
status=0 aid=1)
[92149.953587] wlan0: associated
[92149.953698] cfg80211: Calling CRDA for country: GB
[92149.957582] cfg80211: Regulatory domain changed to country: GB
[92149.957586] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[92149.957589] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[92149.957591] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[92149.957594] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[92149.957596] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz),
(N/A, 2700 mBm)
[92314.007270] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues Q 11
[92314.007280] iwlwifi 0000:03:00.0: Current SW read_ptr 141 write_ptr 169
[92314.007331] iwl data: 00000000: 00 e0 ff ff 00 00 e0 3f 7f 00 00 00
20 00 00 00 .......?.... ...
[92314.007374] iwlwifi 0000:03:00.0: FH TRBs(0) = 0x00000000
[92314.007410] iwlwifi 0000:03:00.0: FH TRBs(1) = 0xc010b0a6
[92314.007446] iwlwifi 0000:03:00.0: FH TRBs(2) = 0x00000000
[92314.007484] iwlwifi 0000:03:00.0: FH TRBs(3) = 0x803000a3
[92314.007520] iwlwifi 0000:03:00.0: FH TRBs(4) = 0x00000000
[92314.007556] iwlwifi 0000:03:00.0: FH TRBs(5) = 0x00000000
[92314.007593] iwlwifi 0000:03:00.0: FH TRBs(6) = 0x00000000
[92314.007629] iwlwifi 0000:03:00.0: FH TRBs(7) = 0x007090ac
[92314.007709] iwlwifi 0000:03:00.0: Q 0 is active and mapped to fifo 3
ra_tid 0x0000 [164,164]
[92314.007787] iwlwifi 0000:03:00.0: Q 1 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[92314.007865] iwlwifi 0000:03:00.0: Q 2 is active and mapped to fifo 1
ra_tid 0x0000 [88,89]
[92314.007942] iwlwifi 0000:03:00.0: Q 3 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[92314.008026] iwlwifi 0000:03:00.0: Q 4 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[92314.008104] iwlwifi 0000:03:00.0: Q 5 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[92314.008181] iwlwifi 0000:03:00.0: Q 6 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[92314.008305] iwlwifi 0000:03:00.0: Q 7 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[92314.008393] iwlwifi 0000:03:00.0: Q 8 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[92314.008474] iwlwifi 0000:03:00.0: Q 9 is active and mapped to fifo 7
ra_tid 0x0000 [173,173]
[92314.008554] iwlwifi 0000:03:00.0: Q 10 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[92314.008638] iwlwifi 0000:03:00.0: Q 11 is active and mapped to fifo 1
ra_tid 0x0000 [141,169]
[92314.008717] iwlwifi 0000:03:00.0: Q 12 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92314.008804] iwlwifi 0000:03:00.0: Q 13 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92314.008891] iwlwifi 0000:03:00.0: Q 14 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92314.008977] iwlwifi 0000:03:00.0: Q 15 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92314.009061] iwlwifi 0000:03:00.0: Q 16 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92314.009150] iwlwifi 0000:03:00.0: Q 17 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92314.009276] iwlwifi 0000:03:00.0: Q 18 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92314.009355] iwlwifi 0000:03:00.0: Q 19 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92552.018285] cfg80211: Calling CRDA to update world regulatory domain
[92552.022175] cfg80211: World regulatory domain updated:
[92552.022181] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[92552.022184] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[92552.022187] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[92552.022190] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[92552.022192] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[92552.022194] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[92555.425322] wlan0: authenticate with 14:d6:4d:cd:4b:2e
[92555.426590] wlan0: send auth to 14:d6:4d:cd:4b:2e (try 1/3)
[92555.444113] wlan0: authenticated
[92555.445369] wlan0: associate with 14:d6:4d:cd:4b:2e (try 1/3)
[92555.449251] wlan0: RX AssocResp from 14:d6:4d:cd:4b:2e (capab=0xc11
status=0 aid=1)
[92555.457598] wlan0: associated
[92555.457689] cfg80211: Calling CRDA for country: GB
[92555.461527] cfg80211: Regulatory domain changed to country: GB
[92555.461533] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[92555.461536] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[92555.461539] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[92555.461541] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[92555.461543] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz),
(N/A, 2700 mBm)
[92915.901967] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues Q 11
[92915.901975] iwlwifi 0000:03:00.0: Current SW read_ptr 80 write_ptr 175
[92915.902026] iwl data: 00000000: 00 00 ff ff 00 00 fe 7f ff 3f 00 00
00 00 00 00 .........?......
[92915.902062] iwlwifi 0000:03:00.0: FH TRBs(0) = 0x00000000
[92915.902098] iwlwifi 0000:03:00.0: FH TRBs(1) = 0xc010b06d
[92915.902134] iwlwifi 0000:03:00.0: FH TRBs(2) = 0x00000000
[92915.902155] iwlwifi 0000:03:00.0: FH TRBs(3) = 0x803000b1
[92915.902191] iwlwifi 0000:03:00.0: FH TRBs(4) = 0x00000000
[92915.902228] iwlwifi 0000:03:00.0: FH TRBs(5) = 0x00000000
[92915.902248] iwlwifi 0000:03:00.0: FH TRBs(6) = 0x00000000
[92915.902269] iwlwifi 0000:03:00.0: FH TRBs(7) = 0x0070902c
[92915.902354] iwlwifi 0000:03:00.0: Q 0 is active and mapped to fifo 3
ra_tid 0x0000 [178,178]
[92915.902430] iwlwifi 0000:03:00.0: Q 1 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[92915.902508] iwlwifi 0000:03:00.0: Q 2 is active and mapped to fifo 1
ra_tid 0x0000 [202,202]
[92915.902592] iwlwifi 0000:03:00.0: Q 3 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[92915.902679] iwlwifi 0000:03:00.0: Q 4 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[92915.902757] iwlwifi 0000:03:00.0: Q 5 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[92915.902840] iwlwifi 0000:03:00.0: Q 6 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[92915.902918] iwlwifi 0000:03:00.0: Q 7 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[92915.903045] iwlwifi 0000:03:00.0: Q 8 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[92915.903128] iwlwifi 0000:03:00.0: Q 9 is active and mapped to fifo 7
ra_tid 0x0000 [45,45]
[92915.903212] iwlwifi 0000:03:00.0: Q 10 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[92915.903290] iwlwifi 0000:03:00.0: Q 11 is active and mapped to fifo 1
ra_tid 0x0000 [80,175]
[92915.903367] iwlwifi 0000:03:00.0: Q 12 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92915.903428] iwlwifi 0000:03:00.0: Q 13 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92915.903496] iwlwifi 0000:03:00.0: Q 14 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92915.903557] iwlwifi 0000:03:00.0: Q 15 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92915.903627] iwlwifi 0000:03:00.0: Q 16 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92915.903703] iwlwifi 0000:03:00.0: Q 17 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92915.903765] iwlwifi 0000:03:00.0: Q 18 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92915.903826] iwlwifi 0000:03:00.0: Q 19 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[92983.267661] cfg80211: Calling CRDA to update world regulatory domain
[92983.272243] cfg80211: World regulatory domain updated:
[92983.272248] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[92983.272252] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[92983.272255] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[92983.272257] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[92983.272260] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[92983.272262] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[92986.643194] wlan0: authenticate with 14:d6:4d:cd:4b:2e
[92986.645444] wlan0: send auth to 14:d6:4d:cd:4b:2e (try 1/3)
[92986.662913] wlan0: authenticated
[92986.663630] wlan0: associate with 14:d6:4d:cd:4b:2e (try 1/3)
[92986.667538] wlan0: RX AssocResp from 14:d6:4d:cd:4b:2e (capab=0xc11
status=0 aid=1)
[92986.683920] wlan0: associated
[92986.684009] cfg80211: Calling CRDA for country: GB
[92986.687250] cfg80211: Regulatory domain changed to country: GB
[92986.687255] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[92986.687258] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[92986.687260] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[92986.687262] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[92986.687264] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz),
(N/A, 2700 mBm)
[93027.091295] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues Q 2
[93027.091303] iwlwifi 0000:03:00.0: Current SW read_ptr 115 write_ptr 169
[93027.091368] iwl data: 00000000: 07 00 00 00 00 00 00 00 00 00 f8 ff
00 00 00 00 ................
[93027.091404] iwlwifi 0000:03:00.0: FH TRBs(0) = 0x00000000
[93027.091440] iwlwifi 0000:03:00.0: FH TRBs(1) = 0x80102082
[93027.091467] iwlwifi 0000:03:00.0: FH TRBs(2) = 0x00000000
[93027.091488] iwlwifi 0000:03:00.0: FH TRBs(3) = 0x803000bb
[93027.091524] iwlwifi 0000:03:00.0: FH TRBs(4) = 0x00000000
[93027.091545] iwlwifi 0000:03:00.0: FH TRBs(5) = 0x00000000
[93027.091578] iwlwifi 0000:03:00.0: FH TRBs(6) = 0x00000000
[93027.091615] iwlwifi 0000:03:00.0: FH TRBs(7) = 0x0070908c
[93027.091685] iwlwifi 0000:03:00.0: Q 0 is active and mapped to fifo 3
ra_tid 0x0000 [188,188]
[93027.091762] iwlwifi 0000:03:00.0: Q 1 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[93027.091853] iwlwifi 0000:03:00.0: Q 2 is active and mapped to fifo 1
ra_tid 0x0000 [115,169]
[93027.091937] iwlwifi 0000:03:00.0: Q 3 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[93027.092021] iwlwifi 0000:03:00.0: Q 4 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[93027.092099] iwlwifi 0000:03:00.0: Q 5 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[93027.092183] iwlwifi 0000:03:00.0: Q 6 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[93027.092310] iwlwifi 0000:03:00.0: Q 7 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[93027.092398] iwlwifi 0000:03:00.0: Q 8 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[93027.092475] iwlwifi 0000:03:00.0: Q 9 is active and mapped to fifo 7
ra_tid 0x0000 [141,141]
[93027.092554] iwlwifi 0000:03:00.0: Q 10 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[93027.092637] iwlwifi 0000:03:00.0: Q 11 is inactive and mapped to fifo
1 ra_tid 0x0000 [198,198]
[93027.092698] iwlwifi 0000:03:00.0: Q 12 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93027.092765] iwlwifi 0000:03:00.0: Q 13 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93027.092915] iwlwifi 0000:03:00.0: Q 14 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93027.092977] iwlwifi 0000:03:00.0: Q 15 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93027.093033] iwlwifi 0000:03:00.0: Q 16 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93027.093097] iwlwifi 0000:03:00.0: Q 17 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93027.093183] iwlwifi 0000:03:00.0: Q 18 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93027.093295] iwlwifi 0000:03:00.0: Q 19 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93155.163708] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues Q 2
[93155.163717] iwlwifi 0000:03:00.0: Current SW read_ptr 244 write_ptr 250
[93155.163776] iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 30 00
00 00 00 00 ..........0.....
[93155.163818] iwlwifi 0000:03:00.0: FH TRBs(0) = 0x00000000
[93155.163856] iwlwifi 0000:03:00.0: FH TRBs(1) = 0xc010b01d
[93155.163901] iwlwifi 0000:03:00.0: FH TRBs(2) = 0x00000000
[93155.163946] iwlwifi 0000:03:00.0: FH TRBs(3) = 0x803000c3
[93155.163982] iwlwifi 0000:03:00.0: FH TRBs(4) = 0x00000000
[93155.164025] iwlwifi 0000:03:00.0: FH TRBs(5) = 0x00000000
[93155.164045] iwlwifi 0000:03:00.0: FH TRBs(6) = 0x00000000
[93155.164066] iwlwifi 0000:03:00.0: FH TRBs(7) = 0x0070905a
[93155.164151] iwlwifi 0000:03:00.0: Q 0 is active and mapped to fifo 3
ra_tid 0x0000 [196,196]
[93155.164228] iwlwifi 0000:03:00.0: Q 1 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[93155.164312] iwlwifi 0000:03:00.0: Q 2 is active and mapped to fifo 1
ra_tid 0x0000 [244,250]
[93155.164397] iwlwifi 0000:03:00.0: Q 3 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[93155.164474] iwlwifi 0000:03:00.0: Q 4 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[93155.164558] iwlwifi 0000:03:00.0: Q 5 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[93155.164636] iwlwifi 0000:03:00.0: Q 6 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[93155.164759] iwlwifi 0000:03:00.0: Q 7 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[93155.164845] iwlwifi 0000:03:00.0: Q 8 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[93155.164935] iwlwifi 0000:03:00.0: Q 9 is active and mapped to fifo 7
ra_tid 0x0000 [91,91]
[93155.165013] iwlwifi 0000:03:00.0: Q 10 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[93155.165091] iwlwifi 0000:03:00.0: Q 11 is active and mapped to fifo 1
ra_tid 0x0000 [16,49]
[93155.165175] iwlwifi 0000:03:00.0: Q 12 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93155.165253] iwlwifi 0000:03:00.0: Q 13 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93155.165321] iwlwifi 0000:03:00.0: Q 14 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93155.165382] iwlwifi 0000:03:00.0: Q 15 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93155.165443] iwlwifi 0000:03:00.0: Q 16 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93155.165526] iwlwifi 0000:03:00.0: Q 17 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93155.165588] iwlwifi 0000:03:00.0: Q 18 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93155.165650] iwlwifi 0000:03:00.0: Q 19 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93501.405979] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues Q 11
[93501.405988] iwlwifi 0000:03:00.0: Current SW read_ptr 204 write_ptr 208
[93501.406044] iwl data: 00000000: 00 f0 00 00 00 00 00 00 00 00 00 00
00 00 00 00 ................
[93501.406081] iwlwifi 0000:03:00.0: FH TRBs(0) = 0x00000000
[93501.406118] iwlwifi 0000:03:00.0: FH TRBs(1) = 0xc010b0cf
[93501.406154] iwlwifi 0000:03:00.0: FH TRBs(2) = 0x00000000
[93501.406191] iwlwifi 0000:03:00.0: FH TRBs(3) = 0x803000db
[93501.406227] iwlwifi 0000:03:00.0: FH TRBs(4) = 0x00000000
[93501.406263] iwlwifi 0000:03:00.0: FH TRBs(5) = 0x00000000
[93501.406300] iwlwifi 0000:03:00.0: FH TRBs(6) = 0x00000000
[93501.406337] iwlwifi 0000:03:00.0: FH TRBs(7) = 0x00709023
[93501.406416] iwlwifi 0000:03:00.0: Q 0 is active and mapped to fifo 3
ra_tid 0x0000 [220,220]
[93501.406493] iwlwifi 0000:03:00.0: Q 1 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[93501.406576] iwlwifi 0000:03:00.0: Q 2 is active and mapped to fifo 1
ra_tid 0x0000 [243,243]
[93501.406659] iwlwifi 0000:03:00.0: Q 3 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[93501.406749] iwlwifi 0000:03:00.0: Q 4 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[93501.406827] iwlwifi 0000:03:00.0: Q 5 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[93501.406940] iwlwifi 0000:03:00.0: Q 6 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[93501.407034] iwlwifi 0000:03:00.0: Q 7 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[93501.407118] iwlwifi 0000:03:00.0: Q 8 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[93501.407206] iwlwifi 0000:03:00.0: Q 9 is active and mapped to fifo 7
ra_tid 0x0000 [36,36]
[93501.407287] iwlwifi 0000:03:00.0: Q 10 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[93501.407371] iwlwifi 0000:03:00.0: Q 11 is active and mapped to fifo 1
ra_tid 0x0000 [204,208]
[93501.407454] iwlwifi 0000:03:00.0: Q 12 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93501.407545] iwlwifi 0000:03:00.0: Q 13 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93501.407625] iwlwifi 0000:03:00.0: Q 14 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93501.407710] iwlwifi 0000:03:00.0: Q 15 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93501.407796] iwlwifi 0000:03:00.0: Q 16 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93501.407877] iwlwifi 0000:03:00.0: Q 17 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93501.407991] iwlwifi 0000:03:00.0: Q 18 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93501.408074] iwlwifi 0000:03:00.0: Q 19 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93503.411241] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues Q 11
[93503.411248] iwlwifi 0000:03:00.0: Current SW read_ptr 206 write_ptr 213
[93503.411298] iwl data: 00000000: 00 c0 1f 00 00 00 00 00 00 00 00 00
00 00 00 00 ................
[93503.411335] iwlwifi 0000:03:00.0: FH TRBs(0) = 0x00000000
[93503.411372] iwlwifi 0000:03:00.0: FH TRBs(1) = 0x801020f4
[93503.411408] iwlwifi 0000:03:00.0: FH TRBs(2) = 0x00000000
[93503.411445] iwlwifi 0000:03:00.0: FH TRBs(3) = 0x803000dc
[93503.411484] iwlwifi 0000:03:00.0: FH TRBs(4) = 0x00000000
[93503.411522] iwlwifi 0000:03:00.0: FH TRBs(5) = 0x00000000
[93503.411560] iwlwifi 0000:03:00.0: FH TRBs(6) = 0x00000000
[93503.411599] iwlwifi 0000:03:00.0: FH TRBs(7) = 0x00709024
[93503.411681] iwlwifi 0000:03:00.0: Q 0 is active and mapped to fifo 3
ra_tid 0x0000 [221,221]
[93503.411766] iwlwifi 0000:03:00.0: Q 1 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[93503.411858] iwlwifi 0000:03:00.0: Q 2 is active and mapped to fifo 1
ra_tid 0x0000 [243,245]
[93503.411939] iwlwifi 0000:03:00.0: Q 3 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[93503.412032] iwlwifi 0000:03:00.0: Q 4 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[93503.412109] iwlwifi 0000:03:00.0: Q 5 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[93503.412187] iwlwifi 0000:03:00.0: Q 6 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[93503.412311] iwlwifi 0000:03:00.0: Q 7 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[93503.412390] iwlwifi 0000:03:00.0: Q 8 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[93503.412468] iwlwifi 0000:03:00.0: Q 9 is active and mapped to fifo 7
ra_tid 0x0000 [37,37]
[93503.412546] iwlwifi 0000:03:00.0: Q 10 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[93503.412613] iwlwifi 0000:03:00.0: Q 11 is active and mapped to fifo 1
ra_tid 0x0000 [206,213]
[93503.412675] iwlwifi 0000:03:00.0: Q 12 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93503.412753] iwlwifi 0000:03:00.0: Q 13 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93503.412836] iwlwifi 0000:03:00.0: Q 14 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93503.412900] iwlwifi 0000:03:00.0: Q 15 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93503.412985] iwlwifi 0000:03:00.0: Q 16 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93503.413121] iwlwifi 0000:03:00.0: Q 17 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93503.413198] iwlwifi 0000:03:00.0: Q 18 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93503.413287] iwlwifi 0000:03:00.0: Q 19 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93506.405217] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues Q 2
[93506.405225] iwlwifi 0000:03:00.0: Current SW read_ptr 244 write_ptr 245
[93506.405275] iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 10 00
00 00 00 00 ................
[93506.405311] iwlwifi 0000:03:00.0: FH TRBs(0) = 0x00000000
[93506.405347] iwlwifi 0000:03:00.0: FH TRBs(1) = 0xc010b0d9
[93506.405383] iwlwifi 0000:03:00.0: FH TRBs(2) = 0x00000000
[93506.405420] iwlwifi 0000:03:00.0: FH TRBs(3) = 0x803000dd
[93506.405456] iwlwifi 0000:03:00.0: FH TRBs(4) = 0x00000000
[93506.405493] iwlwifi 0000:03:00.0: FH TRBs(5) = 0x00000000
[93506.405529] iwlwifi 0000:03:00.0: FH TRBs(6) = 0x00000000
[93506.405566] iwlwifi 0000:03:00.0: FH TRBs(7) = 0x00709029
[93506.405652] iwlwifi 0000:03:00.0: Q 0 is active and mapped to fifo 3
ra_tid 0x0000 [222,222]
[93506.405729] iwlwifi 0000:03:00.0: Q 1 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[93506.405813] iwlwifi 0000:03:00.0: Q 2 is active and mapped to fifo 1
ra_tid 0x0000 [244,245]
[93506.405891] iwlwifi 0000:03:00.0: Q 3 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[93506.405983] iwlwifi 0000:03:00.0: Q 4 is active and mapped to fifo 0
ra_tid 0x0000 [0,0]
[93506.406062] iwlwifi 0000:03:00.0: Q 5 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[93506.406140] iwlwifi 0000:03:00.0: Q 6 is active and mapped to fifo 2
ra_tid 0x0000 [0,0]
[93506.406259] iwlwifi 0000:03:00.0: Q 7 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[93506.406350] iwlwifi 0000:03:00.0: Q 8 is active and mapped to fifo 4
ra_tid 0x0000 [0,0]
[93506.406438] iwlwifi 0000:03:00.0: Q 9 is active and mapped to fifo 7
ra_tid 0x0000 [42,42]
[93506.406544] iwlwifi 0000:03:00.0: Q 10 is active and mapped to fifo 5
ra_tid 0x0000 [0,0]
[93506.406629] iwlwifi 0000:03:00.0: Q 11 is active and mapped to fifo 1
ra_tid 0x0000 [206,218]
[93506.406711] iwlwifi 0000:03:00.0: Q 12 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93506.406795] iwlwifi 0000:03:00.0: Q 13 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93506.406899] iwlwifi 0000:03:00.0: Q 14 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93506.407038] iwlwifi 0000:03:00.0: Q 15 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93506.407117] iwlwifi 0000:03:00.0: Q 16 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93506.407220] iwlwifi 0000:03:00.0: Q 17 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93506.407320] iwlwifi 0000:03:00.0: Q 18 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
[93506.407409] iwlwifi 0000:03:00.0: Q 19 is inactive and mapped to fifo
0 ra_tid 0x0000 [0,0]
Reloaded with 802.11n disabled:
[93527.356994] Intel(R) Wireless WiFi driver for Linux, in-tree:d
[93527.357000] Copyright(c) 2003-2013 Intel Corporation
[93527.357871] iwlwifi 0000:03:00.0: irq 47 for MSI/MSI-X
[93527.363704] iwlwifi 0000:03:00.0: loaded firmware version 18.168.6.1
[93527.369717] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG enabled
[93527.369724] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS enabled
[93527.369727] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[93527.369730] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE disabled
[93527.369733] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_P2P disabled
[93527.369737] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R)
Advanced-N 6205 AGN, REV=0xB0
[93527.369790] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[93527.385882] ieee80211 phy2: Selected rate control algorithm 'iwl-agn-rs'
[93527.454628] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[93527.461431] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[93527.832913] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[93527.839654] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
...
Any ideas?
thanks,
--
js
suse labs
^ permalink raw reply
* Re: [v3.9.x stable regression, bisected] iwlwifi/iwldvm has a 30s delay in EAP authentication
From: Kshitij Kulshreshtha @ 2013-05-22 9:36 UTC (permalink / raw)
To: Emmanuel Grumbach; +Cc: linux-kernel@vger.kernel.org, linux-wireless, gregkh
In-Reply-To: <CANUX_P1sMR6ugSt1Q=hA4dLXQ=mo+dqbAoMi4dn46jYhZZzL7A@mail.gmail.com>
As on 2013-05-22 10:17h, Emmanuel Grumbach did write:
>
> Thanks for the bisection. Can you please try the patch in
> https://bugzilla.kernel.org/show_bug.cgi?id=58341 and report?
> Thanks
>
I can confirm that the patch in this bugzilla entry does indeed get
rid of the delay in EAP authentication.
Thanks.
Kshitij
--
Dr. Kshitij Kulshreshtha
Institut für Mathematik,
Universität Paderborn,
Warburger Straße 100,
33098 Paderborn.
Büro: A3.235
Privatanschrift:
Arnikaweg 62
33100 Paderborn.
^ permalink raw reply
* Re: [v3.9.x stable regression, bisected] iwlwifi/iwldvm has a 30s delay in EAP authentication
From: Emmanuel Grumbach @ 2013-05-22 10:37 UTC (permalink / raw)
To: kkhere.geo+suse; +Cc: linux-kernel@vger.kernel.org, linux-wireless, gregkh
In-Reply-To: <519C9187.6040301@gmail.com>
>>
>> Thanks for the bisection. Can you please try the patch in
>> https://bugzilla.kernel.org/show_bug.cgi?id=58341 and report?
>> Thanks
>>
>
> I can confirm that the patch in this bugzilla entry does indeed get
> rid of the delay in EAP authentication.
>
Thanks for the testing - patch on the way to upstream / stable
^ permalink raw reply
* Re: Bisected 3.9 regression for iwl4965 connection problem to 1672c0e3
From: Stanislaw Gruszka @ 2013-05-22 11:59 UTC (permalink / raw)
To: Johannes Berg; +Cc: Jake Edge, linux-wireless, lkml
In-Reply-To: <20130507153525.GB1576@redhat.com>
On Tue, May 07, 2013 at 05:35:25PM +0200, Stanislaw Gruszka wrote:
> On Tue, May 07, 2013 at 03:53:30PM +0200, Johannes Berg wrote:
> > > I'm not sure if I like to add passive_no_rx to iwlegacy. Stopping queues
> > > and waiting for beacon looks sticky, what happen if beacon will not be
> > > received?
> >
> > Good question, do we get stuck? I was assuming we'd time out, but maybe
> > that's not the case?
>
> AFICT, we wake queues only if beacon arrives or mac80211 call drv_config
> with BSS_CHANGED_IDLE. I'm not sure if the latter prevent stuck.
It should prevent stuck. When we fail to auth, drv_config() with BSS_CHANGED_IDLE
is called via:
ieee80211_destroy_auth_data ->
ieee80211_vif_release_channel ->
__ieee80211_vif_release_channel ->
ieee80211_unassign_vif_chanctx ->
ieee80211_bss_info_change_notify
But there is need to have ->vif.chanctx_conf valid in
__ieee80211_vif_release_channel(), where is below condition:
conf = rcu_dereference_protected(sdata->vif.chanctx_conf,
lockdep_is_held(&local->chanctx_mtx));
if (!conf)
return;
I'm not sure if that always happen. Perhaps would be better to change
BSS_CHANGED_IDLE to BSS_CHANGED_BSSID, which is called directly from
ieee80211_destroy_auth_data() ?
Stanislaw
^ permalink raw reply
* Re: [PATCH] mac80211: Allow single vif mac address change with addr_mask
From: Jakub Kiciński @ 2013-05-22 12:42 UTC (permalink / raw)
To: Helmut Schaa
Cc: linux-wireless, Johannes Berg, Ivo Van Doorn,
Gertjan van Wingerde, stf_xl@wp.pl, Alessandro Lannocca,
Bruno Randolf
In-Reply-To: <CAGXE3d_HQzN5NNJ5tbDXhoeFdobpSJnvxrqAP5+T8DfyEoV_Uw@mail.gmail.com>
On Wed, 22 May 2013 10:06:26 +0200, Helmut Schaa wrote:
> On Tue, May 21, 2013 at 5:10 PM, Jakub Kiciński <moorray3@wp.pl> wrote:
> > On Tue, 21 May 2013 14:54:53 +0200, Helmut Schaa wrote:
> >> When changing the MAC address of a single vif mac80211 will check if the new
> >> address fits into the address mask specified by the driver. This only needs
> >> to be done when using multiple BSSIDs. Hence, check the new address only
> >> against all other vifs.
> >
> > Oh, I see that you already posted this patch for review!
> >
> > I think we should also take care of the way addresses for new
> > interfaces are chosen otherwise they'll just pick up
> > perm_addr and we will end up with incompatible MACs.
>
> Maybe you could send the assign_pem_addr changes as a follow up patch?
I would rather not, I think it would be messy. Or is your
patch already merged somewhere?
Perhaps you could incorporate the change to assign_pem_addr
into your patch and send v2 adding my Sign-off?
> > @@ -1479,7 +1483,17 @@ static void ieee80211_assign_perm_addr(struct ieee80211_local *local,
> > break;
> > }
> >
> > + /*
> > + * Pick address of existing interface in case user changed
> > + * MAC address manually, default to perm_addr.
> > + */
> > m = local->hw.wiphy->perm_addr;
> > + list_for_each_entry(sdata, &local->interfaces, list) {
> > + if (sdata->vif.type == NL80211_IFTYPE_MONITOR)
> > + continue;
> > + m = sdata->vif.addr;
> > + break;
> > + }
> > start = ((u64)m[0] << 5*8) | ((u64)m[1] << 4*8) |
> > ((u64)m[2] << 3*8) | ((u64)m[3] << 2*8) |
> > ((u64)m[4] << 1*8) | ((u64)m[5] << 0*8);
>
> This is only relevant if the driver registered a addr_mask with mac80211.
> So, maybe you could only select a new address (!=perm_addr) if the
> perm_addr is not covered by the addr_mask?
I'm not sure I understand all the internal logic, but if
driver doesn't set addr_mask it will always get one of
wiphy->addresses or perm_addr and leave on line 1468 [1]
before reaching this code.
[1]http://git.kernel.org/cgit/linux/kernel/git/jberg/mac80211-next.git/tree/net/mac80211/iface.c#n1468
-- Kuba
^ permalink raw reply
* Linux wireless summit, 19-20 September 2013 in New Orleans!
From: John W. Linville @ 2013-05-22 17:18 UTC (permalink / raw)
To: linux-wireless; +Cc: linux-bluetooth, linux-nfc
In-Reply-To: <CALx5=V-wOkHb1Q4A_32LBQm9aP0dUL1J5s4ceLwqVGSYhfpwxw@mail.gmail.com>
Announcement...there will be a Linux wireless networking mini-summit
event coming soon. It will be on 19-20 September in New Orleans,
just after LinuxCon North America and concurrent with the Linux
Plumbers Conference.
Attendees of the wireless mini-summit must also register for
either LinuxCon North America or for Linux Plumbers Conference.
More information is available here:
http://wireless.kernel.org/en/developers/Summits/New-Orleans-2013
Please notice that the above is a wiki -- please add your name to
the bottom of the page if you intend to participate in the wireless
summit event. As the event draws nearer, we will hash-out the
discussion topics and the agenda for the event on that wiki. If you
have suggestions or want other changes, please make them and/or let
us know here.
I hope to see you in New Orleans!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* Re: [PATCH 3.10] cfg80211: fix interface down/disconnect state handling
From: Ben Greear @ 2013-05-22 17:31 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wireless, Johannes Berg
In-Reply-To: <1368516968-29292-1-git-send-email-johannes@sipsolutions.net>
On 05/14/2013 12:36 AM, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> When the interface goes down, there's no need to call
> cfg80211_mlme_down() after __cfg80211_disconnect() as
> the latter will call the former (if appropriate.)
>
> Also, in __cfg80211_disconnect(), if the cfg80211 SME
> isn't used, __cfg80211_disconnected() may still need
> to be called (depending on the current state) so that
> the SME state gets cleared.
3.9.3 with this patch (and others) was running well until I
tweaked user-space to drive a bit harder/differently and removed the
noisy printk from my sme state debugging patches.
Now, it appears the problem is back..though of course I
don't have useful debugging as to why :P
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply
* RE: [PATCH 2/2] cfg80211/nl80211: Add coalesce support
From: Bing Zhao @ 2013-05-22 18:06 UTC (permalink / raw)
To: Johannes Berg
Cc: Luis R. Rodriguez, linux-wireless@vger.kernel.org, Jouni Malinen,
Vasanthakumar Thiagarajan, Senthil Balasubramanian,
Luciano Coelho, Amitkumar Karwar
In-Reply-To: <1369210344.8207.0.camel@jlt4.sipsolutions.net>
SGkgSm9oYW5uZXMsDQoNCj4gPiAicGFja2V0IGNvYWxlc2NlIiB3aWxsIHJldXNlIHRoZSBwYXR0
ZXJuIHN0cnVjdHVyZSAoYW5kIGl0cyBlbnVtIGRlZmluaXRpb25zKSBkZWZpbmVkIGZvcg0KPiA+
IFdvV0xBTi4gSXQncyByZW5hbWVkIHNvIHRoYXQgYm90aCBXb1dMQU4gYW5kIENvYWxlc2NlIGNh
biBtYWtlIHVzZSBvZiBpdC4NCj4gDQo+IEJlZm9yZSB5b3UgbWFrZSBhbnkgY2hhbmdlcyAoSSBk
aWRuJ3QgZ2V0IGFyb3VuZCB0byBjb21tZW50aW5nIG9uIHlvdXINCj4gcGF0Y2hlcyB5ZXN0ZXJk
YXkpLCBJIHRoaW5rIHlvdSBoYXZlIHRvIGJlIG1vcmUgY2FyZWZ1bCB3aXRoIHRoZSByZW5hbWVz
DQo+IHRvIG5vdCBicmVhayB0aGUgQVBJLiBQbGVhc2UgcHJvdmlkZSBkZWZpbmVzIG9yIHNvIHRv
IG5vdCBicmVhaw0KPiBjb21waWxhdGlvbiBpbiB0aGUgcmVuYW1lLg0KDQoiW1BBVENIIDEvMl0g
Y2ZnODAyMTEvbmw4MDIxMTogcmVuYW1lIHBhY2tldCBwYXR0ZXJuIHJlbGF0ZWQgc3RydWN0dXJl
cyBhbmQgZW51bXMiIHNob3VsZCBoYXZlIHRha2VuIGNhcmUgb2YgdGhlIHJlbmFtZXMuIFBsZWFz
ZSBsZXQgbWUga25vdyBpZiBJIG1pc3NlZCBhbnl0aGluZyBoZXJlLg0KDQpPZiBjb3Vyc2UgdGhl
IGRvY3VtZW50YXRpb24gYXMgTHVpcyBjb21tZW50ZWQgd2lsbCBiZSBhZGRlZCBpbiB2MiBzZXJp
ZXMuDQoNClRoYW5rcywNCkJpbmcNCg==
^ permalink raw reply
* Re: [PATCH 3.10] cfg80211: fix interface down/disconnect state handling
From: Ben Greear @ 2013-05-22 18:15 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wireless, Johannes Berg
In-Reply-To: <519D00EF.60002@candelatech.com>
On 05/22/2013 10:31 AM, Ben Greear wrote:
> On 05/14/2013 12:36 AM, Johannes Berg wrote:
>> From: Johannes Berg <johannes.berg@intel.com>
>>
>> When the interface goes down, there's no need to call
>> cfg80211_mlme_down() after __cfg80211_disconnect() as
>> the latter will call the former (if appropriate.)
>>
>> Also, in __cfg80211_disconnect(), if the cfg80211 SME
>> isn't used, __cfg80211_disconnected() may still need
>> to be called (depending on the current state) so that
>> the SME state gets cleared.
>
> 3.9.3 with this patch (and others) was running well until I
> tweaked user-space to drive a bit harder/differently and removed the
> noisy printk from my sme state debugging patches.
>
> Now, it appears the problem is back..though of course I
> don't have useful debugging as to why :P
Err, maybe it's something elsewhere in my logic.
Kernel debugging seems to show proper activity so far...
Ben
>
> Ben
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply
* Re: [PATCH 2/2] cfg80211/nl80211: Add coalesce support
From: Johannes Berg @ 2013-05-22 18:23 UTC (permalink / raw)
To: Bing Zhao
Cc: Luis R. Rodriguez, linux-wireless@vger.kernel.org, Jouni Malinen,
Vasanthakumar Thiagarajan, Senthil Balasubramanian,
Luciano Coelho, Amitkumar Karwar
In-Reply-To: <477F20668A386D41ADCC57781B1F70430E801DC176@SC-VEXCH1.marvell.com>
> > Before you make any changes (I didn't get around to commenting on your
> > patches yesterday), I think you have to be more careful with the renames
> > to not break the API. Please provide defines or so to not break
> > compilation in the rename.
>
> "[PATCH 1/2] cfg80211/nl80211: rename packet pattern related
> structures and enums" should have taken care of the renames. Please
> let me know if I missed anything here.
It did in the kernel, I was referring to the changes in nl80211.h, as
far as I can tell those break existing userspace tools. You should be
able to compile tools like iw and wpa_supplicant with the new nl80211.h
without changing anything in them.
johannes
^ permalink raw reply
* Ralink RT3290 proprietary drivers causing kernel panic
From: Mohit @ 2013-05-22 18:24 UTC (permalink / raw)
To: linux-wireless
Hello,
I am on openSUSE 12.3 with kernel 3.7.10-1.4-desktop, i
wanted to try out the proprietary drivers for Ralink RT3290 so i
downloaded the drivers from
http://www.mediatek.com/_en/07_downloads/01_windows.php?sn=501 and
compiled the drivers as mentioned on my thread here :
https://forums.opensuse.org/english/get-technical-help-here/wireless/486975-rt3290-wireless-proprietary-drivers-not-working.html#post2557514.
Everything compiled fine, openSUSE was able to scan and connect to
access points after installation, but when i access the internet a
kernel panic occurs after ~5sec (time varies based on the data usage).
So i humbly request you to please provide the solution for the same, you
can reach me through email or reply to my thread (probably faster as i
don't check my email everyday).
Thank You!
--
--
******************************************************************************************************************************************************************
"This e-Mail may contain proprietary and confidential information and is
sent for the intended recipient(s) only. If, by an addressing or
transmission error, this mail has been misdirected to you, you are
requested to delete this mail immediately.You are also hereby notified that
any use, any form of reproduction, dissemination, copying, disclosure,
modification, distribution and/or publication of this e-mail
message,contents or its attachment(s) other than by its intended
recipient(s) is strictly prohibited.Any opinions expressed in this email
are those of the individual and not necessarily of the organization.Before
opening attachment(s), please scan for viruses."
**********************************************************************************************************************************************************************
^ permalink raw reply
* Re: [GIT] [3.10] NFC fixes
From: John W. Linville @ 2013-05-22 18:27 UTC (permalink / raw)
To: Samuel Ortiz; +Cc: Linux Wireless, Linux NFC
In-Reply-To: <20130521230711.GD4566@zurbaran>
On Wed, May 22, 2013 at 01:07:11AM +0200, Samuel Ortiz wrote:
> Hi John,
>
> This is the first batch of NFC fixes for 3.10, and it contains:
>
> - 3 fixes for the NFC MEI support:
> * We now depend on the correct Kconfig symbol.
> * We register an MEI event callback whenever we enable an NFC device,
> otherwise we fail to read anything after an enable/disable cycle.
> * We only disable an MEI device from its disable mey_phy_ops,
> preventing useless consecutive disable calls.
>
> - An NFC Makefile cleanup, as I forgot to remove a commented out line when
> moving the LLCP code to the NFC top level directory.
>
> The following changes since commit 6bb4880d9ef30375da4507aeabd6dc261a2c6c2b:
>
> ath9k: fix draining aggregation tid buffers (2013-05-17 14:31:09 -0400)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-fixes.git tags/nfc-fixes-3.10-1
>
> for you to fetch changes up to e3a6b14ceda0207c3405c6266e5177a85c0db044:
>
> NFC: mei: Do not disable MEI devices from their remove routine (2013-05-21 10:48:41 +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* RE: [PATCH 2/2] cfg80211/nl80211: Add coalesce support
From: Bing Zhao @ 2013-05-22 18:46 UTC (permalink / raw)
To: Johannes Berg
Cc: Luis R. Rodriguez, linux-wireless@vger.kernel.org, Jouni Malinen,
Vasanthakumar Thiagarajan, Senthil Balasubramanian,
Luciano Coelho, Amitkumar Karwar
In-Reply-To: <1369246994.8207.24.camel@jlt4.sipsolutions.net>
SGkgSm9oYW5uZXMsDQoNCj4gPiA+IEJlZm9yZSB5b3UgbWFrZSBhbnkgY2hhbmdlcyAoSSBkaWRu
J3QgZ2V0IGFyb3VuZCB0byBjb21tZW50aW5nIG9uIHlvdXINCj4gPiA+IHBhdGNoZXMgeWVzdGVy
ZGF5KSwgSSB0aGluayB5b3UgaGF2ZSB0byBiZSBtb3JlIGNhcmVmdWwgd2l0aCB0aGUgcmVuYW1l
cw0KPiA+ID4gdG8gbm90IGJyZWFrIHRoZSBBUEkuIFBsZWFzZSBwcm92aWRlIGRlZmluZXMgb3Ig
c28gdG8gbm90IGJyZWFrDQo+ID4gPiBjb21waWxhdGlvbiBpbiB0aGUgcmVuYW1lLg0KPiA+DQo+
ID4gIltQQVRDSCAxLzJdIGNmZzgwMjExL25sODAyMTE6IHJlbmFtZSBwYWNrZXQgcGF0dGVybiBy
ZWxhdGVkDQo+ID4gc3RydWN0dXJlcyBhbmQgZW51bXMiIHNob3VsZCBoYXZlIHRha2VuIGNhcmUg
b2YgdGhlIHJlbmFtZXMuIFBsZWFzZQ0KPiA+IGxldCBtZSBrbm93IGlmIEkgbWlzc2VkIGFueXRo
aW5nIGhlcmUuDQo+IA0KPiBJdCBkaWQgaW4gdGhlIGtlcm5lbCwgSSB3YXMgcmVmZXJyaW5nIHRv
IHRoZSBjaGFuZ2VzIGluIG5sODAyMTEuaCwgYXMNCj4gZmFyIGFzIEkgY2FuIHRlbGwgdGhvc2Ug
YnJlYWsgZXhpc3RpbmcgdXNlcnNwYWNlIHRvb2xzLiBZb3Ugc2hvdWxkIGJlDQo+IGFibGUgdG8g
Y29tcGlsZSB0b29scyBsaWtlIGl3IGFuZCB3cGFfc3VwcGxpY2FudCB3aXRoIHRoZSBuZXcgbmw4
MDIxMS5oDQo+IHdpdGhvdXQgY2hhbmdpbmcgYW55dGhpbmcgaW4gdGhlbS4NCg0KSSBzZWUuIFRo
YW5rcyBmb3IgeW91ciBoZWxwLg0KDQpSZWdhcmRzLA0KQmluZw0KDQo=
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox