linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Dale Turner <rx_guy@hotmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: carl9170 problem
Date: Tue, 28 Sep 2010 13:35:44 +0200	[thread overview]
Message-ID: <201009281335.44475.chunkeey@googlemail.com> (raw)
In-Reply-To: <SNT113-W459FFC08EF0C4936BEDD5CF1660@phx.gbl>

On Tuesday 28 September 2010 03:47:00 Dale Turner wrote:
> >> kernel: ieee80211 phy9: FW: MAC RESET
> > The device failed to send pending data for more than 150ms(HT40) - 300ms,
> > either because the medium was busy, or the AP failed to response at all
> > mostly because it has crashed first.
> > (check if your AP's TSF is no where near your AP's uptime)
> 
> I don't think there are any nearby networks on my channel.
> I purposely change it from default ( 6 ) to 11 (actually wide 9).
What's wide 9? HT40 with the primary channel on 11 and the extension
on 6?
 
> The access point is a Linksys wrt120n (probably not the best, I know).
Isn't this a 1-stream align-n (AR9285) platform? If so then there is
no advantage of using an AR9170 over the AR9271.

> To be honest, I don't know what a TSF is or how to check it.
The TSF keeps the timers for all STAs in the "network" synchronized.
http://en.wikipedia.org/wiki/Timing_Synchronization_Function_%28TSF%29

It can be easily check by: iw dev wlanX scan

e.g.: (sample output)
BSS 00:02:32:0d:d1:32 (on wlan13)
        TSF: 2669831323 usec (0d, 00:44:29) <-------
        freq: 2437

This will tell you that the "network" has an uptime of
0 days, 0 hours, 44 minutes and 29 seconds.

Regards,
	Chr

      parent reply	other threads:[~2010-09-28 11:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25  0:34 carl9170 problem Dale Turner
2010-09-25 22:57 ` Christian Lamparter
     [not found]   ` <SNT113-W459FFC08EF0C4936BEDD5CF1660@phx.gbl>
2010-09-28 10:11     ` Dale Turner
2010-09-28 11:35     ` Christian Lamparter [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=201009281335.44475.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rx_guy@hotmail.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).