All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Schoenick <jschoenick@mozilla.com>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"Scott Sanbar" <scott.sanbar@gmail.com>,
	linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: BCM4331 fails to associate after suspend
Date: Fri, 03 Feb 2012 14:37:20 -0800	[thread overview]
Message-ID: <4F2C61A0.7070802@mozilla.com> (raw)
In-Reply-To: <20120203222818.GA3749@ubuntu-mba>

On 02/03/2012 02:28 PM, Seth Forshee wrote:
> I've been looking into some association problems seen with a MacBook Pro
> 8,2 that has BCM4331 wireless, which I've confirmed still exist in
> wireless-testing. The association failures reliably start appearing
> after the machine is resumed from s3 without external power applied
> (whether or not power is applied when the machine is suspended doesn't
> matter).
>
> When the association failures are happening the BCM4331 seems to be able
> to receive packets okay, as it can scan successfully. Transmissions
> don't work though; no frames from the BCM4331 are ever seen on the air,
> as though the tx path is off. Reloading both the b43 and bcma drivers
> gets things working again, but reloading just b43 does not.
>
> I've been looking around a bit in the b43 and bcma drivers, but so far I
> haven't found the reason why this happens. Any help would be
> appreciated. Let me know if there's additional information I can
> provide.
>
> Thanks,
> Seth
>
> _______________________________________________
> b43-dev mailing list
> b43-dev at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/b43-dev

I can add that reloading the modules after a suspend/resumes restores 
functionality, though oddly adding them to SUSPEND_MODULES in pm-utils 
config does not.

WARNING: multiple messages have this Message-ID (diff)
From: John Schoenick <jschoenick@mozilla.com>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"Scott Sanbar" <scott.sanbar@gmail.com>,
	linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: Re: BCM4331 fails to associate after suspend
Date: Fri, 03 Feb 2012 14:37:20 -0800	[thread overview]
Message-ID: <4F2C61A0.7070802@mozilla.com> (raw)
In-Reply-To: <20120203222818.GA3749@ubuntu-mba>

On 02/03/2012 02:28 PM, Seth Forshee wrote:
> I've been looking into some association problems seen with a MacBook Pro
> 8,2 that has BCM4331 wireless, which I've confirmed still exist in
> wireless-testing. The association failures reliably start appearing
> after the machine is resumed from s3 without external power applied
> (whether or not power is applied when the machine is suspended doesn't
> matter).
>
> When the association failures are happening the BCM4331 seems to be able
> to receive packets okay, as it can scan successfully. Transmissions
> don't work though; no frames from the BCM4331 are ever seen on the air,
> as though the tx path is off. Reloading both the b43 and bcma drivers
> gets things working again, but reloading just b43 does not.
>
> I've been looking around a bit in the b43 and bcma drivers, but so far I
> haven't found the reason why this happens. Any help would be
> appreciated. Let me know if there's additional information I can
> provide.
>
> Thanks,
> Seth
>
> _______________________________________________
> b43-dev mailing list
> b43-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/b43-dev

I can add that reloading the modules after a suspend/resumes restores 
functionality, though oddly adding them to SUSPEND_MODULES in pm-utils 
config does not.

  reply	other threads:[~2012-02-03 22:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 22:28 BCM4331 fails to associate after suspend Seth Forshee
2012-02-03 22:37 ` John Schoenick [this message]
2012-02-03 22:37   ` John Schoenick
2012-02-04 10:44 ` Arend van Spriel
2012-02-04 10:44   ` Arend van Spriel
2012-02-04 14:25   ` Seth Forshee
2012-02-04 14:25     ` Seth Forshee
2012-02-06 16:56     ` Rafał Miłecki
2012-02-06 16:56       ` Rafał Miłecki
2012-02-06 17:37       ` Seth Forshee
2012-02-06 17:37         ` Seth Forshee
2012-02-06 19:13         ` Hauke Mehrtens
2012-02-06 19:13           ` Hauke Mehrtens
2012-02-06 22:34           ` Seth Forshee
2012-02-06 22:34             ` Seth Forshee
2012-02-07  7:04             ` Rafał Miłecki
2012-02-07  7:04               ` Rafał Miłecki
2012-02-07  7:08               ` Rafał Miłecki
2012-02-07  7:08                 ` Rafał Miłecki
2012-02-07 15:29                 ` Seth Forshee
2012-02-07 15:29                   ` Seth Forshee
2012-02-16 14:55                   ` Seth Forshee
2012-02-16 14:55                     ` Seth Forshee

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=4F2C61A0.7070802@mozilla.com \
    --to=jschoenick@mozilla.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=scott.sanbar@gmail.com \
    --cc=seth.forshee@canonical.com \
    --cc=zajec5@gmail.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.