linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: Fabio Rossi <rossi.f@inwind.it>, linux-wireless@vger.kernel.org
Subject: Re: regression with kernel 3.8
Date: Mon, 25 Feb 2013 23:38:38 +0100	[thread overview]
Message-ID: <1361831918.9192.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130225192629.GH13296@thinkpad-t410>

On Mon, 2013-02-25 at 13:26 -0600, Seth Forshee wrote:
> On Mon, Feb 25, 2013 at 07:18:16PM +0100, Fabio Rossi wrote:
> > I'm using the latest wireless-testing.git and I have found a regression with 
> > kernel 3.8. I don't know if this is related to the driver I'm using (ath5k) but 
> > I have bisected the problem to the commit 
> > 6c17b77b67587b9f9e3070fb89fe98cef3187131 (mac80211: Fix tx queue handling 
> > during scans). Basically the authentication and association infos don't appear 
> > anymore in the kernel logs during a connection to my access point.
> > 
> > Tell me what you need to further debug the issue and solve the problem.
> 
> That patch is after 3.8.
> 
> Johannes, this looks like a problem with the changes you made when
> applying that patch. I really should have tested the result before now.

Hmm, crap. Sorry about that!

> I think the off-channel frames are getting queued rather than passed
> down to the driver, which obviously isn't what we want. I'll get this
> fixed.

I saw you posted it, I'll take a closer look tomorrow morning.

johannes


  parent reply	other threads:[~2013-02-25 22:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25 18:18 regression with kernel 3.8 Fabio Rossi
2013-02-25 19:26 ` Seth Forshee
2013-02-25 20:58   ` [PATCH] mac80211: Ensure off-channel frames don't get queued Seth Forshee
2013-02-26 20:16     ` Johannes Berg
2013-02-25 22:38   ` Johannes Berg [this message]
2013-02-26 19:13     ` regression with kernel 3.8 Seth Forshee

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=1361831918.9192.1.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rossi.f@inwind.it \
    --cc=seth.forshee@canonical.com \
    /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).