linux-kernel - Re: iwlagn is getting very shaky

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 28 Nov 2011 08:33:23 +0200
From:	Emmanuel Grumbach <egrumbach@...il.com>
To:	Norbert Preining <preining@...ic.at>
Cc:	"Guy, Wey-Yi" <wey-yi.w.guy@...el.com>,
	Pekka Enberg <penberg@...helsinki.fi>,
	"ipw3945-devel@...ts.sourceforge.net" 
	<ipw3945-devel@...ts.sourceforge.net>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Johannes Berg <johannes@...solutions.net>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>,
	Dave Jones <davej@...hat.com>,
	David Rientjes <rientjes@...gle.com>
Subject: Re: iwlagn is getting very shaky

On Mon, Nov 28, 2011 at 06:23, Norbert Preining <preining@...ic.at> wrote:
> On Mo, 28 Nov 2011, Emmanuel Grumbach wrote:
>> If the problem is solved, then no :-)
>
> I will report back. I have now reverted all the patches and additions
> by stashing them away, and applied only the last patch send. THe only
> thing out of default I see is:
> [ 1074.038324] wlan0: associated
> [ 1076.157989] Rx A-MPDU request on tid 0 result 0
> [ 1098.215008] Open BA session requested for 00:24:c4:ab:bd:ef tid 0
> [ 1098.232249] activated addBA response timer on tid 0
> [ 1098.232861] switched off addBA timer for tid 0
> [ 1098.232868] Aggregation is on for tid 0
> [ 1098.233027] iwlwifi 0000:06:00.0: Tx aggregation enabled on ra = 00:24:c4:ab:bd:ef tid = 0
> but it seems to work smoothly.
>
> I will report more after a few suspend/resume iteations.
>

Ok
It is a bit odd though since these prints seem to point to a
successful flow, while you were likely to experience a problem in the
handshake between the AP and your machine. I am basically saying that
this log is too good, you didn't get into the corner case that we
didn't handle properly.
--
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/