linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Björn Smedman" <bjorn.smedman@venatech.se>
To: ath9k-devel@lists.ath9k.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: ath9k: association lost on ap side only
Date: Sun, 8 Aug 2010 20:29:49 +0200	[thread overview]
Message-ID: <AANLkTi=o6m9pSaXQ4ago6sRoE1R7-O6uv0S35Dy2VO7a@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim4ccC7pQrW0LymdZ_cAiaBhLW3VofsFj9CcpfP@mail.gmail.com>

2010/8/7 Björn Smedman <bjorn.smedman@venatech.se>:
> Hi all,
>
> I'm trying out compat-wireless-2010-07-29 with openwrt/trunk@22474
> patches on AR913x and quite often (a few times a day) run into a
> problem where my laptop thinks it's associated but the router thinks
> it's not.

I also run into some weirdness where the laptop disassociates (macos
reports it as "AirPort: Link Down on en1. Reason 4 (Disassociated due
to inactivity)"). From end-users point of view it's like if somebody
pulled the power on the router, but it comes back faster than it would
in that case.

The log looks like this when that happened:

Aug  8 18:20:11 OpenWrt user.debug kernel: ath: Timeout while waiting
for nf to load: AR_PHY_AGC_CONTROL=0x40d22
Aug  8 18:20:32 OpenWrt user.debug kernel: ath: DMA failed to stop in
10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
Aug  8 18:20:32 OpenWrt user.debug kernel: ath: DMA failed to stop in
10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
Aug  8 18:20:48 OpenWrt user.debug kernel: ath: DMA failed to stop in
10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
Aug  8 18:20:48 OpenWrt user.debug kernel: ath: DMA failed to stop in
10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020

/Björn

      reply	other threads:[~2010-08-08 18:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-07 15:52 ath9k: association lost on ap side only Björn Smedman
2010-08-08 18:29 ` Björn Smedman [this message]

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='AANLkTi=o6m9pSaXQ4ago6sRoE1R7-O6uv0S35Dy2VO7a@mail.gmail.com' \
    --to=bjorn.smedman@venatech.se \
    --cc=ath9k-devel@lists.ath9k.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).