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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4595B4D22AB93C4FABBA84AAD5AA37FD120BF8@ORSMSX103.amr.corp.intel.com>
Date:	Fri, 13 Apr 2012 01:32:38 +0000
From:	"Venkataraman, Meenakshi" <meenakshi.venkataraman@...el.com>
To:	Norbert Preining <preining@...ic.at>
CC:	Emmanuel Grumbach <egrumbach@...il.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"ipw3945-devel@...ts.sourceforge.net" 
	<ipw3945-devel@...ts.sourceforge.net>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>
Subject: RE: 3.4-rc2, ilwagn still most of the time completely unusable

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/