From: John Greene <jogreene@redhat.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Joe Perches <joe@perches.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] brcmsmac: Reduce log spam in heavy tx, make err print in debug
Date: Tue, 04 Jun 2013 10:10:42 -0400 [thread overview]
Message-ID: <51ADF562.7050707@redhat.com> (raw)
In-Reply-To: <51ACCD0E.10407@broadcom.com>
On 06/03/2013 01:06 PM, Arend van Spriel wrote:
> On 06/03/2013 06:54 PM, Joe Perches wrote:
>> On Mon, 2013-06-03 at 09:47 -0400, John Greene wrote:
>>> Move message to debug mode to reduce log spam under heavy tx (iperf)
>>> load.
>> []
>>> diff --git a/drivers/net/wireless/brcm80211/brcmsmac/ampdu.c
>>> b/drivers/net/wireless/brcm80211/brcmsmac/ampdu.c
>> []
>>> @@ -900,7 +900,7 @@ brcms_c_ampdu_dotxstatus_complete(struct
>>> ampdu_info *ampdu, struct scb *scb,
>>> if (supr_status) {
>>> update_rate = false;
>>> if (supr_status == TX_STATUS_SUPR_BADCH) {
>>> - brcms_err(wlc->hw->d11core,
>>> + brcms_dbg_ht(wlc->hw->d11core,
>>> "%s: Pkt tx suppressed, illegal channel
>>> possibly %d\n",
>>> __func__, CHSPEC_CHANNEL(
>>> wlc->default_bss->chanspec));
>>
>> net_ratelimited instead?
>
> Yes and only when driver debug level is set.
>
> Regards,
> Arend
>
>
Thanks for the ACK, Arend. And comments..live and learn.
Certainly they would be reasonable also. Issue (confined to an
annoyance level, hence the workaround) is why this comes up when the
channel being flagged is the same as the one the AP I'm connected with
is on. That is the root of the problem, more work needed on that point
which probably would render this moot.
--
John Greene
next prev parent reply other threads:[~2013-06-04 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 13:47 [PATCH] brcmsmac: Reduce log spam in heavy tx, make err print in debug John Greene
2013-06-03 16:54 ` Joe Perches
2013-06-03 17:06 ` Arend van Spriel
2013-06-04 14:10 ` John Greene [this message]
2013-06-03 17:07 ` Arend van Spriel
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=51ADF562.7050707@redhat.com \
--to=jogreene@redhat.com \
--cc=arend@broadcom.com \
--cc=joe@perches.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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.