From: Sujith Manoharan <sujith@msujith.org>
To: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 5/5] ath9k: Fix TX IQ calibration for SoC chips
Date: Wed, 15 Jan 2014 13:45:00 +0530 [thread overview]
Message-ID: <21206.17284.157496.206327@gargle.gargle.HOWL> (raw)
In-Reply-To: <52D63EBB.7020607@neratec.com>
Wojciech Dubowik wrote:
> Jan 15 08:43:44 wlanTS kernel: [ 1177.026210] NOISE/RSSI/SIGNAL for 04:f0:21:04:56:9e: -87/53/-34
> Jan 15 08:43:44 wlanTS kernel: [ 1177.028515] NOISE/RSSI/SIGNAL for 04:f0:21:04:56:9e: -87/55/-32
> Jan 15 08:43:44 wlanTS kernel: [ 1177.028768] ath: phy0: Set HW Key
> Jan 15 08:43:44 wlanTS kernel: [ 1177.028827] ath: phy0: Set HW Key
> Jan 15 08:43:44 wlanTS kernel: [ 1177.032695] NOISE/RSSI/SIGNAL for 04:f0:21:04:56:9e: -87/53/-34
> Jan 15 08:43:44 wlanTS kernel: [ 1177.032710] ath: phy0: bmiss: 10 sleep: 15360
> Jan 15 08:43:44 wlanTS kernel: [ 1177.032716] ath: phy0: next DTIM 106306560
> Jan 15 08:43:44 wlanTS kernel: [ 1177.032717] ath: phy0: next beacon 106306560
> Jan 15 08:43:44 wlanTS kernel: [ 1177.032718] ath: phy0: beacon period 15360
> Jan 15 08:43:44 wlanTS kernel: [ 1177.032719] ath: phy0: DTIM period 15360
> Jan 15 08:43:44 wlanTS kernel: [ 1177.032749] cfg80211: Found new beacon on frequency: 5180 MHz (Ch 36) on phy0
> Jan 15 08:43:44 wlanTS kernel: [ 1177.032758] cfg80211: Pending regulatory request, waiting for it to be processed...
> Jan 15 08:43:44 wlanTS kernel: [ 1177.048561] NOISE/RSSI/SIGNAL for 04:f0:21:04:56:9e: -87/39/-48
> Jan 15 08:43:44 wlanTS kernel: [ 1177.063921] NOISE/RSSI/SIGNAL for 04:f0:21:04:56:9e: -87/37/-50
> Jan 15 08:43:44 wlanTS kernel: [ 1177.079283] NOISE/RSSI/SIGNAL for 04:f0:21:04:56:9e: -87/33/-54
I can reproduce this issue too and this happens only once - right after
association. After association, running a background scan doesn't show any
problems.
Sujith
next prev parent reply other threads:[~2014-01-15 8:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 5:10 [PATCH 1/5] ath9k: Separate routines for PCOEM and SoC calibration Sujith Manoharan
2013-11-17 5:10 ` [PATCH 2/5] ath9k: Remove RTT/MCI code from " Sujith Manoharan
2013-11-17 5:10 ` [PATCH 3/5] ath9k: Remove unnecessary check Sujith Manoharan
2013-11-17 5:10 ` [PATCH 4/5] ath9k: Fix Carrier Leak calibration for SoC chips Sujith Manoharan
2013-11-17 5:10 ` [PATCH 5/5] ath9k: Fix TX IQ " Sujith Manoharan
2014-01-09 12:17 ` Wojciech Dubowik
2014-01-09 13:10 ` Sujith Manoharan
2014-01-09 13:35 ` Wojciech Dubowik
2014-01-09 13:52 ` Sujith Manoharan
2014-01-09 13:59 ` Wojciech Dubowik
2014-01-13 14:34 ` Wojciech Dubowik
2014-01-13 15:07 ` Sujith Manoharan
[not found] ` <52D402C3.3070606@neratec.com>
[not found] ` <21204.1991.201080.986559@gargle.gargle.HOWL>
2014-01-13 15:42 ` Sujith Manoharan
2014-01-13 16:06 ` Sujith Manoharan
2014-01-15 7:54 ` Wojciech Dubowik
2014-01-15 8:15 ` Sujith Manoharan [this message]
2014-01-15 8:30 ` Wojciech Dubowik
2014-01-16 11:06 ` Sujith Manoharan
2014-01-16 11:19 ` Sujith Manoharan
2014-01-16 11:44 ` Wojciech Dubowik
2014-01-16 21:36 ` Sujith Manoharan
2014-01-17 7:30 ` Wojciech Dubowik
2014-01-20 3:33 ` Sujith Manoharan
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=21206.17284.157496.206327@gargle.gargle.HOWL \
--to=sujith@msujith.org \
--cc=Wojciech.Dubowik@neratec.com \
--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).