From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC] ath9k: Fix softlockup in AR9485
Date: Thu, 31 May 2012 10:19:01 +0530 [thread overview]
Message-ID: <4FC6F83D.90107@qca.qualcomm.com> (raw)
In-Reply-To: <CAJ-VmomiQjGKKPtErYuhChpvqHCof4wXwt4BH2n1Rei_RnvyGA@mail.gmail.com>
Hi Adrian,
On Thursday 31 May 2012 12:18 AM, Adrian Chadd wrote:
> (Yes, this is a public response.)
>
> Hi,
>
> That has me a bit concerned. Waiting for the STA to be associated is
> really just some kind of "settling" delay. You're still TX/RXing at
> that point.
yeah, but i am pretty sure in the STA mode we have this PLL registers
having sane values once the STA is associated. i checked if i am missing
hardware code/init_pll routine or if its actually overwritten by INI
values, but no. i also checked this issue with IBSS and monitor mode
even under shield room, still it did not show much improvements or more
clue.
>
> I think we need to speak to the baseband/clock teams and figure out
> why this is actually occuring.
oh yes and i had been already sending some mails internally, checking
with people who might have good knowledge about this.
>
> Can we please leave this out of the tree (but in the bug report) until
> this gets root caused internally?
one thing i observed was this rx hang detection is based on the 'delta
of rx unicast packets' for a particular time. if its lesser than 5 this
rx hang detection kicks off. another system expert told me this rx hang
itself can be specific to AP rather than STA.
finally i would check with one system expert and another Engineer to get
some thoughts, then send it as a PATCH.
>
> Thanks,
>
>
>
> adrian
--
thanks,
shafi
WARNING: multiple messages have this Message-ID (diff)
From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
<linux-wireless@vger.kernel.org>,
Rodriguez Luis <rodrigue@qca.qualcomm.com>,
<ath9k-devel@lists.ath9k.org>, <stable@vger.kernel.org>
Subject: Re: [RFC] ath9k: Fix softlockup in AR9485
Date: Thu, 31 May 2012 10:19:01 +0530 [thread overview]
Message-ID: <4FC6F83D.90107@qca.qualcomm.com> (raw)
In-Reply-To: <CAJ-VmomiQjGKKPtErYuhChpvqHCof4wXwt4BH2n1Rei_RnvyGA@mail.gmail.com>
Hi Adrian,
On Thursday 31 May 2012 12:18 AM, Adrian Chadd wrote:
> (Yes, this is a public response.)
>
> Hi,
>
> That has me a bit concerned. Waiting for the STA to be associated is
> really just some kind of "settling" delay. You're still TX/RXing at
> that point.
yeah, but i am pretty sure in the STA mode we have this PLL registers
having sane values once the STA is associated. i checked if i am missing
hardware code/init_pll routine or if its actually overwritten by INI
values, but no. i also checked this issue with IBSS and monitor mode
even under shield room, still it did not show much improvements or more
clue.
>
> I think we need to speak to the baseband/clock teams and figure out
> why this is actually occuring.
oh yes and i had been already sending some mails internally, checking
with people who might have good knowledge about this.
>
> Can we please leave this out of the tree (but in the bug report) until
> this gets root caused internally?
one thing i observed was this rx hang detection is based on the 'delta
of rx unicast packets' for a particular time. if its lesser than 5 this
rx hang detection kicks off. another system expert told me this rx hang
itself can be specific to AP rather than STA.
finally i would check with one system expert and another Engineer to get
some thoughts, then send it as a PATCH.
>
> Thanks,
>
>
>
> adrian
--
thanks,
shafi
next prev parent reply other threads:[~2012-05-31 4:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 16:10 [ath9k-devel] [RFC] ath9k: Fix softlockup in AR9485 Mohammed Shafi Shajakhan
2012-05-30 16:10 ` Mohammed Shafi Shajakhan
2012-05-30 18:48 ` [ath9k-devel] " Adrian Chadd
2012-05-30 18:48 ` Adrian Chadd
2012-05-31 4:49 ` Mohammed Shafi Shajakhan [this message]
2012-05-31 4:49 ` Mohammed Shafi Shajakhan
2012-05-31 2:44 ` [ath9k-devel] " Sujith Manoharan
2012-05-31 2:44 ` Sujith Manoharan
2012-05-31 5:34 ` Mohammed Shafi Shajakhan
2012-05-31 5:34 ` Mohammed Shafi Shajakhan
2012-05-31 5:41 ` Sujith Manoharan
2012-05-31 5:41 ` Sujith Manoharan
2012-05-31 5:52 ` Mohammed Shafi Shajakhan
2012-05-31 5:52 ` Mohammed Shafi Shajakhan
2012-06-08 12:16 ` Sujith Manoharan
2012-06-08 12:16 ` Sujith Manoharan
2012-06-11 5:03 ` Mohammed Shafi Shajakhan
2012-06-11 5:03 ` Mohammed Shafi Shajakhan
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=4FC6F83D.90107@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.com \
--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.