From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Johannes Berg <johannes@sipsolutions.net>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Kernel oops with 2.6.31-wl
Date: Mon, 14 Sep 2009 22:55:40 +0200 [thread overview]
Message-ID: <200909142255.42958.mb@bu3sch.de> (raw)
In-Reply-To: <4AAEAC90.7070205@lwfinger.net>
On Monday 14 September 2009 22:50:24 Larry Finger wrote:
> Michael Buesch wrote:
> > On Monday 14 September 2009 20:20:21 Larry Finger wrote:
> >> Johannes Berg wrote:
> >>> On Mon, 2009-09-14 at 09:05 -0500, Larry Finger wrote:
> >>>> Using the kernel v2.6.31-38241-g2d3a51e, I get the following kernel
> >>>> oops when unloading b43:
> >>>> RIP: 0010:[<ffffffffa02a3a3e>] [<ffffffffa02a3a3e>]
> >>>> b43_op_config+0x10c/0x36f [b43]
> >>> Seems like a b43 problem to me.
> >> I had pretty much reached that conclusion. I will need to swap cards
> >> to debug as the 4315 won't run on older kernels without a lot of patches.
> >
> > I can't reproduce here. What sequence of events is needed to trigger this?
>
> All I have to do is make a connection, then "sudo modprobe -rv b43"
> while the connection is live. I have not tried shutting the interface
> down before the modprobe. It gets through the "rmmod b43" and the
> "rmmod ssb" and then crashes.
Ok, works. Thanks.
I'll send a patch soon.
--
Greetings, Michael.
prev parent reply other threads:[~2009-09-14 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 14:05 Kernel oops with 2.6.31-wl Larry Finger
2009-09-14 17:40 ` Johannes Berg
2009-09-14 18:20 ` Larry Finger
2009-09-14 20:45 ` Michael Buesch
2009-09-14 20:50 ` Larry Finger
2009-09-14 20:55 ` Michael Buesch [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=200909142255.42958.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).