From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tor Krill Date: Fri, 30 Apr 2010 11:07:14 +0200 Subject: [ath9k-devel] ath9k: corrupt frames forwarded to mac80211 as decrypted In-Reply-To: <87och2ku6z.fsf@gmail.com> References: <20100331191058.GD18913@lundinova.se> <20100416104850.GA13329@lundinova.se> <20100420082519.GB5288@lundinova.se> <1271754651.14253.112.camel@ranga-desktop> <20100420110657.GH5288@lundinova.se> <20100420113505.GJ5288@lundinova.se> <1272530496.5866.50.camel@tor-desktop> <87och2ku6z.fsf@gmail.com> Message-ID: <1272618434.2191.19.camel@tor-desktop> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Thu, 2010-04-29 at 14:08 -0400, Ben Gamari wrote: > On Thu, 29 Apr 2010 10:41:36 +0200, Tor Krill 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