All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roland Vossen" <rvossen@broadcom.com>
To: "Guilherme Salazar" <gmesalazar@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: ieee80211 messages at startup (3.0 kernel)
Date: Mon, 25 Jul 2011 09:27:11 +0200	[thread overview]
Message-ID: <4E2D1ACF.1010307@broadcom.com> (raw)
In-Reply-To: <CA+Hmt2hyH3tZqSJjdOZfceGtpfHyTL4hh56ngXLHevOpVT07VA@mail.gmail.com>

Hi Guilherme,

 > I've been seeing weird messages concerning ieee80211 driver at startup
 > after using 3.0.0 kernel.
 > I don't know whether that is a problem or just debugging messages,
 > since everything is working fine,
 > but I've attached the dmesg output (before and after using the 3.0.0)
 > and my config file.

this issue has been fixed in the staging-next repo, the fix is probably 
still on its way to the wireless repo. FYI, the commit on staging-next is:

-----------------
commit 37c962d195005d009e130e65a9e55960996c3cab
Author: Roland Vossen <rvossen@broadcom.com>
Date:   Wed Jun 29 16:48:22 2011 -0700

     staging: brcm80211: fix for reported log spam problem

     Every few minutes, this message would appear in syslog:

     ieee80211 ph0: wl_ops_bss_info_changed: BSS idle: true (implement)

     The message has been deleted, the driver requires no special action 
on this
     particular event (). See: 
https://bugzilla.kernel.org/show_bug.cgi?id=38162
-----------------

Bye, Roland.


      reply	other threads:[~2011-07-25  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-24  0:53 ieee80211 messages at startup (3.0 kernel) Guilherme Salazar
2011-07-25  7:27 ` Roland Vossen [this message]

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=4E2D1ACF.1010307@broadcom.com \
    --to=rvossen@broadcom.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gmesalazar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.