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]

Date:	Wed, 11 Apr 2012 23:24:31 +0000
From:	"Venkataraman, Meenakshi" <meenakshi.venkataraman@...el.com>
To:	Norbert Preining <preining@...ic.at>,
	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,

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

--
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/