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:	Fri, 13 Apr 2012 14:38:58 +0900
From:	Norbert Preining <preining@...ic.at>
To:	"Venkataraman, Meenakshi" <meenakshi.venkataraman@...el.com>
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 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@...ist.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
--
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/