iwlagn (3.3-wl), the saga continuous

iwlagn (3.3-wl), the saga continuous

[Norbert Preining]

Dear all,

I am now running 3.3.0-wl, and I was now travelling quite some time
without having *any*problems with wlan. But as soon as I come
home or to the university the horror starts. Here at home I am 
now, after fresh reboot, no suspend involved, swamped with dmesg
lines:
[ 8206.158741] delba from 00:0a:79:eb:56:10 (initiator) tid 0 reason code 39
[ 8206.158744] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 8206.430282] Rx A-MPDU request on tid 0 result 0

So around 4000+ in 2 hours ... I guess you can evaluate how flaky the
connection is ...

As usual, any patches to be tested etc I can do. All of that is easy
to reproduce ;-)

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
NAAS (n.)
The winemaking region of Albania where most of the wine that people
take to bottle-parties comes from.
			--- Douglas Adams, The Meaning of Liff

3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

Dear all,

I am now having problems with the iwlagn driver since about 4 kernel
revisions, without any tendency that things are getting better.

I already have reported that with 3.3-wl there are hundreds and thousands
of lines
	delba from 00:0a:79:eb:56:10 (initiator) tid 0 reason code 39
	Rx BA session stop requested for ...
*IF* it is connected.

On the contrary, it sometimes not even connects, after reloading the module,
retrying many times, today my log was smarmed with messages:
	[ 9457.156030] wlan0: authentication with 00:24:c4:ab:bd:e0 timed out
	[ 9457.176828] iwlwifi 0000:06:00.0: ACTIVATE a non DRIVER active station id 0 addr 00:24:c4:ab:bd:e0

Above is all on the University network, which is rather new and
in good shape.

But I want to report *SOME* progress: Formerly I had *BIG* problems 
with my home network (some strange Corega WL router AFAIR, Japanese only,
but it was working without a click before 2.6.38 or 39 or so).
Now, when I *DISABLE* 11n (11n_disable=1) then all the problems are
gone *AT*HOME*, no warnings anymore, no complains, no hickups.
On the university it is still a pain.

As I have already sent debug output etc etc as requested here, I will
not repeat that unless asked for it.

Well, hope that in another 20 kernel revisions that might get fixed,
we are not talking about a brand new wlan adapter anymore ... that
was some years ago ... especially the regression from 2.6.38 where it
was working without any problem to the current very sad state of affair
is frustrating.


On Fr, 30 Mär 2012, Norbert Preining wrote:
> I am now running 3.3.0-wl, and I was now travelling quite some time
> without having *any*problems with wlan. But as soon as I come
> home or to the university the horror starts. Here at home I am 
> now, after fresh reboot, no suspend involved, swamped with dmesg
> lines:
> [ 8206.158741] delba from 00:0a:79:eb:56:10 (initiator) tid 0 reason code 39
> [ 8206.158744] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
> [ 8206.430282] Rx A-MPDU request on tid 0 result 0
> 
> So around 4000+ in 2 hours ... I guess you can evaluate how flaky the
> connection is ...

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
GOLANT (adj.)
Blank, sly and faintly embarrassed. Pertaining to the expression seen
on the face of someone who has clearly forgotten your name.
			--- Douglas Adams, The Meaning of Liff

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[David Miller]

From: Norbert Preining <preining@logic.at>
Date: Wed, 11 Apr 2012 11:37:47 +0900

> Well, hope that in another 20 kernel revisions that might get fixed,
> we are not talking about a brand new wlan adapter anymore ... that
> was some years ago ... especially the regression from 2.6.38 where it
> was working without any problem to the current very sad state of affair
> is frustrating.

In those 20 kernel revisions you, or a party interested in helping
you, could have GIT bisected the guilty change which introduced
the problem.

Then we'd have something concrete to go on, and use to work towards a
fix.

Right now there isn't nearly enough information to fix the problem.

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Ted Ts'o]

On Tue, Apr 10, 2012 at 10:54:51PM -0400, David Miller wrote:
> 
> In those 20 kernel revisions you, or a party interested in helping
> you, could have GIT bisected the guilty change which introduced
> the problem.
> 
> Then we'd have something concrete to go on, and use to work towards a
> fix.
> 
> Right now there isn't nearly enough information to fix the problem.

I'll note that I've been having troubles with my iwlagn driver losing
the ability to connect to WPA2 authenticated AP's at work (Google
Cambridge).  This has been true for since sometime around 3.0; my
excuse for why I haven't tried bisecting it is that it can take
several hours for the bug to manifest itself, and when it does, it's
much simpler to either (a) reboot, or (b) rmmod iwlagn and then
modprobe iwlagn.

I also don't know if it's a problem with (a) the iwlagn driver, (b) my
hardware, (c) the network-manager WPA code, or (d) the enterprise AP
that we are using, or some combination of the four.  On my todo list
is to get a completely different 802.11abn wireless PC Card, and then
try to see if the problem reproduces itself there, and then see if I
can at some point try to set aside a full week where I'd do nothing
else with my laptop but git bisects full-time.

Sometimes, git bisects are not terribly useful ways of trying to find
the problem commits --- and I've tried doing them before to debug
iwlagn problems twice before, and past experience tells me it's a
minimum of 1, and usually more like 2 or 3 days of lost productivity
while I try to debug it --- and that's when the problem is obvious
within 10 or 20 minutes of the reboot.  :-(

						- Ted

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Dave Jones]

On Wed, Apr 11, 2012 at 02:40:47PM -0400, Ted Ts'o wrote:

 > I'll note that I've been having troubles with my iwlagn driver losing
 > the ability to connect to WPA2 authenticated AP's at work (Google
 > Cambridge).  This has been true for since sometime around 3.0; my
 > excuse for why I haven't tried bisecting it is that it can take
 > several hours for the bug to manifest itself, and when it does, it's
 > much simpler to either (a) reboot, or (b) rmmod iwlagn and then
 > modprobe iwlagn.
 > 
 > I also don't know if it's a problem with (a) the iwlagn driver, (b) my
 > hardware, (c) the network-manager WPA code, or (d) the enterprise AP
 > that we are using, or some combination of the four.  On my todo list
 > is to get a completely different 802.11abn wireless PC Card, and then
 > try to see if the problem reproduces itself there, and then see if I
 > can at some point try to set aside a full week where I'd do nothing
 > else with my laptop but git bisects full-time.
 > 
 > Sometimes, git bisects are not terribly useful ways of trying to find
 > the problem commits --- and I've tried doing them before to debug
 > iwlagn problems twice before, and past experience tells me it's a
 > minimum of 1, and usually more like 2 or 3 days of lost productivity
 > while I try to debug it --- and that's when the problem is obvious
 > within 10 or 20 minutes of the reboot.  :-(

iwlwifi has a debug module option which generates a ton of spew, but
the Intel developers have managed to diagnose several iwlwifi problems
I've had by staring at the dumps. Starting there is probably going to
be faster than bisecting. (Especially when you're in a situation like I was
where it was just 'differently broken' at various points in time).

	Dave

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

On Mi, 11 Apr 2012, Dave Jones wrote:
>  > I'll note that I've been having troubles with my iwlagn driver losing
>  > the ability to connect to WPA2 authenticated AP's at work (Google
>  > Cambridge).  This has been true for since sometime around 3.0; my
>  > excuse for why I haven't tried bisecting it is that it can take
>  > several hours for the bug to manifest itself, and when it does, it's
>  > much simpler to either (a) reboot, or (b) rmmod iwlagn and then
>  > modprobe iwlagn.

Agreed. 150%

> iwlwifi has a debug module option which generates a ton of spew, but
> the Intel developers have managed to diagnose several iwlwifi problems

I sent already several times *loads* of these dumps to the developers.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
MELLON UDRIGLE (n.)
The ghastly sound made by traditional folksingers.
			--- Douglas Adams, The Meaning of Liff

RE: 3.4-rc2, ilwagn still most of the time completely unusable

[Venkataraman, Meenakshi]

Hi Norbert,

Sorry about the annoyance it is causing you...but let's see if we can solve the problems you're seeing.

>I already have reported that with 3.3-wl there are hundreds and thousands of
>lines
>	delba from 00:0a:79:eb:56:10 (initiator) tid 0 reason code 39
>	Rx BA session stop requested for ...
>*IF* it is connected.

[MV]  This is actually printed by mac80211 when it stops a block ack session; which can happen with bursty traffic. It's not an error per se. You'll see this message if you have debugging enabled for mac80211, specifically CONFIG_MAC80211_HT_DEBUG. Perhaps you could reduce the debugging information you print out for mac80211?

>On the contrary, it sometimes not even connects, after reloading the module,
>retrying many times, today my log was smarmed with messages:
>	[ 9457.156030] wlan0: authentication with 00:24:c4:ab:bd:e0 timed out
>	[ 9457.176828] iwlwifi 0000:06:00.0: ACTIVATE a non DRIVER active
>station id 0 addr 00:24:c4:ab:bd:e0

[MV]  this could potentially be a problem with our driver. I would like some logs to figure out what happened here. Can you send me a detailed dmesg log with debug=0xFFFFFFFF?  Thanks. :-)

>But I want to report *SOME* progress: Formerly I had *BIG* problems with
>my home network (some strange Corega WL router AFAIR, Japanese only, but
>it was working without a click before 2.6.38 or 39 or so).
>Now, when I *DISABLE* 11n (11n_disable=1) then all the problems are gone
>*AT*HOME*, no warnings anymore, no complains, no hickups.
>On the university it is still a pain.

[MV] Any idea how 11n is performing with 3.4-rc2 on your home network? Are you seeing the same problems as before?

Thanks,
Meenakshi

RE: 3.4-rc2, ilwagn still most of the time completely unusable

[Venkataraman, Meenakshi]

Hi Norbert,

Sorry about the annoyance it is causing you...but let's see if we can solve the problems you're seeing.

>I already have reported that with 3.3-wl there are hundreds and thousands of
>lines
>	delba from 00:0a:79:eb:56:10 (initiator) tid 0 reason code 39
>	Rx BA session stop requested for ...
>*IF* it is connected.

[MV]  This is actually printed by mac80211 when it stops a block ack session; which can happen with bursty traffic. It's not an error per se. You'll see this message if you have debugging enabled for mac80211, specifically CONFIG_MAC80211_HT_DEBUG. Perhaps you could reduce the debugging information you print out for mac80211?

>On the contrary, it sometimes not even connects, after reloading the module,
>retrying many times, today my log was smarmed with messages:
>	[ 9457.156030] wlan0: authentication with 00:24:c4:ab:bd:e0 timed out
>	[ 9457.176828] iwlwifi 0000:06:00.0: ACTIVATE a non DRIVER active
>station id 0 addr 00:24:c4:ab:bd:e0

[MV]  this could potentially be a problem with our driver. I would like some logs to figure out what happened here. Can you send me a detailed dmesg log with debug=0xFFFFFFFF?  Thanks. :-)

>But I want to report *SOME* progress: Formerly I had *BIG* problems with
>my home network (some strange Corega WL router AFAIR, Japanese only, but
>it was working without a click before 2.6.38 or 39 or so).
>Now, when I *DISABLE* 11n (11n_disable=1) then all the problems are gone
>*AT*HOME*, no warnings anymore, no complains, no hickups.
>On the university it is still a pain.

[MV] Any idea how 11n is performing with 3.4-rc2 on your home network? Are you seeing the same problems as before?

Thanks,
Meenakshi

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

Hi Meenakshi,

thanks for your email

On Mi, 11 Apr 2012, Venkataraman, Meenakshi wrote:
> Sorry about the annoyance it is causing you...but let's see if we can solve the problems you're seeing.

Yes, let us make another trial ;-)

> >	delba from 00:0a:79:eb:56:10 (initiator) tid 0 reason code 39
> >	Rx BA session stop requested for ...
> >*IF* it is connected.
> 
> [MV]  This is actually printed by mac80211 when it stops a block ack session; which can happen with bursty traffic. It's not an error per se. You'll see this message if you have debugging enabled for mac80211, specifically CONFIG_MAC80211_HT_DEBUG. Perhaps you could reduce the debugging information you print out for mac80211?

Probably I was asked to activate that at some point ;-) Will disactivate
it. Thanks.

> >On the contrary, it sometimes not even connects, after reloading the module,
> >retrying many times, today my log was smarmed with messages:
> >	[ 9457.156030] wlan0: authentication with 00:24:c4:ab:bd:e0 timed out
> >	[ 9457.176828] iwlwifi 0000:06:00.0: ACTIVATE a non DRIVER active
> >station id 0 addr 00:24:c4:ab:bd:e0
> 
> [MV]  this could potentially be a problem with our driver. I would like some logs to figure out what happened here. Can you send me a detailed dmesg log with debug=0xFFFFFFFF?  Thanks. :-)

I will do when I am back at university.

> >But I want to report *SOME* progress: Formerly I had *BIG* problems with
> >my home network (some strange Corega WL router AFAIR, Japanese only, but
> >it was working without a click before 2.6.38 or 39 or so).
> >Now, when I *DISABLE* 11n (11n_disable=1) then all the problems are gone
> >*AT*HOME*, no warnings anymore, no complains, no hickups.
> >On the university it is still a pain.
> 
> [MV] Any idea how 11n is performing with 3.4-rc2 on your home network? Are you seeing the same problems as before?

On the university often no connection at all.
At home: connection hangs for several seconds, when I look at the 
ping www.kernel.org I have more than 20% packet loss. And interestingly
quite often the ping looks like:
64 bytes from pub1.kernel.org (149.20.20.133): icmp_req=131 ttl=53 time=125 ms
64 bytes from pub1.kernel.org (149.20.20.133): icmp_req=133 ttl=53 time=124 ms
64 bytes from 149.20.20.133: icmp_req=134 ttl=53 time=135 ms
64 bytes from pub1.kernel.org (149.20.20.133): icmp_req=135 ttl=53 time=123 ms
64 bytes from pub1.kernel.org (149.20.20.133): icmp_req=136 ttl=53 time=121 ms
which does NOT relate in anyway to my feeling, because when I 
check the *real* time *before* the line
	64 bytes from 149.20.20.133: icmp_req=134 ttl=53 time=135 ms
there are *several* seconds, (3-4, sometimes more) of waiting time.

That of course destroys regularly every ssh and ftp connection.
http is of course not the problem (but who cares for the web?).

I have create a log with the above debug settings but 11n NOT disabled.
I also added some
	===== remarks =======
(variable number of =, tough, but at least always 4, so you can search
for ====) with logger "....". The log is *BIG*, compressed 3Mb, you
can find it here:
	http://www.logic.at/people/preining/syslog.bz2

Ok, when I have something from the university I will let you know.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
IPING (participial vb.)
The increasingly anxious shifting from leg to leg you go through when
you are desperate to go to the lavatory and the person you are talking
to keeps on remembering a few final things he want to mention.
			--- Douglas Adams, The Meaning of Liff

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

Hi Meenakshi,

thanks for your email

On Mi, 11 Apr 2012, Venkataraman, Meenakshi wrote:
> Sorry about the annoyance it is causing you...but let's see if we can solve the problems you're seeing.

Yes, let us make another trial ;-)

> >	delba from 00:0a:79:eb:56:10 (initiator) tid 0 reason code 39
> >	Rx BA session stop requested for ...
> >*IF* it is connected.
> 
> [MV]  This is actually printed by mac80211 when it stops a block ack session; which can happen with bursty traffic. It's not an error per se. You'll see this message if you have debugging enabled for mac80211, specifically CONFIG_MAC80211_HT_DEBUG. Perhaps you could reduce the debugging information you print out for mac80211?

Probably I was asked to activate that at some point ;-) Will disactivate
it. Thanks.

> >On the contrary, it sometimes not even connects, after reloading the module,
> >retrying many times, today my log was smarmed with messages:
> >	[ 9457.156030] wlan0: authentication with 00:24:c4:ab:bd:e0 timed out
> >	[ 9457.176828] iwlwifi 0000:06:00.0: ACTIVATE a non DRIVER active
> >station id 0 addr 00:24:c4:ab:bd:e0
> 
> [MV]  this could potentially be a problem with our driver. I would like some logs to figure out what happened here. Can you send me a detailed dmesg log with debug=0xFFFFFFFF?  Thanks. :-)

I will do when I am back at university.

> >But I want to report *SOME* progress: Formerly I had *BIG* problems with
> >my home network (some strange Corega WL router AFAIR, Japanese only, but
> >it was working without a click before 2.6.38 or 39 or so).
> >Now, when I *DISABLE* 11n (11n_disable=1) then all the problems are gone
> >*AT*HOME*, no warnings anymore, no complains, no hickups.
> >On the university it is still a pain.
> 
> [MV] Any idea how 11n is performing with 3.4-rc2 on your home network? Are you seeing the same problems as before?

On the university often no connection at all.
At home: connection hangs for several seconds, when I look at the 
ping www.kernel.org I have more than 20% packet loss. And interestingly
quite often the ping looks like:
64 bytes from pub1.kernel.org (149.20.20.133): icmp_req=131 ttl=53 time=125 ms
64 bytes from pub1.kernel.org (149.20.20.133): icmp_req=133 ttl=53 time=124 ms
64 bytes from 149.20.20.133: icmp_req=134 ttl=53 time=135 ms
64 bytes from pub1.kernel.org (149.20.20.133): icmp_req=135 ttl=53 time=123 ms
64 bytes from pub1.kernel.org (149.20.20.133): icmp_req=136 ttl=53 time=121 ms
which does NOT relate in anyway to my feeling, because when I 
check the *real* time *before* the line
	64 bytes from 149.20.20.133: icmp_req=134 ttl=53 time=135 ms
there are *several* seconds, (3-4, sometimes more) of waiting time.

That of course destroys regularly every ssh and ftp connection.
http is of course not the problem (but who cares for the web?).

I have create a log with the above debug settings but 11n NOT disabled.
I also added some
	===== remarks =======
(variable number of =, tough, but at least always 4, so you can search
for ====) with logger "....". The log is *BIG*, compressed 3Mb, you
can find it here:
	http://www.logic.at/people/preining/syslog.bz2

Ok, when I have something from the university I will let you know.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
IPING (participial vb.)
The increasingly anxious shifting from leg to leg you go through when
you are desperate to go to the lavatory and the person you are talking
to keeps on remembering a few final things he want to mention.
			--- Douglas Adams, The Meaning of Liff

RE: 3.4-rc2, ilwagn still most of the time completely unusable

[Venkataraman, Meenakshi]

Hi Norbert,

>> >	delba from 00:0a:79:eb:56:10 (initiator) tid 0 reason code 39
>> >	Rx BA session stop requested for ...
>> >*IF* it is connected.
>>
>> [MV]  This is actually printed by mac80211 when it stops a block ack session;
>which can happen with bursty traffic. It's not an error per se. You'll see this
>message if you have debugging enabled for mac80211, specifically
>CONFIG_MAC80211_HT_DEBUG. Perhaps you could reduce the debugging
>information you print out for mac80211?
>
>Probably I was asked to activate that at some point ;-) Will disactivate it.
>Thanks.

[MV] Well...actually don't turn off this debugging yet. Johannes tells me that these messages could still be due to an issue with the driver. I was looking at the standards, and  Reason code 39 means that the peer (the AP) is requesting this due to a timeout. I  don't see that in the log you sent me, so not sure what timed out. However, I do see Rx BA session stop requests from the AP with reason code 32, which is based on the standard means "disassociated for unspecified QoS related reason".

In your logs I also see missed beacon notifications from the firmware ~every 500 milliseconds. My thought is that it is probably due to turning on power save. I'm not sure if it is affecting the performance of your system overall. Are you using the power save option? And if so, what is the behaviour when power save is turned off?

I don't see the invalid station activation error in the log you sent me, so I'm guessing it appears only on the other network. Do send us logs for that. 

If you're up for it, I'd ask you to do one thing  (or three) -- open 3 separate bugs for the issues you're seeing at: bugzilla.intellinuxwireless.org so we can keep track of them separately. The issue of trying to activate an invalid station ID is definitely a new one, and likely due to a different cause than that related to aggregation or the troubles you're having even with 11n disabled. I could do this too, and add you to the CC list. I might need logs for these bugs, but not yet.

Thanks,
Meenakshi

RE: 3.4-rc2, ilwagn still most of the time completely unusable

[Venkataraman, Meenakshi]

Hi Norbert,

>> >	delba from 00:0a:79:eb:56:10 (initiator) tid 0 reason code 39
>> >	Rx BA session stop requested for ...
>> >*IF* it is connected.
>>
>> [MV]  This is actually printed by mac80211 when it stops a block ack session;
>which can happen with bursty traffic. It's not an error per se. You'll see this
>message if you have debugging enabled for mac80211, specifically
>CONFIG_MAC80211_HT_DEBUG. Perhaps you could reduce the debugging
>information you print out for mac80211?
>
>Probably I was asked to activate that at some point ;-) Will disactivate it.
>Thanks.

[MV] Well...actually don't turn off this debugging yet. Johannes tells me that these messages could still be due to an issue with the driver. I was looking at the standards, and  Reason code 39 means that the peer (the AP) is requesting this due to a timeout. I  don't see that in the log you sent me, so not sure what timed out. However, I do see Rx BA session stop requests from the AP with reason code 32, which is based on the standard means "disassociated for unspecified QoS related reason".

In your logs I also see missed beacon notifications from the firmware ~every 500 milliseconds. My thought is that it is probably due to turning on power save. I'm not sure if it is affecting the performance of your system overall. Are you using the power save option? And if so, what is the behaviour when power save is turned off?

I don't see the invalid station activation error in the log you sent me, so I'm guessing it appears only on the other network. Do send us logs for that. 

If you're up for it, I'd ask you to do one thing  (or three) -- open 3 separate bugs for the issues you're seeing at: bugzilla.intellinuxwireless.org so we can keep track of them separately. The issue of trying to activate an invalid station ID is definitely a new one, and likely due to a different cause than that related to aggregation or the troubles you're having even with 11n disabled. I could do this too, and add you to the CC list. I might need logs for these bugs, but not yet.

Thanks,
Meenakshi

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

Hi,

On Fr, 13 Apr 2012, Venkataraman, Meenakshi wrote:
> [MV] Well...actually don't turn off this debugging yet.

Ok, just compiled and rebooted with new git checkout, but will recompile
with option again enabled.

> In your logs I also see missed beacon notifications from the firmware ~every 500 milliseconds. My thought is that it is probably due to turning on power save. I'm not sure if it is affecting the performance of your system overall. Are you using the power save option? And if so, what is the behaviour when power save is turned off?

I am not sure what you mean with power safe of the iwl driver. If I do
	iwconfig wlan0
I see
	Power Management:off
is this what you mean, and 
	$ cat /sys/class/ieee80211/phy2/power/runtime_enabled
	disabled
Is it what you mean?

> I don't see the invalid station activation error in the log you sent me, so I'm guessing it appears only on the other network. Do send us logs for that. 

Yes, that is on a differnet network. As soon as I can catch the log I 
send it.

> If you're up for it, I'd ask you to do one thing  (or three) -- open 3 separate bugs for the issues you're seeing at: bugzilla.intellinuxwireless.org so we can keep track of them separately. The issue of trying to activate an invalid station ID is definitely a new one, and likely due to a different cause than that related to aggregation or the troubles you're having even with 11n disabled. I could do this too, and add you to the CC list. I might need logs for these bugs, but not yet.

Sure, will do that.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
ESHER (n.)
One of those push tapes installed in public washrooms enabling the
user to wash their trousers without actually getting into the
basin. The most powerful esher of recent years was 'damped down' by
Red Adair after an incredible sixty-eight days' fight in Manchester's
Piccadilly Station.
			--- Douglas Adams, The Meaning of Liff

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

Hi,

On Fr, 13 Apr 2012, Venkataraman, Meenakshi wrote:
> [MV] Well...actually don't turn off this debugging yet.

Ok, just compiled and rebooted with new git checkout, but will recompile
with option again enabled.

> In your logs I also see missed beacon notifications from the firmware ~every 500 milliseconds. My thought is that it is probably due to turning on power save. I'm not sure if it is affecting the performance of your system overall. Are you using the power save option? And if so, what is the behaviour when power save is turned off?

I am not sure what you mean with power safe of the iwl driver. If I do
	iwconfig wlan0
I see
	Power Management:off
is this what you mean, and 
	$ cat /sys/class/ieee80211/phy2/power/runtime_enabled
	disabled
Is it what you mean?

> I don't see the invalid station activation error in the log you sent me, so I'm guessing it appears only on the other network. Do send us logs for that. 

Yes, that is on a differnet network. As soon as I can catch the log I 
send it.

> If you're up for it, I'd ask you to do one thing  (or three) -- open 3 separate bugs for the issues you're seeing at: bugzilla.intellinuxwireless.org so we can keep track of them separately. The issue of trying to activate an invalid station ID is definitely a new one, and likely due to a different cause than that related to aggregation or the troubles you're having even with 11n disabled. I could do this too, and add you to the CC list. I might need logs for these bugs, but not yet.

Sure, will do that.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
ESHER (n.)
One of those push tapes installed in public washrooms enabling the
user to wash their trousers without actually getting into the
basin. The most powerful esher of recent years was 'damped down' by
Red Adair after an incredible sixty-eight days' fight in Manchester's
Piccadilly Station.
			--- Douglas Adams, The Meaning of Liff

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

Hi Meenakshi,

On Fr, 13 Apr 2012, Venkataraman, Meenakshi wrote:
> In your logs I also see missed beacon notifications from the firmware ~every 500 milliseconds. My thought is that it is probably due to turning on power save. I'm not sure if it is affecting the performance of your system overall. Are you using the power save option? And if so, what is the behaviour when power save is turned off?

Good point. I have now changed iwlwifi to load with power_save=0
because as I found someone (don't ask me who!, nm? gnome? acpi?)
turns on power saving.

WIth that turned off I *believe* I have better results, but I will tet
it a bi tmore.

> I don't see the invalid station activation error in the log you sent me, so I'm guessing it appears only on the other network. Do send us logs for that. 

Now I got one ....
	http://www.logic.at/people/preining/syslog-debug.bz2
take care, unpacked it is big!

One more thing, I believe that this happens most of the times
(but not necessarily exclusively, but I don't have statistics)
after resume (from suspend to ram).

So saying, it seems that with power_save=0 even if I get several of
these:
[ 1601.552069] tx session timer expired on tid 0
[ 1601.552116] Tx BA session stop requested for 00:24:c4:ab:bd:e0 tid 0
[ 1601.576292] Stopping Tx BA session for 00:24:c4:ab:bd:e0 tid 0
[ 1603.470312] Open BA session requested for 00:24:c4:ab:bd:e0 tid 0
[ 1603.480274] activated addBA response timer on tid 0
[ 1603.483479] switched off addBA timer for tid 0
[ 1603.483485] Aggregation is on for tid 0
the connection does not break down, as before. Well, I am not sure whether
it is a consequence or coincidence.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
GWEEK (n.)
A coat hanger recycled as a car aerial.
			--- Douglas Adams, The Meaning of Liff

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

Hi Meenakshi,

On Fr, 13 Apr 2012, Venkataraman, Meenakshi wrote:
> In your logs I also see missed beacon notifications from the firmware ~every 500 milliseconds. My thought is that it is probably due to turning on power save. I'm not sure if it is affecting the performance of your system overall. Are you using the power save option? And if so, what is the behaviour when power save is turned off?

Good point. I have now changed iwlwifi to load with power_save=0
because as I found someone (don't ask me who!, nm? gnome? acpi?)
turns on power saving.

WIth that turned off I *believe* I have better results, but I will tet
it a bi tmore.

> I don't see the invalid station activation error in the log you sent me, so I'm guessing it appears only on the other network. Do send us logs for that. 

Now I got one ....
	http://www.logic.at/people/preining/syslog-debug.bz2
take care, unpacked it is big!

One more thing, I believe that this happens most of the times
(but not necessarily exclusively, but I don't have statistics)
after resume (from suspend to ram).

So saying, it seems that with power_save=0 even if I get several of
these:
[ 1601.552069] tx session timer expired on tid 0
[ 1601.552116] Tx BA session stop requested for 00:24:c4:ab:bd:e0 tid 0
[ 1601.576292] Stopping Tx BA session for 00:24:c4:ab:bd:e0 tid 0
[ 1603.470312] Open BA session requested for 00:24:c4:ab:bd:e0 tid 0
[ 1603.480274] activated addBA response timer on tid 0
[ 1603.483479] switched off addBA timer for tid 0
[ 1603.483485] Aggregation is on for tid 0
the connection does not break down, as before. Well, I am not sure whether
it is a consequence or coincidence.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
GWEEK (n.)
A coat hanger recycled as a car aerial.
			--- Douglas Adams, The Meaning of Liff

RE: 3.4-rc2, ilwagn still most of the time completely unusable

[Venkataraman, Meenakshi]

Hey Norbert,

>WIth that turned off I *believe* I have better results, but I will tet
>it a bi tmore.

[MV] How is this looking now?

>> I don't see the invalid station activation error in the log you sent me, so I'm
>guessing it appears only on the other network. Do send us logs for that.
>
>Now I got one ....
>	http://www.logic.at/people/preining/syslog-debug.bz2
>take care, unpacked it is big!

[MV]  I'm going through this log -- don't have a root cause for this yet, but getting closer to it. I see in this log that authentication is timing out. It appears that the driver sent out the authentication frame, and received some frame OTA, but I can't tell what it received from just the dmesg log. I'd like some trace-cmd logs from you. Is it possible for you to collect a trace-cmd log and send over the binary to me?

>One more thing, I believe that this happens most of the times
>(but not necessarily exclusively, but I don't have statistics)
>after resume (from suspend to ram).

[MV]  This is good to know. I wonder if this is related to the PCIe l used on your platform. Can you try to use PCIe link state management to L0s in your BIOS and see if the stability of your system improves?

>>So saying, it seems that with power_save=0 even if I get several of
>these:
>[ 1601.552069] tx session timer expired on tid 0
>[ 1601.552116] Tx BA session stop requested for 00:24:c4:ab:bd:e0 tid 0
>[ 1601.576292] Stopping Tx BA session for 00:24:c4:ab:bd:e0 tid 0
>[ 1603.470312] Open BA session requested for 00:24:c4:ab:bd:e0 tid 0
>[ 1603.480274] activated addBA response timer on tid 0
>[ 1603.483479] switched off addBA timer for tid 0
>[ 1603.483485] Aggregation is on for tid 0
>the connection does not break down, as before. Well, I am not sure whether
>it is a consequence or coincidence.

[MV] the tx session timer expiry ... hmm... I haven't looked at it. Otherwise, it seems to be Tx Aggregation sessions being turned on and turned off, so perhaps we will reduce the debug level at which it is printed. One of us is looking at the frequency with which these messages are being reported.

Thanks,
Meenakshi

RE: 3.4-rc2, ilwagn still most of the time completely unusable

[Venkataraman, Meenakshi]

Hey Norbert,

>WIth that turned off I *believe* I have better results, but I will tet
>it a bi tmore.

[MV] How is this looking now?

>> I don't see the invalid station activation error in the log you sent me, so I'm
>guessing it appears only on the other network. Do send us logs for that.
>
>Now I got one ....
>	http://www.logic.at/people/preining/syslog-debug.bz2
>take care, unpacked it is big!

[MV]  I'm going through this log -- don't have a root cause for this yet, but getting closer to it. I see in this log that authentication is timing out. It appears that the driver sent out the authentication frame, and received some frame OTA, but I can't tell what it received from just the dmesg log. I'd like some trace-cmd logs from you. Is it possible for you to collect a trace-cmd log and send over the binary to me?

>One more thing, I believe that this happens most of the times
>(but not necessarily exclusively, but I don't have statistics)
>after resume (from suspend to ram).

[MV]  This is good to know. I wonder if this is related to the PCIe l used on your platform. Can you try to use PCIe link state management to L0s in your BIOS and see if the stability of your system improves?

>>So saying, it seems that with power_save=0 even if I get several of
>these:
>[ 1601.552069] tx session timer expired on tid 0
>[ 1601.552116] Tx BA session stop requested for 00:24:c4:ab:bd:e0 tid 0
>[ 1601.576292] Stopping Tx BA session for 00:24:c4:ab:bd:e0 tid 0
>[ 1603.470312] Open BA session requested for 00:24:c4:ab:bd:e0 tid 0
>[ 1603.480274] activated addBA response timer on tid 0
>[ 1603.483479] switched off addBA timer for tid 0
>[ 1603.483485] Aggregation is on for tid 0
>the connection does not break down, as before. Well, I am not sure whether
>it is a consequence or coincidence.

[MV] the tx session timer expiry ... hmm... I haven't looked at it. Otherwise, it seems to be Tx Aggregation sessions being turned on and turned off, so perhaps we will reduce the debug level at which it is printed. One of us is looking at the frequency with which these messages are being reported.

Thanks,
Meenakshi

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

Hi Meenakshi,

On Mi, 25 Apr 2012, Venkataraman, Meenakshi wrote:
> >WIth that turned off I *believe* I have better results, but I will tet
> >it a bi tmore.
> 
> [MV] How is this looking now?

Definitely better. I still get occasional hickup but normally they
are just temporary, and no intervention is needed.

> [MV]  I'm going through this log -- don't have a root cause for this yet, but getting closer to it. I see in this log that authentication is timing out. It appears that the driver sent out the authentication frame, and received some frame OTA, but I can't tell what it received from just the dmesg log. I'd like some trace-cmd logs from you. Is it possible for you to collect a trace-cmd log and send over the binary to me?

WHat do you mean with trace-cmd? I don't have a "trace" utility installed,
only strace and ltrace AFAIR. And then, what should be traced?

> >One more thing, I believe that this happens most of the times
> >(but not necessarily exclusively, but I don't have statistics)
> >after resume (from suspend to ram).
> 
> [MV]  This is good to know. I wonder if this is related to the PCIe l used on your platform. Can you try to use PCIe link state management to L0s in your BIOS and see if the stability of your system improves?

This is a locked down bios from Sony, I can't get access to
these details, unfortunately.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
TIGHARRY (n.)
The accomplice or 'lure' who gets punters to participate in the three
card trick on London streets by winning an improbable amount of money
very easily.
			--- Douglas Adams, The Meaning of Liff

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

Hi Meenakshi,

On Mi, 25 Apr 2012, Venkataraman, Meenakshi wrote:
> >WIth that turned off I *believe* I have better results, but I will tet
> >it a bi tmore.
> 
> [MV] How is this looking now?

Definitely better. I still get occasional hickup but normally they
are just temporary, and no intervention is needed.

> [MV]  I'm going through this log -- don't have a root cause for this yet, but getting closer to it. I see in this log that authentication is timing out. It appears that the driver sent out the authentication frame, and received some frame OTA, but I can't tell what it received from just the dmesg log. I'd like some trace-cmd logs from you. Is it possible for you to collect a trace-cmd log and send over the binary to me?

WHat do you mean with trace-cmd? I don't have a "trace" utility installed,
only strace and ltrace AFAIR. And then, what should be traced?

> >One more thing, I believe that this happens most of the times
> >(but not necessarily exclusively, but I don't have statistics)
> >after resume (from suspend to ram).
> 
> [MV]  This is good to know. I wonder if this is related to the PCIe l used on your platform. Can you try to use PCIe link state management to L0s in your BIOS and see if the stability of your system improves?

This is a locked down bios from Sony, I can't get access to
these details, unfortunately.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
TIGHARRY (n.)
The accomplice or 'lure' who gets punters to participate in the three
card trick on London streets by winning an improbable amount of money
very easily.
			--- Douglas Adams, The Meaning of Liff

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

Hi everyone,

I am coming back to this old thread, not because it has been solved, 
but because today I got a funny new message while checking why 
everything got stuck again:
	[69588.972126] iwlwifi 0000:06:00.0: fail to flush all tx fifo queues
and after doing
	rfkill block wifi
	sleep 20
	rfkill unblock wifi
I got a kernel warning:
[76477.289251] WARNING: at net/mac80211/driver-ops.h:12 ieee80211_bss_info_change_notify+0x14e/0x1ca [mac80211]()
[76477.289256] Hardware name: VGN-Z11VN_B
[76477.289260] wlan0:  Failed check-sdata-in-driver check, flags: 0x0
[76477.289350] Modules linked in: dm_mod btusb iptable_filter bnep rfcomm bluetooth snd_hrtimer vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc isofs btrfs zlib_deflate libcrc32c vfat fat fuse loop uinput snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc hso arc4 snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi iwlwifi mac80211 snd_seq_midi_event cfg80211 snd_seq lpc_ich snd_seq_device snd_timer mxm_wmi mfd_core snd firewire_ohci firewire_core sony_laptop joydev crc_itu_t tpm_infineon rfkill soundcore
[76477.289361] Pid: 4278, comm: NetworkManager Tainted: P        W  O 3.5.0-rc4+ #78
[76477.289365] Call Trace:
[76477.289380]  [<ffffffff8102ba46>] warn_slowpath_common+0x83/0x9c
[76477.289389]  [<ffffffff8102bb02>] warn_slowpath_fmt+0x46/0x48
[76477.289402]  [<ffffffff813f21da>] ? neigh_ifdown+0xc5/0xd6
[76477.289424]  [<ffffffffa00b252e>] ieee80211_bss_info_change_notify+0x14e/0x1ca [mac80211]
[76477.289448]  [<ffffffffa00b267d>] ieee80211_ifa_changed+0xd3/0xe6 [mac80211]
[76477.289458]  [<ffffffff8104b7e3>] notifier_call_chain+0x37/0x61
[76477.289467]  [<ffffffff8104b919>] __blocking_notifier_call_chain+0x46/0x5f
[76477.289475]  [<ffffffff8104b946>] blocking_notifier_call_chain+0x14/0x16
[76477.289485]  [<ffffffff81432cc0>] __inet_del_ifa+0x176/0x22c
[76477.289494]  [<ffffffff81432f96>] inet_rtm_deladdr+0xe7/0x128
[76477.289504]  [<ffffffff813f61e0>] rtnetlink_rcv_msg+0x226/0x235
[76477.289513]  [<ffffffff8140460c>] ? netlink_sendmsg+0x124/0x20e
[76477.289520]  [<ffffffff813f5fba>] ? __rtnl_unlock+0x17/0x17
[76477.289528]  [<ffffffff814048b8>] netlink_rcv_skb+0x43/0x91
[76477.289536]  [<ffffffff813f415f>] rtnetlink_rcv+0x26/0x2d
[76477.289543]  [<ffffffff81404466>] netlink_unicast+0xe0/0x162
[76477.289551]  [<ffffffff814046d1>] netlink_sendmsg+0x1e9/0x20e
[76477.289562]  [<ffffffff813d7360>] __sock_sendmsg_nosec+0x61/0x6c
[76477.289570]  [<ffffffff813d774e>] sock_sendmsg+0xa1/0xb6
[76477.289582]  [<ffffffff813d96fb>] ? move_addr_to_kernel+0x49/0x67
[76477.289591]  [<ffffffff813e2605>] ? copy_from_user+0x9/0xb
[76477.289599]  [<ffffffff813e29e2>] ? verify_iovec+0x52/0xa4
[76477.289607]  [<ffffffff813d7a11>] __sys_sendmsg+0x206/0x293
[76477.289617]  [<ffffffff8108d48b>] ? __rcu_read_unlock+0xc/0x55
[76477.289627]  [<ffffffff810e69f5>] ? fput+0x16/0x1c7
[76477.289635]  [<ffffffff810e6888>] ? fget_light+0x92/0x9e
[76477.289643]  [<ffffffff813d77b3>] ? fput_light+0xd/0xf
[76477.289651]  [<ffffffff8108d48b>] ? __rcu_read_unlock+0xc/0x55
[76477.289659]  [<ffffffff810e6888>] ? fget_light+0x92/0x9e
[76477.289668]  [<ffffffff813da1ce>] sys_sendmsg+0x42/0x60
[76477.289678]  [<ffffffff81474b72>] system_call_fastpath+0x16/0x1b


Maybe this tells you something.

> > >	[ 9457.176828] iwlwifi 0000:06:00.0: ACTIVATE a non DRIVER active
> > >station id 0 addr 00:24:c4:ab:bd:e0

These messages now appear only now and then.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
The fronting for the eighty-yard long marble-topped bar
had been made by stitching together nearly twenty thousand
Antarean Mosaic Lizard skins, despite the fact that the
twenty thousand lizards concerned had needed them to keep
their insides in.
                 --- The Book decribing Milliways' politically incorrect
                 --- decor.
                 --- Douglas Adams, The Hitchhikers Guide to the Galaxy

Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

Hi everyone,

I am coming back to this old thread, not because it has been solved, 
but because today I got a funny new message while checking why 
everything got stuck again:
	[69588.972126] iwlwifi 0000:06:00.0: fail to flush all tx fifo queues
and after doing
	rfkill block wifi
	sleep 20
	rfkill unblock wifi
I got a kernel warning:
[76477.289251] WARNING: at net/mac80211/driver-ops.h:12 ieee80211_bss_info_change_notify+0x14e/0x1ca [mac80211]()
[76477.289256] Hardware name: VGN-Z11VN_B
[76477.289260] wlan0:  Failed check-sdata-in-driver check, flags: 0x0
[76477.289350] Modules linked in: dm_mod btusb iptable_filter bnep rfcomm bluetooth snd_hrtimer vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc isofs btrfs zlib_deflate libcrc32c vfat fat fuse loop uinput snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc hso arc4 snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi iwlwifi mac80211 snd_seq_midi_event cfg80211 snd_seq lpc_ich snd_seq_device snd_timer mxm_wmi mfd_core snd firewire_ohci firewire_core sony_laptop joydev crc_itu_t tpm_infineon rfkill soundcore
[76477.289361] Pid: 4278, comm: NetworkManager Tainted: P        W  O 3.5.0-rc4+ #78
[76477.289365] Call Trace:
[76477.289380]  [<ffffffff8102ba46>] warn_slowpath_common+0x83/0x9c
[76477.289389]  [<ffffffff8102bb02>] warn_slowpath_fmt+0x46/0x48
[76477.289402]  [<ffffffff813f21da>] ? neigh_ifdown+0xc5/0xd6
[76477.289424]  [<ffffffffa00b252e>] ieee80211_bss_info_change_notify+0x14e/0x1ca [mac80211]
[76477.289448]  [<ffffffffa00b267d>] ieee80211_ifa_changed+0xd3/0xe6 [mac80211]
[76477.289458]  [<ffffffff8104b7e3>] notifier_call_chain+0x37/0x61
[76477.289467]  [<ffffffff8104b919>] __blocking_notifier_call_chain+0x46/0x5f
[76477.289475]  [<ffffffff8104b946>] blocking_notifier_call_chain+0x14/0x16
[76477.289485]  [<ffffffff81432cc0>] __inet_del_ifa+0x176/0x22c
[76477.289494]  [<ffffffff81432f96>] inet_rtm_deladdr+0xe7/0x128
[76477.289504]  [<ffffffff813f61e0>] rtnetlink_rcv_msg+0x226/0x235
[76477.289513]  [<ffffffff8140460c>] ? netlink_sendmsg+0x124/0x20e
[76477.289520]  [<ffffffff813f5fba>] ? __rtnl_unlock+0x17/0x17
[76477.289528]  [<ffffffff814048b8>] netlink_rcv_skb+0x43/0x91
[76477.289536]  [<ffffffff813f415f>] rtnetlink_rcv+0x26/0x2d
[76477.289543]  [<ffffffff81404466>] netlink_unicast+0xe0/0x162
[76477.289551]  [<ffffffff814046d1>] netlink_sendmsg+0x1e9/0x20e
[76477.289562]  [<ffffffff813d7360>] __sock_sendmsg_nosec+0x61/0x6c
[76477.289570]  [<ffffffff813d774e>] sock_sendmsg+0xa1/0xb6
[76477.289582]  [<ffffffff813d96fb>] ? move_addr_to_kernel+0x49/0x67
[76477.289591]  [<ffffffff813e2605>] ? copy_from_user+0x9/0xb
[76477.289599]  [<ffffffff813e29e2>] ? verify_iovec+0x52/0xa4
[76477.289607]  [<ffffffff813d7a11>] __sys_sendmsg+0x206/0x293
[76477.289617]  [<ffffffff8108d48b>] ? __rcu_read_unlock+0xc/0x55
[76477.289627]  [<ffffffff810e69f5>] ? fput+0x16/0x1c7
[76477.289635]  [<ffffffff810e6888>] ? fget_light+0x92/0x9e
[76477.289643]  [<ffffffff813d77b3>] ? fput_light+0xd/0xf
[76477.289651]  [<ffffffff8108d48b>] ? __rcu_read_unlock+0xc/0x55
[76477.289659]  [<ffffffff810e6888>] ? fget_light+0x92/0x9e
[76477.289668]  [<ffffffff813da1ce>] sys_sendmsg+0x42/0x60
[76477.289678]  [<ffffffff81474b72>] system_call_fastpath+0x16/0x1b


Maybe this tells you something.

> > >	[ 9457.176828] iwlwifi 0000:06:00.0: ACTIVATE a non DRIVER active
> > >station id 0 addr 00:24:c4:ab:bd:e0

These messages now appear only now and then.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
The fronting for the eighty-yard long marble-topped bar
had been made by stitching together nearly twenty thousand
Antarean Mosaic Lizard skins, despite the fact that the
twenty thousand lizards concerned had needed them to keep
their insides in.
                 --- The Book decribing Milliways' politically incorrect
                 --- decor.
                 --- Douglas Adams, The Hitchhikers Guide to the Galaxy

Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Johannes Berg]

Hi Norbert,

> I am coming back to this old thread, not because it has been solved,

Somehow your mail didn't make it to the lists, not sure why.

> but because today I got a funny new message while checking why
> everything got stuck again:
>         [69588.972126] iwlwifi 0000:06:00.0: fail to flush all tx fifo queues
> and after doing
>         rfkill block wifi
>         sleep 20
>         rfkill unblock wifi
> I got a kernel warning:
> [76477.289251] WARNING: at net/mac80211/driver-ops.h:12 ieee80211_bss_info_change_notify+0x14e/0x1ca [mac80211]()
> [76477.289256] Hardware name: VGN-Z11VN_B
> [76477.289260] wlan0:  Failed check-sdata-in-driver check, flags: 0x0
> [76477.289350] Modules linked in: ...
> [76477.289361] Pid: 4278, comm: NetworkManager Tainted: P        W  O 3.5.0-rc4+ #78
> [76477.289365] Call Trace:
> [76477.289380]  [<ffffffff8102ba46>] warn_slowpath_common+0x83/0x9c
> [76477.289389]  [<ffffffff8102bb02>] warn_slowpath_fmt+0x46/0x48
> [76477.289402]  [<ffffffff813f21da>] ? neigh_ifdown+0xc5/0xd6
> [76477.289424]  [<ffffffffa00b252e>] ieee80211_bss_info_change_notify+0x14e/0x1ca [mac80211]
> [76477.289448]  [<ffffffffa00b267d>] ieee80211_ifa_changed+0xd3/0xe6 [mac80211]
> [76477.289458]  [<ffffffff8104b7e3>] notifier_call_chain+0x37/0x61
> [76477.289467]  [<ffffffff8104b919>] __blocking_notifier_call_chain+0x46/0x5f
> [76477.289475]  [<ffffffff8104b946>] blocking_notifier_call_chain+0x14/0x16
> [76477.289485]  [<ffffffff81432cc0>] __inet_del_ifa+0x176/0x22c
> [76477.289494]  [<ffffffff81432f96>] inet_rtm_deladdr+0xe7/0x128
> [76477.289504]  [<ffffffff813f61e0>] rtnetlink_rcv_msg+0x226/0x235

Fun. I don't actually see how this can possibly happen though?!


> Maybe this tells you something.
> 
> > > >   [ 9457.176828] iwlwifi 0000:06:00.0: ACTIVATE a non DRIVER active
> > > >station id 0 addr 00:24:c4:ab:bd:e0
> 
> These messages now appear only now and then.

I fixed those recently.

You seem to be on 3.5.0-rc now, is that really no different from 3.4?

johannes

Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Johannes Berg]

Hi Norbert,

> I am coming back to this old thread, not because it has been solved,

Somehow your mail didn't make it to the lists, not sure why.

> but because today I got a funny new message while checking why
> everything got stuck again:
>         [69588.972126] iwlwifi 0000:06:00.0: fail to flush all tx fifo queues
> and after doing
>         rfkill block wifi
>         sleep 20
>         rfkill unblock wifi
> I got a kernel warning:
> [76477.289251] WARNING: at net/mac80211/driver-ops.h:12 ieee80211_bss_info_change_notify+0x14e/0x1ca [mac80211]()
> [76477.289256] Hardware name: VGN-Z11VN_B
> [76477.289260] wlan0:  Failed check-sdata-in-driver check, flags: 0x0
> [76477.289350] Modules linked in: ...
> [76477.289361] Pid: 4278, comm: NetworkManager Tainted: P        W  O 3.5.0-rc4+ #78
> [76477.289365] Call Trace:
> [76477.289380]  [<ffffffff8102ba46>] warn_slowpath_common+0x83/0x9c
> [76477.289389]  [<ffffffff8102bb02>] warn_slowpath_fmt+0x46/0x48
> [76477.289402]  [<ffffffff813f21da>] ? neigh_ifdown+0xc5/0xd6
> [76477.289424]  [<ffffffffa00b252e>] ieee80211_bss_info_change_notify+0x14e/0x1ca [mac80211]
> [76477.289448]  [<ffffffffa00b267d>] ieee80211_ifa_changed+0xd3/0xe6 [mac80211]
> [76477.289458]  [<ffffffff8104b7e3>] notifier_call_chain+0x37/0x61
> [76477.289467]  [<ffffffff8104b919>] __blocking_notifier_call_chain+0x46/0x5f
> [76477.289475]  [<ffffffff8104b946>] blocking_notifier_call_chain+0x14/0x16
> [76477.289485]  [<ffffffff81432cc0>] __inet_del_ifa+0x176/0x22c
> [76477.289494]  [<ffffffff81432f96>] inet_rtm_deladdr+0xe7/0x128
> [76477.289504]  [<ffffffff813f61e0>] rtnetlink_rcv_msg+0x226/0x235

Fun. I don't actually see how this can possibly happen though?!


> Maybe this tells you something.
> 
> > > >   [ 9457.176828] iwlwifi 0000:06:00.0: ACTIVATE a non DRIVER active
> > > >station id 0 addr 00:24:c4:ab:bd:e0
> 
> These messages now appear only now and then.

I fixed those recently.

You seem to be on 3.5.0-rc now, is that really no different from 3.4?

johannes

Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

On Do, 28 Jun 2012, Johannes Berg wrote:
> Somehow your mail didn't make it to the lists, not sure why.

Hmm, yeah, some of the emails were privte exchange with 
Venkataraman and Lin.

> Fun. I don't actually see how this can possibly happen though?!

Hmm, actually I think I have seen similar things quite regularly,
and reported them also.

> > > > >   [ 9457.176828] iwlwifi 0000:06:00.0: ACTIVATE a non DRIVER active
> > > > >station id 0 addr 00:24:c4:ab:bd:e0
> > 
> > These messages now appear only now and then.
> 
> I fixed those recently.

Good.

> You seem to be on 3.5.0-rc now, is that really no different from 3.4?

The feeling is that it is definitely better.

I can actually work now wirelessly, and in case of hangs an rfkill block
rfkill unblock practically always, and mostly is not needed.

So yes, it is better, definitely.

I think till 3.4 I had to use the cable quite regularly.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
JAWCRAIG (n. medical)
A massive facial spasm which is brought on by being told a really
astounding piece of news. A mysterious attack of jawcraig affected
40,000 sheep in Whales in 1952.
			--- Douglas Adams, The Meaning of Liff

Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Alessandro Suardi]

On Thu, Jun 28, 2012 at 10:16 AM, Norbert Preining <preining@logic.at> wrote:
> On Do, 28 Jun 2012, Johannes Berg wrote:
>> Somehow your mail didn't make it to the lists, not sure why.
>
> Hmm, yeah, some of the emails were privte exchange with
> Venkataraman and Lin.
>
>> Fun. I don't actually see how this can possibly happen though?!
>
> Hmm, actually I think I have seen similar things quite regularly,
> and reported them also.
>
>> > > > >   [ 9457.176828] iwlwifi 0000:06:00.0: ACTIVATE a non DRIVER active
>> > > > >station id 0 addr 00:24:c4:ab:bd:e0
>> >
>> > These messages now appear only now and then.
>>
>> I fixed those recently.
>
> Good.

Just a report to say that I still see those in 3.5.0-rc5.

I recently moved from a Dell Latitude 6400, with a bcm4322 chip managed
 by the Broadcom-STA out-of-tree driver (wl module) to the new Latitude 6420,
 which has this as per lspci:

02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 (rev 34)

 and I have two issues compared to the bcm4322; one is the above message,
 which appears when the driver can't associate to my D-Link DSL2740B router;
 telnetting into the router and bouncing its AP component via wlctl is enough
 to allow the laptop to connect again.
At the same time, my wife's old 32-bit Dell D610 with an ipw2200 connects just
 fine to the DSL-2740B.


The second issue is that the wifi speed is much lower with the new 6420 under
 iwlwifi - topping out at under 3MB/s compared with peaks of 10MB/s with the
 bcm4322's wl driver, which hardly ever went under 6MB/s.

iwconfig wlan0 reports fluctuating bitrates of 18/24/36 Mb/s whereas I could see
 very easily 130Mb/s with the wl driver. Maybe something is also due to the fact
 that the DSL-2740B has a draft-N implementation and its Broadcom chip has
 better feelings with the laptop's Broadcom wl than the iwlwifi.


I'm available for more detailed reporting and testing.

Thanks,

>> You seem to be on 3.5.0-rc now, is that really no different from 3.4?
>
> The feeling is that it is definitely better.
>
> I can actually work now wirelessly, and in case of hangs an rfkill block
> rfkill unblock practically always, and mostly is not needed.
>
> So yes, it is better, definitely.
>
> I think till 3.4 I had to use the cable quite regularly.
>
> Best wishes
>
> Norbert

--alessandro

"don't underestimate the things that I will do"

 (Adele, "Rolling In The Deep")

Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

In preach for decent iwl driver ...

On Do, 28 Jun 2012, Norbert Preining wrote:
> > You seem to be on 3.5.0-rc now, is that really no different from 3.4?
> 
> The feeling is that it is definitely better.
> 
> I can actually work now wirelessly, and in case of hangs an rfkill block
> rfkill unblock practically always, and mostly is not needed.

Ok, that was said *UNTIL* I reenabled 11n. Up to now I was loading the
iwlwifi module with
	11n_disable=1

Now, latest git from today, I though, let us try to enable 11n again,
and there we go, boot from cold machine and after short time everything
is dead without reaction. Dmesg gives many many funny messages:

[   30.047943] iwlwifi 0000:06:00.0: L1 Enabled; Disabling L0S
[   30.051933] iwlwifi 0000:06:00.0: Radio type=0x1-0x2-0x0
[   30.164836] iwlwifi 0000:06:00.0: L1 Enabled; Disabling L0S
[   30.167876] iwlwifi 0000:06:00.0: Radio type=0x1-0x2-0x0
[   37.533619] wlan0: authenticate with 00:0a:79:eb:56:10
[   37.536433] wlan0: send auth to 00:0a:79:eb:56:10 (try 1/3)
[   37.538241] wlan0: authenticated
[   37.538391] wlan0: associating with AP with corrupt beacon
[   37.540056] wlan0: associate with 00:0a:79:eb:56:10 (try 1/3)
[   37.543844] wlan0: RX AssocResp from 00:0a:79:eb:56:10 (capab=0x411 status=0 aid=3)
[   37.543848] wlan0: associated
[   37.547219] cfg80211: Calling CRDA for country: JP
[   37.551474] cfg80211: Regulatory domain changed to country: JP
[   37.551477] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   37.551479] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[   37.551481] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (N/A, 2000 mBm)
[   37.551483] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
[   37.551485] cfg80211:   (4910000 KHz - 4930000 KHz @ 10000 KHz), (N/A, 2300 mBm)
[   37.551486] cfg80211:   (4910000 KHz - 4990000 KHz @ 40000 KHz), (N/A, 2300 mBm)
[   37.551488] cfg80211:   (4930000 KHz - 4950000 KHz @ 10000 KHz), (N/A, 2300 mBm)
[   37.551490] cfg80211:   (5030000 KHz - 5045000 KHz @ 10000 KHz), (N/A, 2300 mBm)
[   37.551492] cfg80211:   (5030000 KHz - 5090000 KHz @ 40000 KHz), (N/A, 2300 mBm)
[   37.551494] cfg80211:   (5050000 KHz - 5060000 KHz @ 10000 KHz), (N/A, 2300 mBm)
[   37.551495] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[   37.551497] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[   37.551499] cfg80211:   (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2300 mBm)
[   39.526929] Rx A-MPDU request on tid 0 result 0
[   46.907606] type=1305 audit(1342079160.633:43563): auid=4294967295 ses=4294967295 op="remove rule" key=(null) list=4 res=1
[   46.907619] type=1305 audit(1342079160.633:43564): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 res=1
[   49.372661] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[   49.392528] activated addBA response timer on tid 0
[   49.394760] switched off addBA timer for tid 0
[   49.394769] Aggregation is on for tid 0
[   52.416068] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
[   52.416081] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
[   52.416089] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
[   52.416096] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
[   52.416103] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
[   52.416110] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
[   52.416117] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
[   52.416124] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
[   52.416131] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
[   52.416138] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
[   69.252057] tx session timer expired on tid 0
[   69.252125] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[   69.272673] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[   99.933558] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[   99.952530] activated addBA response timer on tid 0
[   99.954667] switched off addBA timer for tid 0
[   99.954676] Aggregation is on for tid 0
[  115.075768] net_ratelimit: 25 callbacks suppressed
[  115.075783] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[  122.721571] Rx A-MPDU request on tid 0 result 0
[  132.008042] tx session timer expired on tid 0
[  132.008099] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  132.028663] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  150.396166] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  150.416568] activated addBA response timer on tid 0
[  150.418855] switched off addBA timer for tid 0
[  150.418864] Aggregation is on for tid 0
[  155.648232] tx session timer expired on tid 0
[  155.648344] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  155.712077] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  174.770400] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  174.788589] activated addBA response timer on tid 0
[  174.790924] switched off addBA timer for tid 0
[  174.790933] Aggregation is on for tid 0
[  179.952240] tx session timer expired on tid 0
[  179.952309] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  179.988674] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  190.379820] Monitor-Mwait will be used to enter C-2 state
[  190.464417] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[  194.899310] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[  198.557158] Rx A-MPDU request on tid 0 result 0
[  199.857800] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  199.876203] activated addBA response timer on tid 0
[  199.878134] switched off addBA timer for tid 0
[  199.878137] Aggregation is on for tid 0
[  205.012031] tx session timer expired on tid 0
[  205.012059] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  205.028154] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  231.043030] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  231.068189] activated addBA response timer on tid 0
[  232.068013] addBA response timer expired on tid 0
[  232.070445] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  232.172044] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
[  236.076079] switched off addBA timer for tid 0
[  236.076083] got addBA resp for tid 0 but we already gave up
[  236.076108] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[  236.077505] Rx A-MPDU request on tid 0 result 0
[  236.077522] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  236.085520] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  236.100112] activated addBA response timer on tid 0
[  236.101931] switched off addBA timer for tid 0
[  236.101934] Aggregation is on for tid 0
[  250.832035] tx session timer expired on tid 0
[  250.832062] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  250.848187] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  256.749542] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  256.768199] activated addBA response timer on tid 0
[  256.770132] switched off addBA timer for tid 0
[  256.770134] Aggregation is on for tid 0
[  267.328057] tx session timer expired on tid 0
[  267.328076] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  267.344218] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  269.719144] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  269.732239] activated addBA response timer on tid 0
[  269.734184] switched off addBA timer for tid 0
[  269.734186] Aggregation is on for tid 0
[  274.936071] tx session timer expired on tid 0
[  274.936105] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  274.952285] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  278.160167] usb 8-2: USB disconnect, device number 2
[  281.245767] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  281.256213] activated addBA response timer on tid 0
[  281.258078] switched off addBA timer for tid 0
[  281.258081] Aggregation is on for tid 0
[  320.855956] Open BA session requested for 00:0a:79:eb:56:10 tid 6
[  320.880286] activated addBA response timer on tid 6
[  320.882267] switched off addBA timer for tid 6
[  320.882272] Aggregation is on for tid 6
[  322.428079] tx session timer expired on tid 0
[  322.428090] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  322.452276] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  332.088032] tx session timer expired on tid 6
[  332.088085] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 6
[  335.900144] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 6
[  350.580037] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  350.592129] activated addBA response timer on tid 0
[  350.593928] switched off addBA timer for tid 0
[  350.593930] Aggregation is on for tid 0
[  364.040010] tx session timer expired on tid 0
[  364.040034] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  364.060167] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  391.857778] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  391.876229] activated addBA response timer on tid 0
[  391.878181] switched off addBA timer for tid 0
[  391.878188] Aggregation is on for tid 0
[  397.100028] tx session timer expired on tid 0
[  397.100052] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  397.124294] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  447.952847] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  447.968288] activated addBA response timer on tid 0
[  447.970265] switched off addBA timer for tid 0
[  447.970271] Aggregation is on for tid 0
[  453.116013] tx session timer expired on tid 0
[  453.116042] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  455.904124] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  469.983154] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  470.004246] activated addBA response timer on tid 0
[  470.006181] switched off addBA timer for tid 0
[  470.006186] Aggregation is on for tid 0
[  475.320065] tx session timer expired on tid 0
[  475.320103] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  475.352211] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  525.855950] Open BA session requested for 00:0a:79:eb:56:10 tid 6
[  525.872237] activated addBA response timer on tid 6
[  525.874154] switched off addBA timer for tid 6
[  525.874160] Aggregation is on for tid 6
[  531.008066] tx session timer expired on tid 6
[  531.008101] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 6
[  531.036289] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 6
[  591.614347] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  591.628233] activated addBA response timer on tid 0
[  591.630127] switched off addBA timer for tid 0
[  591.630132] Aggregation is on for tid 0
[  675.970533] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[  676.123652] Rx A-MPDU request on tid 0 result 0
[  678.176189] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[  678.219031] Rx A-MPDU request on tid 0 result 0
[  678.240242] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[  683.166179] Rx A-MPDU request on tid 0 result 0
[  688.800013] tx session timer expired on tid 0
[  688.800036] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  688.820256] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  715.753804] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  715.784268] activated addBA response timer on tid 0
[  715.786266] switched off addBA timer for tid 0
[  715.786272] Aggregation is on for tid 0
[  728.776062] tx session timer expired on tid 0
[  728.776091] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  728.796221] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  737.754033] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  737.776299] activated addBA response timer on tid 0
[  737.778264] switched off addBA timer for tid 0
[  737.778270] Aggregation is on for tid 0
[  758.980031] tx session timer expired on tid 0
[  758.980082] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  759.016307] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  788.578489] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  788.600254] activated addBA response timer on tid 0
[  788.602218] switched off addBA timer for tid 0
[  788.602224] Aggregation is on for tid 0
[  803.504097] tx session timer expired on tid 0
[  803.504138] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  803.524276] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  824.510495] Open BA session requested for 00:0a:79:eb:56:10 tid 6
[  824.528269] activated addBA response timer on tid 6
[  824.530247] switched off addBA timer for tid 6
[  824.530253] Aggregation is on for tid 6
[  829.712080] tx session timer expired on tid 6
[  829.712129] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 6
[  829.728181] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 6
[  858.453300] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  858.472261] activated addBA response timer on tid 0
[  858.474165] switched off addBA timer for tid 0
[  858.474172] Aggregation is on for tid 0
[  863.688071] tx session timer expired on tid 0
[  863.688121] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  863.708290] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  903.634792] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  903.664267] activated addBA response timer on tid 0
[  903.666272] switched off addBA timer for tid 0
[  903.666279] Aggregation is on for tid 0
[  911.992023] tx session timer expired on tid 0
[  911.992057] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  912.012298] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  931.478394] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  931.496346] activated addBA response timer on tid 0
[  932.496100] addBA response timer expired on tid 0
[  932.496149] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  935.892151] switched off addBA timer for tid 0
[  935.892160] got addBA resp for tid 0 but we already gave up
[  935.892207] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  935.902372] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  935.912202] activated addBA response timer on tid 0
[  935.914010] switched off addBA timer for tid 0
[  935.914012] Aggregation is on for tid 0
[  946.972030] tx session timer expired on tid 0
[  946.972079] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  946.996293] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  957.025964] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  957.056276] activated addBA response timer on tid 0
[  957.058143] switched off addBA timer for tid 0
[  957.058149] Aggregation is on for tid 0
[  967.472028] tx session timer expired on tid 0
[  967.472069] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[  967.508296] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[  996.664073] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[  996.672202] activated addBA response timer on tid 0
[  996.674167] switched off addBA timer for tid 0
[  996.674173] Aggregation is on for tid 0
[ 1002.008033] tx session timer expired on tid 0
[ 1002.008076] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[ 1002.028299] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[ 1051.699694] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[ 1051.732280] activated addBA response timer on tid 0
[ 1052.732077] addBA response timer expired on tid 0
[ 1052.732105] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[ 1055.908118] switched off addBA timer for tid 0
[ 1055.908126] got addBA resp for tid 0 but we already gave up
[ 1055.908173] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[ 1068.701488] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[ 1068.732250] activated addBA response timer on tid 0
[ 1068.734110] switched off addBA timer for tid 0
[ 1068.734116] Aggregation is on for tid 0
[ 1079.024062] tx session timer expired on tid 0
[ 1079.024109] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[ 1079.056276] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[ 1116.716696] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[ 1116.736346] activated addBA response timer on tid 0
[ 1116.738258] switched off addBA timer for tid 0
[ 1116.738265] Aggregation is on for tid 0
[ 1121.908042] tx session timer expired on tid 0
[ 1121.908084] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[ 1121.920195] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[ 1130.839113] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[ 1130.856186] activated addBA response timer on tid 0
[ 1130.858090] switched off addBA timer for tid 0
[ 1130.858092] Aggregation is on for tid 0
[ 1137.504065] tx session timer expired on tid 0
[ 1137.504094] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[ 1137.528217] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[ 1188.853434] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[ 1188.868312] activated addBA response timer on tid 0
[ 1188.870219] switched off addBA timer for tid 0
[ 1188.870225] Aggregation is on for tid 0
[ 1202.572069] tx session timer expired on tid 0
[ 1202.572112] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[ 1202.588311] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[ 1205.842236] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[ 1205.860248] activated addBA response timer on tid 0
[ 1205.862276] switched off addBA timer for tid 0
[ 1205.862281] Aggregation is on for tid 0
[ 1219.611200] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1219.640915] Rx A-MPDU request on tid 0 result 0
[ 1219.652704] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1219.668255] Rx A-MPDU request on tid 0 result 0
[ 1220.183679] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1220.192230] Rx A-MPDU request on tid 0 result 0
[ 1220.633590] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1220.787950] Rx A-MPDU request on tid 0 result 0
[ 1228.728530] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1228.809410] Rx A-MPDU request on tid 0 result 0
[ 1228.852826] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1229.085139] Rx A-MPDU request on tid 0 result 0
[ 1230.503937] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1230.745132] Rx A-MPDU request on tid 0 result 0
[ 1250.604674] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1251.863016] Rx A-MPDU request on tid 0 result 0
[ 1251.947364] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1252.290963] Rx A-MPDU request on tid 0 result 0
[ 1252.329981] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1253.455024] Rx A-MPDU request on tid 0 result 0
[ 1253.935912] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1255.279219] Rx A-MPDU request on tid 0 result 0
[ 1255.448164] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1256.083286] Rx A-MPDU request on tid 0 result 0
[ 1256.307717] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1256.763290] Rx A-MPDU request on tid 0 result 0
[ 1257.059071] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1257.267242] Rx A-MPDU request on tid 0 result 0
[ 1257.916762] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1258.235389] Rx A-MPDU request on tid 0 result 0
[ 1258.421010] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1260.151685] Rx A-MPDU request on tid 0 result 0
[ 1261.537236] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1265.396031] tx session timer expired on tid 0
[ 1265.396091] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[ 1265.420304] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[ 1267.540420] Rx A-MPDU request on tid 0 result 0
[ 1268.112599] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1269.888616] Rx A-MPDU request on tid 0 result 0
[ 1271.879324] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1272.472915] Rx A-MPDU request on tid 0 result 0
[ 1272.834556] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1278.962095] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[ 1278.992238] activated addBA response timer on tid 0
[ 1278.994465] switched off addBA timer for tid 0
[ 1278.994471] Aggregation is on for tid 0
[ 1284.128028] tx session timer expired on tid 0
[ 1284.128081] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[ 1284.136166] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[ 1291.113670] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[ 1291.128236] activated addBA response timer on tid 0
[ 1292.128061] addBA response timer expired on tid 0
[ 1292.128090] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
[ 1295.952061] switched off addBA timer for tid 0
[ 1295.952069] got addBA resp for tid 0 but we already gave up
[ 1295.952139] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
[ 1301.997218] Rx A-MPDU request on tid 0 result 0
[ 1302.311441] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1302.695714] Open BA session requested for 00:0a:79:eb:56:10 tid 0
[ 1302.712940] activated addBA response timer on tid 0
[ 1302.714749] switched off addBA timer for tid 0
[ 1302.714751] Aggregation is on for tid 0
[ 1302.868055] Rx A-MPDU request on tid 0 result 0
[ 1305.905814] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1306.304384] Rx A-MPDU request on tid 0 result 0
[ 1308.044965] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1309.005987] Rx A-MPDU request on tid 0 result 0
[ 1309.138988] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1310.512800] Rx A-MPDU request on tid 0 result 0
[ 1311.568780] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1312.180963] Rx A-MPDU request on tid 0 result 0
[ 1312.595070] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1314.345134] Rx A-MPDU request on tid 0 result 0
[ 1314.871701] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1315.317486] Rx A-MPDU request on tid 0 result 0
[ 1315.455485] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1315.617855] Rx A-MPDU request on tid 0 result 0
[ 1315.759023] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1315.913446] Rx A-MPDU request on tid 0 result 0
[ 1316.051602] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1316.105381] Rx A-MPDU request on tid 0 result 0
[ 1316.246593] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1316.453412] Rx A-MPDU request on tid 0 result 0
[ 1316.645651] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1316.765334] Rx A-MPDU request on tid 0 result 0
[ 1316.879960] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1317.341497] Rx A-MPDU request on tid 0 result 0
[ 1317.698354] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1318.137662] Rx A-MPDU request on tid 0 result 0
[ 1318.282442] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1318.337572] Rx A-MPDU request on tid 0 result 0
[ 1318.602768] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1318.689813] Rx A-MPDU request on tid 0 result 0
[ 1318.829183] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1318.885552] Rx A-MPDU request on tid 0 result 0
[ 1318.897440] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1318.998340] Rx A-MPDU request on tid 0 result 0
[ 1319.849545] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 recipient reason: 32
[ 1319.849820] Rx A-MPDU request on tid 0 result 0
[ 1320.024218] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1321.285843] Rx A-MPDU request on tid 0 result 0
[ 1321.354509] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1321.813911] Rx A-MPDU request on tid 0 result 0
[ 1321.958338] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1324.502158] Rx A-MPDU request on tid 0 result 0
[ 1324.781588] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1327.882374] Rx A-MPDU request on tid 0 result 0
[ 1328.851063] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1334.359659] Rx A-MPDU request on tid 0 result 0
[ 1334.442784] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 recipient reason: 32
[ 1334.443055] Rx A-MPDU request on tid 0 result 0
[ 1335.236228] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1336.279440] Rx A-MPDU request on tid 0 result 0
[ 1337.359458] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1338.787441] Rx A-MPDU request on tid 0 result 0
[ 1338.902301] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1338.951462] Rx A-MPDU request on tid 0 result 0
[ 1339.114149] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1339.143323] Rx A-MPDU request on tid 0 result 0
[ 1339.614671] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1339.888483] Rx A-MPDU request on tid 0 result 0
[ 1340.520279] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1341.028517] Rx A-MPDU request on tid 0 result 0
[ 1341.282571] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1341.588025] Rx A-MPDU request on tid 0 result 0
[ 1341.794666] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1342.039485] Rx A-MPDU request on tid 0 result 0
[ 1342.620671] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1343.067653] Rx A-MPDU request on tid 0 result 0
[ 1343.072591] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1343.455750] Rx A-MPDU request on tid 0 result 0
[ 1343.461169] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1344.015842] Rx A-MPDU request on tid 0 result 0
[ 1344.020901] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1344.035804] Rx A-MPDU request on tid 0 result 0
[ 1344.046268] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1344.497040] Rx A-MPDU request on tid 0 result 0
[ 1344.501908] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1346.240193] Rx A-MPDU request on tid 0 result 0
[ 1346.292049] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1348.252199] Rx A-MPDU request on tid 0 result 0
[ 1348.382382] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1348.508178] Rx A-MPDU request on tid 0 result 0
[ 1348.769494] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1348.788090] Rx A-MPDU request on tid 0 result 0
[ 1348.938350] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1349.105715] Rx A-MPDU request on tid 0 result 0
[ 1349.169052] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1349.692245] Rx A-MPDU request on tid 0 result 0
[ 1351.188910] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
[ 1351.392419] Rx A-MPDU request on tid 0 result 0
[ 1354.645239] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0

At that point I removed the iwlwifi module, and reloaded it with 
11n_disable=1 again, otherwise nothing would work at all...

It is a pity that this is a problem now since 2.6.38 when I reported it
the first time as far as I remember, it is such a long time ...

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
CONDOVER (n.)
One who is employed to stand about all day browsing through the
magazine racks in the newsagent.
			--- Douglas Adams, The Meaning of Liff

Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Johannes Berg]

On Thu, 2012-07-12 at 17:14 +0900, Norbert Preining wrote:

> > I can actually work now wirelessly, and in case of hangs an rfkill block
> > rfkill unblock practically always, and mostly is not needed.
> 
> Ok, that was said *UNTIL* I reenabled 11n. Up to now I was loading the
> iwlwifi module with
> 	11n_disable=1
> 
> Now, latest git from today, I though, let us try to enable 11n again,
> and there we go, boot from cold machine and after short time everything
> is dead without reaction. Dmesg gives many many funny messages:
> 
> [   30.047943] iwlwifi 0000:06:00.0: L1 Enabled; Disabling L0S
> [   30.051933] iwlwifi 0000:06:00.0: Radio type=0x1-0x2-0x0
> [   30.164836] iwlwifi 0000:06:00.0: L1 Enabled; Disabling L0S
> [   30.167876] iwlwifi 0000:06:00.0: Radio type=0x1-0x2-0x0
> [   37.533619] wlan0: authenticate with 00:0a:79:eb:56:10
> [   37.536433] wlan0: send auth to 00:0a:79:eb:56:10 (try 1/3)
> [   37.538241] wlan0: authenticated
> [   37.538391] wlan0: associating with AP with corrupt beacon

That might be an indication of things already going wrong with your
AP ... :-(

[snip log]

Mostly from the log it seems that there's a lot of spurious aggregation
setup/teardown, some of it seems to originate from the AP.

> At that point I removed the iwlwifi module, and reloaded it with 
> 11n_disable=1 again, otherwise nothing would work at all...

With the latest, I've extended 11n_disable to have more bits.

11n_disable=1 will disable HT completely
11n_disable=2 will disable TX aggregation
11n_disable=4 will disable RX aggregation

It'd be interesting to see what happens for you with 11n_disable=2/4/6.

johannes

Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable

[Norbert Preining]

Hi Johannes,

Sorry for the late reply, I was travelling around the world ...
I have now tested the =2 and =4 settings at home, with the following
outcome:

On Do, 12 Jul 2012, Johannes Berg wrote:
> With the latest, I've extended 11n_disable to have more bits.
> 
> 11n_disable=1 will disable HT completely
> 11n_disable=2 will disable TX aggregation
> 11n_disable=4 will disable RX aggregation

11n_disabled=2:
lots of messages
  Open BA session requested for 00:0a:79:eb:56:10 tid 0
  BA request denied - HW unavailable for tid 0
and
  Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
  Rx A-MPDU request on tid 0 result 0

Connection is stable for quite some time, but after 1-2 hours I got
a bad hang, grinding to a halt. pings to kernel.org gives 26% 
packet loss, but the rest of the packets are fast 130ms 

(Isn't that a strange thing - 25+% packet loss and all others are fast?)
I assume the packaet loss is related to the above messages.


11n_disabled=4:

lots of messages
  Rx A-MPDU request on tid 0 result -22
and at some point ping timeouts of 80+ secs (!) and then total hang
(as far as I remember)

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
PERRANZABULOE (n.)
One of those spray things used to wet ironing with.
			--- Douglas Adams, The Meaning of Liff