From: Adam Baker <linux@baker-net.org.uk>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>,
rt2400-devel@lists.sourceforge.net, jbenc <jbenc@suse.cz>,
Michael Wu <flamingice@sourmilk.net>
Subject: Re: Kernel BUG when using ad-hoc mode in rt2x00
Date: Thu, 27 Sep 2007 23:00:29 +0100 [thread overview]
Message-ID: <200709272300.29829.linux@baker-net.org.uk> (raw)
In-Reply-To: <1190755233.18521.328.camel@johannes.berg>
On Tuesday 25 September 2007 22:20, Johannes Berg wrote:
> On Tue, 2007-09-25 at 23:09 +0200, Johannes Berg wrote:
> > On Tue, 2007-08-21 at 12:34 +0200, Johannes Berg wrote:
> > > At that point, sdata->bss should point to the master device, which
> > > apparently hasn't been initialised yet. The device initialisation code
> > > is pretty black magic to me, Jiri/Michael?
> >
> > No reply. Can you try this patch?
>
> Ah, no, there's a bug in this. Try this:
> http://johannes.sipsolutions.net/patches/kernel/all/2007-09-25-21%3a19/005-
>mac80211-fix-register-netdevice-error-return-oops.patch
>
I can't currently test it the way I was testing before because rt2x00
currently Oopses on unplug (I'll investigate that tomorrow) but it did
occasionally crash on scanning even if the interface had been up for a long
time before and with this patch it has survived quite a few scans.
I'll keep testing but it looks promising.
Adam Baker
prev parent reply other threads:[~2007-09-27 22:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 22:24 Kernel BUG when using ad-hoc mode in rt2x00 Adam Baker
2007-08-14 9:57 ` Ivo van Doorn
2007-08-15 9:50 ` Johannes Berg
2007-08-15 21:49 ` Adam Baker
2007-08-16 13:48 ` Johannes Berg
2007-08-16 15:25 ` Adam Baker
2007-08-16 15:35 ` Johannes Berg
2007-08-16 21:43 ` Adam Baker
2007-08-17 10:13 ` Johannes Berg
2007-08-20 20:21 ` Adam Baker
2007-08-21 10:34 ` Johannes Berg
2007-09-25 21:09 ` Johannes Berg
2007-09-25 21:20 ` Johannes Berg
2007-09-27 22:00 ` Adam Baker [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=200709272300.29829.linux@baker-net.org.uk \
--to=linux@baker-net.org.uk \
--cc=flamingice@sourmilk.net \
--cc=ivdoorn@gmail.com \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rt2400-devel@lists.sourceforge.net \
/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).