From: Jon Masters <jonathan@jonmasters.org>
To: devel <devel@linuxdriverproject.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: PROBLEM: brcm80211 unable to survive suspend/resume cycle
Date: Mon, 08 Nov 2010 22:13:57 -0500 [thread overview]
Message-ID: <1289272437.3916.440.camel@constitution.bos.jonmasters.org> (raw)
Folks,
I reported this before, but let me open up a new thread for this now
that this driver has landed in 2.6.37-rc1 and been out for a while. I am
able to use this driver (more or less) for daily use on my netbook, but
it is unable survive a suspend/resume cycle without being unloaded and
then reloaded again on resume. That actually seems to work quite well.
I believe the problem is firmware related:
[ 553.355497] wl0: wlc_coreinit: ucode did not self-suspend!
[ 554.040495] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and
MI_MACSSPNDD is still not on.
[ 554.040517] wl0: psmdebug 0x000f8773, phydebug 0x00000000, psm_brc
0x0000
[ 554.154625] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and
MI_MACSSPNDD is still not on.
[ 554.154647] wl0: psmdebug 0x000f8773, phydebug 0x00000000, psm_brc
0x0000
[ 554.270438] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and
MI_MACSSPNDD is still not on.
[ 554.270459] wl0: psmdebug 0x000f8773, phydebug 0x00000000, psm_brc
0x0000
[ 554.384569] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and
MI_MACSSPNDD is still not on.
After the "ucode did not self-suspend", I then get the subsequent two
line warnings repeated forever until I reload the driver. Sure, it's
probably a firmware issue, but isn't there something the driver can do
to kick it into a full reset if it doesn't come back? It's able to do it
on module load initially...
Jon.
next reply other threads:[~2010-11-09 3:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 3:13 Jon Masters [this message]
2010-11-09 3:16 ` PROBLEM: brcm80211 unable to survive suspend/resume cycle Jon Masters
2010-11-09 3:24 ` Greg KH
2010-11-09 7:58 ` Jon Masters
2010-11-09 18:02 ` Brett Rudley
2010-11-09 23:11 ` Jon Masters
2010-11-16 4:04 ` Jon Masters
2010-12-08 7:03 ` Jon Masters
2010-12-08 7:10 ` Jon Masters
2010-12-22 14:31 ` Jon Masters
2011-01-12 9:26 ` Arend Van Spriel
2011-01-19 17:16 ` Jon Masters
2011-01-19 17:43 ` Arend Van Spriel
2011-01-19 17:51 ` Jon Masters
2011-03-14 7:09 ` Jon Masters
2011-01-19 21:19 ` Greg KH
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=1289272437.3916.440.camel@constitution.bos.jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=devel@linuxdriverproject.org \
--cc=linux-kernel@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 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).