From: Johannes Berg <johannes@sipsolutions.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Giacomo Mulas <gmulas@ca.astro.it>,
linux-kernel@vger.kernel.org, debian-kernel@lists.debian.org,
Broadcom Linux <bcm43xx-dev@lists.berlios.de>
Subject: Re: b43 locks the machine when resuming after suspend to disk
Date: Thu, 03 Jul 2008 01:07:44 +0200 [thread overview]
Message-ID: <1215040064.13270.20.camel@johannes.berg> (raw)
In-Reply-To: <200807030108.37614.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
On Thu, 2008-07-03 at 01:08 +0200, Rafael J. Wysocki wrote:
> On Thursday, 3 of July 2008, Johannes Berg wrote:
> > On Wed, 2008-07-02 at 23:40 +0200, Rafael J. Wysocki wrote:
> > > On Wednesday, 2 of July 2008, Giacomo Mulas wrote:
> > > > I tried searching on the list for this, before posting, but searching the
> > > > mailing list archives with keywords such as b43, suspend, resume... brings
> > > > up such a ludicrous amount of threads that it's not realistic to check them
> > > > all, so just tell me what to look for if it's been asked already.
> > > >
> > > > Whenever I do a suspend to disk after using b43, the computer freezes hard
> > > > as soon as it attempts again to access b43 after resume.
> > > >
> > > > Minimal how to reproduce the freeze:
> > > > 1) modprobe b43
> > > > 2) hibernate (using any suspend to disk, which one is irrelevant)
> > > > 3) resume
> > > > 4) ifconfig wlan0 up
> >
> > > I think you need the appended patch, but it only applies to linux-next.
> >
> > Rafael, you misled me :) This is a completely different thing.
>
> Ah, sorry then. I was too quick with my response.
No trouble, it reminded me that I wanted to ask stable to pick up that
patch anyway although I don't think we ever ran into the issue there.
This seems very odd though, Giacomo, are you sure it also happens if you
unload the module?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-07-02 23:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 20:51 Giacomo Mulas
2008-07-02 21:40 ` Rafael J. Wysocki
2008-07-02 21:46 ` Johannes Berg
2008-07-02 21:56 ` Johannes Berg
2008-07-02 22:32 ` Larry Finger
2008-07-02 22:37 ` Johannes Berg
2008-07-02 22:56 ` Johannes Berg
2008-07-02 23:08 ` Rafael J. Wysocki
2008-07-02 23:07 ` Johannes Berg [this message]
2008-07-02 23:27 ` Larry Finger
2008-07-02 23:41 ` Johannes Berg
2008-07-03 9:19 ` Giacomo Mulas
2008-07-10 18:10 ` Pavel Machek
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=1215040064.13270.20.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=debian-kernel@lists.debian.org \
--cc=gmulas@ca.astro.it \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®