From: Johannes Berg <johannes@sipsolutions.net>
To: Jake Edge <jake@lwn.net>
Cc: linux-wireless@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Bisected 3.9 regression for iwl4965 connection problem to 1672c0e3
Date: Mon, 06 May 2013 17:24:19 +0200 [thread overview]
Message-ID: <1367853859.8434.11.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130506092143.58a7713f@chukar.edge2.net>
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
next prev parent reply other threads:[~2013-05-06 15:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-05 20:38 Bisected 3.9 regression for iwl4965 connection problem to 1672c0e3 Jake Edge
2013-05-06 12:38 ` Stanislaw Gruszka
2013-05-06 14:37 ` Jake Edge
2013-05-06 15:30 ` Stanislaw Gruszka
2013-05-06 15:31 ` Johannes Berg
2013-05-06 15:44 ` Johannes Berg
2013-05-07 8:42 ` Stanislaw Gruszka
2013-05-07 8:46 ` Emmanuel Grumbach
2013-05-07 13:53 ` Johannes Berg
2013-05-07 15:35 ` Stanislaw Gruszka
2013-05-07 16:07 ` [PATCH 3.10] iwl4965: workaround connection regression on passive channel Stanislaw Gruszka
2013-05-22 11:59 ` Bisected 3.9 regression for iwl4965 connection problem to 1672c0e3 Stanislaw Gruszka
2013-05-24 20:28 ` Johannes Berg
2013-05-06 15:11 ` Johannes Berg
2013-05-06 15:21 ` Jake Edge
2013-05-06 15:24 ` Johannes Berg [this message]
2013-05-06 15:29 ` Jake Edge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1367853859.8434.11.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jake@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).