From: "Arend van Spriel" <arend@broadcom.com>
To: "Milan Bouchet-Valat" <nalimilan@club.fr>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: BCM4313 doesn't work after suspend (brcmsmac on compat-wireless-next)
Date: Fri, 20 Jan 2012 18:04:44 +0100 [thread overview]
Message-ID: <4F199EAC.3050602@broadcom.com> (raw)
In-Reply-To: <1327067694.2590.6.camel@milan>
On 01/20/2012 02:54 PM, Milan Bouchet-Valat wrote:
> Hi!
>
> With kernels 3.2 and 3.2.1, my Broadcom 4313 wireless card doesn't work
> after suspend: I need to reload the brcmsmac module by hand on resume.
> It worked fine with 3.1 kernels.
>
> So I tried compat-wireless-next today (on Fedora 16), and it still
> doesn't work, though instead of oopses I get warnings. ;-)
>
> The error messages are:
> [ 165.612939] ieee80211 phy0: wl0: wlc_coreinit: ucode did not self-suspend!
> [ 165.751978] ieee80211 phy0: wl0: wlc_suspend_mac_and_wait: waited 83000 uS
> and MI_MACSSPNDD is still not on.
> [ 165.751989] ieee80211 phy0: wl0: psmdebug 0x00ff8181, phydebug 0x00000031,
> psm_brc 0x0000
>
> (the two latter repeated many times, see attached dmesg.log)
>
> Please ask for any details you may need (output of lspci -vnn is
> attached too, just in case).
>
>
> PS: Please keep me in CC, as I'm not subscribed to the list
I am not sure when compat-wireless-next was generated, but several
patches were made for suspend/resume. You also need bcma patches. Is
bcma included in the compat-wireless package.
Gr. AvS
next prev parent reply other threads:[~2012-01-20 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 13:54 BCM4313 doesn't work after suspend (brcmsmac on compat-wireless-next) Milan Bouchet-Valat
2012-01-20 17:04 ` Arend van Spriel [this message]
2012-01-20 17:22 ` Milan Bouchet-Valat
2012-01-21 9:58 ` Arend van Spriel
2012-01-24 10:25 ` Milan Bouchet-Valat
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=4F199EAC.3050602@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nalimilan@club.fr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).