linux-kernel - Re: Bisected 3.9 regression for iwl4965 connection problem to 1672c0e3

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: <1367853859.8434.11.camel@jlt4.sipsolutions.net>
Date:	Mon, 06 May 2013 17:24:19 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Jake Edge <jake@....net>
Cc:	linux-wireless@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>
Subject: Re: Bisected 3.9 regression for iwl4965 connection problem to
 1672c0e3

On Mon, 2013-05-06 at 09:21 -0600, Jake Edge wrote:

> > Thanks for the report. Is the AP on a passive channel by any chance (5
> > GHz, or channels 12/13)?
> 
> No, from what I can see on my router, it is using channel 36 (5.180
> GHz) for the SSID in question

So yes, that is a passive channel for the 4965 device :-)

> but Stanislaw seems to have pinpointed the issue.

Yeah that was a workaround, but I'm not sure we'd really want to do
that. I'd rather see what really caused this issue. I have a feeling
it's the passive-no-RX workaround, or lack thereof maybe? I need to look
a bit closer.

johannes

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