All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tor Krill <tor@excito.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: corrupt frames forwarded to mac80211 as decrypted
Date: Fri, 30 Apr 2010 11:07:14 +0200	[thread overview]
Message-ID: <1272618434.2191.19.camel@tor-desktop> (raw)
In-Reply-To: <87och2ku6z.fsf@gmail.com>

On Thu, 2010-04-29 at 14:08 -0400, Ben Gamari wrote:
> On Thu, 29 Apr 2010 10:41:36 +0200, Tor Krill <tor@excito.com> wrote:
> > This patch, in modified form went into wireless-testing and linux-next a
> > few days ago
> > 
> > http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commit;h=3a37495268ab45507b4cab9d4cb18c5496ab7a10
> > 
> > And it indeed fixed a lot of our issues :). Unfortunately we still
> > experience failures with ath9k in AP mode with these symptoms.
> > 
> > We lose connectivity on STA side, we still seems to be associated but
> > are unable to transfer any data. Any reconnection fails.
> > 
> 
> If I'm not mistaken, I seem to see the same type of behavior on this
> side. I have a AR5008s in both the STA and AP. After a few hours or so
> of association the suddenly refuses to send or recieve, yet remains
> associated. Thereafter, all further association attempts timeout until
> the driver is reloaded (rmmod/insmod) on the STA. After reloading, I
> will be able to reassociate and things will work fine for a few more
> hours.
> 
> I'm not sure if this is precisely the same issue that you're
> experiencing (I always pinned this on the STA since reloading the driver
> seems to reset things) but I felt the similarities were too striking not
> to say something. I'd be happy to provide any debugging information
> necessary.

Yes, could it perhaps be that you experience the same problem, bug, as
we do but in the STA instead? (Since it also run ath9k).

/Tor

  parent reply	other threads:[~2010-04-30  9:07 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31 19:10 ath9k: receive stops working in AP-mode and 802.11n Johan Hovold
2010-03-31 19:10 ` [ath9k-devel] " Johan Hovold
2010-04-16 10:48 ` ath9k: corrupt frames forwarded to mac80211 as decrypted (was: ath9k: receive stops working in AP-mode and 802.11n) Johan Hovold
2010-04-16 10:48   ` [ath9k-devel] " Johan Hovold
2010-04-16 10:52   ` [RFC][PATCH 1/6] ath9k: clean up rx skb post-process logic Johan Hovold
2010-04-16 10:52     ` [ath9k-devel] " Johan Hovold
2010-04-16 10:52   ` [RFC][PATCH 2/6] ath9k: do not mark frames with RXKEY_IX_INVALID as decrypted Johan Hovold
2010-04-16 10:52     ` [ath9k-devel] " Johan Hovold
2010-04-16 11:32     ` Jouni Malinen
2010-04-16 11:32       ` Jouni Malinen
2010-04-20  8:35       ` Johan Hovold
2010-04-20  8:35         ` Johan Hovold
2010-04-16 10:52   ` [RFC][PATCH 3/6] ath9k: do not mark frames with RX_DECRYPT_BUSY " Johan Hovold
2010-04-16 10:52     ` [ath9k-devel] " Johan Hovold
2010-04-16 10:52   ` [RFC][PATCH 4/6] ath9k: do not mark frames with RX_KEY_MISS " Johan Hovold
2010-04-16 10:52     ` [ath9k-devel] " Johan Hovold
2010-04-16 10:52   ` [RFC][PATCH 5/6] ath9k: check error flags even if rx frame is marked ok Johan Hovold
2010-04-16 10:52     ` [ath9k-devel] " Johan Hovold
2010-04-16 10:52   ` [RFC][PATCH 6/6] ath9k: clear mic error flag on encrypted frames Johan Hovold
2010-04-16 10:52     ` [ath9k-devel] " Johan Hovold
2010-04-20  8:25   ` [ath9k-devel] ath9k: corrupt frames forwarded to mac80211 as decrypted Johan Hovold
2010-04-20  8:25     ` Johan Hovold
2010-04-20  8:28     ` [RFC][PATCH 1/2] ath9k: fix corrupt frames being forwarded to mac80211 Johan Hovold
2010-04-20  8:28       ` [ath9k-devel] " Johan Hovold
2010-04-20  8:38       ` Johan Hovold
2010-04-20  8:38         ` [ath9k-devel] " Johan Hovold
2010-04-20  8:28     ` [RFC][PATCH 2/2] ath9k: use also AR_DecryptBusyErr to determine decrypt errors Johan Hovold
2010-04-20  8:28       ` [ath9k-devel] " Johan Hovold
2010-04-20  9:10     ` [ath9k-devel] ath9k: corrupt frames forwarded to mac80211 as decrypted Ranga Rao Ravuri
2010-04-20  9:10       ` Ranga Rao Ravuri
2010-04-20 11:06       ` Johan Hovold
2010-04-20 11:06         ` Johan Hovold
2010-04-20 11:35         ` Johan Hovold
2010-04-20 11:35           ` Johan Hovold
2010-04-29  8:26           ` Daniel Yingqiang Ma
2010-04-29  8:26             ` Daniel Yingqiang Ma
2010-04-29  8:41             ` Tor Krill
2010-04-29  9:35               ` Daniel Yingqiang Ma
2010-04-29 18:08               ` Ben Gamari
2010-04-29 20:08                 ` Will Dyson
2010-04-30  9:07                 ` Tor Krill [this message]
2010-04-29 20:21               ` Benoit PAPILLAULT
2010-04-30  9:50               ` Tor Krill

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=1272618434.2191.19.camel@tor-desktop \
    --to=tor@excito.com \
    --cc=ath9k-devel@lists.ath9k.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.