All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: wireless <linux-wireless@vger.kernel.org>,
	"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
	Kan Yan <kanyan@broadcom.com>,
	Roland Vossen <rvossen@broadcom.com>,
	Henry Ptasinski <henryp@broadcom.com>,
	Brett Rudley <brudley@broadcom.com>
Subject: Re: Instability in brcmsmac
Date: Wed, 22 Feb 2012 17:48:15 -0600	[thread overview]
Message-ID: <4F457EBF.6010203@lwfinger.net> (raw)
In-Reply-To: <4F451459.2050807@broadcom.com>

On 02/22/2012 10:14 AM, Arend van Spriel wrote:
>
> I tried reproducing this, but not luck so far. Could you provide me with syslog
> including both kernel messages and wpa_supplicant. From the log you provided it
> seems mac80211 triggers the disassoc. It could be a beacon timeout, but I would
> like to be sure. More debug output from mac80211 itself would also be helpful to
> understand the issue.

I may have misunderstood the symptoms with my system. The only AP that is 
connected automatically is 802.11n; however, many of my cards now refuse to 
connect to that AP. The BCM43224 is one of them. As a result, when the 
connection to an 802.11g AP failed, the reconnection was to the N router, and it 
failed.

I need to determine what is causing the failure to connect to the N router. It 
might be a regression. After I find and fix that problem, then I can retest the 
BCM43224.

Thanks, and sorry for the noise,

Larry


      reply	other threads:[~2012-02-22 23:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19 20:53 Instability in brcmsmac Larry Finger
2012-02-20 10:24 ` Arend van Spriel
2012-02-22 16:14 ` Arend van Spriel
2012-02-22 23:48   ` Larry Finger [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=4F457EBF.6010203@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=arend@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=frankyl@broadcom.com \
    --cc=henryp@broadcom.com \
    --cc=kanyan@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rvossen@broadcom.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.