All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roland Vossen" <rvossen@broadcom.com>
To: "Larry Finger" <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: More log spam from brcm80211
Date: Thu, 24 Mar 2011 17:37:53 +0100	[thread overview]
Message-ID: <4D8B7361.8050803@broadcom.com> (raw)
In-Reply-To: <4D8B6D2D.3090505@lwfinger.net>

Hello Larry,

did you already try my preliminary patch (email that I sent you 
yesterday) for the previous log spam problem ?

Regarding this new problem: I will get back to you shortly.

Bye, Roland.


On 03/24/2011 05:11 PM, Larry Finger wrote:
> Roland,
>
> My logs are getting spammed with lots of "Short CCK" messages that come from the
> following code fragment:
>
>                   if (IS_CCK(rspec)) {
>                           if (rxh->PhyRxStatus_0&  PRXS0_SHORTH)
>                                   WL_ERROR("Short CCK\n");
>                           rx_status->flag |= RX_FLAG_SHORTPRE;
>                   } else if (IS_OFDM(rspec)) {
>                           rx_status->flag |= RX_FLAG_SHORTPRE;
>                   } else {
>                           WL_ERROR("%s: Unknown modulation\n", __func__);
>                   }
>
> Logging this condition for debugging might be appropriate, but I do not think it
> necessary for general use.
>
> Larry
>



  parent reply	other threads:[~2011-03-24 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24 16:11 More log spam from brcm80211 Larry Finger
2011-03-24 16:34 ` Roland Vossen
2011-03-24 16:37 ` Roland Vossen [this message]
2011-03-24 16:49   ` Larry Finger
2011-03-25  9:50     ` Roland Vossen

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=4D8B7361.8050803@broadcom.com \
    --to=rvossen@broadcom.com \
    --cc=Larry.Finger@lwfinger.net \
    --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 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.