From: Jonathan McDowell <noodles@earth.li>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Intel Linux Wireless <ilw@linux.intel.com>
Subject: Re: [Ilw] Problems with Intel 2230 and AP mode
Date: Wed, 10 Apr 2013 14:26:55 -0700 [thread overview]
Message-ID: <20130410212655.GE31591@earth.li> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB301969FA5@HASMSX103.ger.corp.intel.com>
On Mon, Apr 08, 2013 at 05:52:47AM +0000, Grumbach, Emmanuel wrote:
> > > > > > >
> > > > > > > I'm trying to build my own wifi router, cobbling together
> > > > > > > a Debian (wheezy) box, hostapd (1.0) and an Intel 2230.
> > > > > > > I'm seeing various problems with the 2230 and I'm
> > > > > > > wondering if I'm mad for trying to use this card in AP
> > > > > > > mode (in which case is there an alternative Intel card I
> > > > > > > should use, or is an ath9k my best bet), or if it's
> > > > > > > worthwhile reporting the issues and trying fixes.
> > > > > > >
> > > > > > > I'm using 3.8.5 (and previously 3.8.4). I tried 3.9-rc4
> > > > > > > briefly but it was unusable - as soon as there was any
> > > > > > > traffic I saw errors like:
> > > ...
> > > > Can you please try the patch attached?
> > > >
> > > > Note that I couldn't really test it so...
> > > >
> > > > Also, it seems that the best way to reproduce the issue is to have a
> > > > station disappear while TX AMPDU is working.
> > >
> > > I suspect that's being caused by the cell phones appearing briefly and
> > > then disappearing. I've applied the patch to 3.9-rc5 (and also "iwlwifi:
> > > dvm: don't send HCMD in restart flow" which I saw hit stable but isn't
> > > in rc5) and I've had the following WARNING:
...
> > Stupid me - can you please try with this one?
>
> Err again.... Take this one instead... Sorry...
This is looking good - up for over 48 hours now on 3.9-rc6 + your patch
and no "txq_id mismatch" messages, no WARNINGs and no sign of the
firmware restart messages either. Thanks!
J.
--
Real Programmers don't drink decaf.
next prev parent reply other threads:[~2013-04-10 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 19:08 Problems with Intel 2230 and AP mode Jonathan McDowell
2013-04-02 19:11 ` [Ilw] " Grumbach, Emmanuel
2013-04-03 18:21 ` Jonathan McDowell
2013-04-07 7:23 ` Grumbach, Emmanuel
2013-04-07 22:03 ` Jonathan McDowell
2013-04-08 5:39 ` Grumbach, Emmanuel
2013-04-08 5:52 ` Grumbach, Emmanuel
2013-04-10 21:26 ` Jonathan McDowell [this message]
2013-04-26 18:17 ` [Ilw] Firmware problems " Jonathan McDowell
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=20130410212655.GE31591@earth.li \
--to=noodles@earth.li \
--cc=emmanuel.grumbach@intel.com \
--cc=ilw@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.