From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: ap tsf seems random and only uses lower 24 bits or so
Date: Tue, 29 Jun 2010 18:52:34 +0200 [thread overview]
Message-ID: <4C2A24D2.4070007@openwrt.org> (raw)
In-Reply-To: <AANLkTik_d6tIKj3otsgaojVBPfvW1lz9OBRujeZLyv1U@mail.gmail.com>
On 2010-06-29 6:36 PM, Bj?rn Smedman wrote:
> 2010/6/29 Felix Fietkau <nbd@openwrt.org>:
>> One beacon miss should never cause a TSF reset. Only a lot of
>> consecutive beacon misses trigger a hardware reset, which then resets
>> the TSF. Looking at your log, it appears that the beacon miss is a
>> symptom rather than a cause of the TSF jumps.
>> Can you add a debug statement to the hw reset function to see if it's
>> called before the TSF jumps?
>
> Yup, seems to be a hardware reset. Added an ath_print ("Reset HW!") at
> the beginning of ath9k_hw_reset() and used debug mask 0x101:
>
> ...
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 3 [tsf 14863367
> tsftu 14515 intval 100] vif (null)
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 2 [tsf 14888967
> tsftu 14540 intval 100] vif (null)
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 1 [tsf 14914568
> tsftu 14565 intval 100] vif (null)
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: Reset HW!
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: ah->misc_mode 0xc
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: Setting CFG 0x10a
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 0 [tsf 80123
> tsftu 78 intval 100] vif 80945e70
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: missed 1 consecutive beacons
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: Reset HW!
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: ah->misc_mode 0xc
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: Setting CFG 0x10a
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 0 [tsf 80989
> tsftu 79 intval 100] vif 80945e70
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: missed 1 consecutive beacons
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: resume beacon xmit
> after 1 misses
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 3 [tsf 117792
> tsftu 115 intval 100] vif (null)
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 2 [tsf 143368
> tsftu 140 intval 100] vif (null)
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 1 [tsf 168967
> tsftu 165 intval 100] vif (null)
> ...
Please add another print to the end of ath9k_hw_check_alive() before the
'return false'. Make sure it prints the value of the 'reg' variable.
If you see it in the log, then it's probably the baseband getting stuck.
- Felix
WARNING: multiple messages have this Message-ID (diff)
From: Felix Fietkau <nbd@openwrt.org>
To: "Björn Smedman" <bjorn.smedman@venatech.se>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
ath9k-devel@lists.ath9k.org
Subject: Re: ath9k: ap tsf seems random and only uses lower 24 bits or so
Date: Tue, 29 Jun 2010 18:52:34 +0200 [thread overview]
Message-ID: <4C2A24D2.4070007@openwrt.org> (raw)
In-Reply-To: <AANLkTik_d6tIKj3otsgaojVBPfvW1lz9OBRujeZLyv1U@mail.gmail.com>
On 2010-06-29 6:36 PM, Björn Smedman wrote:
> 2010/6/29 Felix Fietkau <nbd@openwrt.org>:
>> One beacon miss should never cause a TSF reset. Only a lot of
>> consecutive beacon misses trigger a hardware reset, which then resets
>> the TSF. Looking at your log, it appears that the beacon miss is a
>> symptom rather than a cause of the TSF jumps.
>> Can you add a debug statement to the hw reset function to see if it's
>> called before the TSF jumps?
>
> Yup, seems to be a hardware reset. Added an ath_print ("Reset HW!") at
> the beginning of ath9k_hw_reset() and used debug mask 0x101:
>
> ...
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 3 [tsf 14863367
> tsftu 14515 intval 100] vif (null)
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 2 [tsf 14888967
> tsftu 14540 intval 100] vif (null)
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 1 [tsf 14914568
> tsftu 14565 intval 100] vif (null)
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: Reset HW!
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: ah->misc_mode 0xc
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: Setting CFG 0x10a
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 0 [tsf 80123
> tsftu 78 intval 100] vif 80945e70
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: missed 1 consecutive beacons
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: Reset HW!
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: ah->misc_mode 0xc
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: Setting CFG 0x10a
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 0 [tsf 80989
> tsftu 79 intval 100] vif 80945e70
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: missed 1 consecutive beacons
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: resume beacon xmit
> after 1 misses
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 3 [tsf 117792
> tsftu 115 intval 100] vif (null)
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 2 [tsf 143368
> tsftu 140 intval 100] vif (null)
> Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 1 [tsf 168967
> tsftu 165 intval 100] vif (null)
> ...
Please add another print to the end of ath9k_hw_check_alive() before the
'return false'. Make sure it prints the value of the 'reg' variable.
If you see it in the log, then it's probably the baseband getting stuck.
- Felix
next prev parent reply other threads:[~2010-06-29 16:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 22:31 [ath9k-devel] ath9k: ap tsf seems random and only uses lower 24 bits or so Björn Smedman
2010-06-28 22:31 ` Björn Smedman
2010-06-28 22:55 ` [ath9k-devel] " Felix Fietkau
2010-06-28 22:55 ` Felix Fietkau
2010-06-29 6:08 ` [ath9k-devel] " Benoit Papillault
2010-06-29 6:08 ` Benoit Papillault
2010-06-29 11:45 ` Felix Fietkau
2010-06-29 11:45 ` Felix Fietkau
2010-06-29 21:23 ` Benoit Papillault
2010-06-29 21:23 ` Benoit Papillault
2010-06-29 15:20 ` Björn Smedman
2010-06-29 15:20 ` Björn Smedman
2010-06-29 15:55 ` [ath9k-devel] " Felix Fietkau
2010-06-29 15:55 ` Felix Fietkau
2010-06-29 16:36 ` [ath9k-devel] " Björn Smedman
2010-06-29 16:36 ` Björn Smedman
2010-06-29 16:52 ` Felix Fietkau [this message]
2010-06-29 16:52 ` Felix Fietkau
2010-06-29 17:32 ` [ath9k-devel] " Björn Smedman
2010-06-29 17:32 ` Björn Smedman
2010-06-29 21:40 ` [ath9k-devel] " Björn Smedman
2010-06-29 21:40 ` Björn Smedman
2010-06-29 21:54 ` [ath9k-devel] " Felix Fietkau
2010-06-29 21:54 ` Felix Fietkau
2010-06-29 22:50 ` [ath9k-devel] " Björn Smedman
2010-06-29 22:50 ` Björn Smedman
2010-06-29 23:56 ` [ath9k-devel] " Felix Fietkau
2010-06-29 23:56 ` Felix Fietkau
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=4C2A24D2.4070007@openwrt.org \
--to=nbd@openwrt.org \
--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.